Fix NuGet package versions #257
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The version numbers of the NuGet packages which are pushed to nuget.org currently include the Git commit ID as a suffix (e.g. 1.5.1-g60ffd20a7c).
This causes NuGet to mark those packages as prerelease, and as a result most people stick to the 1.2.0 version, which is about 8 months old.
NB.GV drops the build suffix when building from master (as specified in
version.json
). Because Travis checks out the commits in a detached head state, NB.GV doesn't detect this and adds the suffix anyway.NB.GV detects 'cloud build services' using environment variables, but doesn't have built in support for Travis (yet, see dotnet/Nerdbank.GitVersioning#310).
As a workaround, set the environment variables used by other cloud build services.