Changes to enable SemVer in binary and NuGet version numbers. #1480
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
dilijev
commented
Aug 23, 2016
•
dilijev
commented
- Provide the ability to specify all four fields of the NuGet package version (by defining environment variables in the build environment with defaults specified in init_build.ps1).
- No longer pad binary version number segments.
- No longer use build number in the product version number (include that information in the file version string, along with branch, commit, and build date).
|
@curtisman Need to merge this so that we can build a NuGet package from specifically the |
dilijev
changed the title
* Provide the ability to specify all four fields of the NuGet package version (by defining environment variables in the build environment with defaults specified in init_build.ps1). * No longer pad binary version number segments. * No longer use build number in the product version number (include that information in the file version string, along with branch, commit, and build date).
chakrabot
pushed a commit
that referenced
this pull request
Aug 24, 2016
…ersion numbers. Merge pull request #1480 from dilijev:nuget * Provide the ability to specify all four fields of the NuGet package version (by defining environment variables in the build environment with defaults specified in init_build.ps1). * No longer pad binary version number segments. * No longer use build number in the product version number (include that information in the file version string, along with branch, commit, and build date).
chakrabot
pushed a commit
that referenced
this pull request
Aug 24, 2016
…y and NuGet version numbers. Merge pull request #1480 from dilijev:nuget * Provide the ability to specify all four fields of the NuGet package version (by defining environment variables in the build environment with defaults specified in init_build.ps1). * No longer pad binary version number segments. * No longer use build number in the product version number (include that information in the file version string, along with branch, commit, and build date).
dilijev
added a commit
that referenced
this pull request
Aug 24, 2016
…nd NuGet version numbers. Merge pull request #1480 from dilijev:nuget * Provide the ability to specify all four fields of the NuGet package version (by defining environment variables in the build environment with defaults specified in init_build.ps1). * No longer pad binary version number segments. * No longer use build number in the product version number (include that information in the file version string, along with branch, commit, and build date).
chakrabot
pushed a commit
that referenced
this pull request
Aug 25, 2016
…r in binary and NuGet version numbers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.