Skip to content

Updated NuGet 4.3.0+ support of SemVer 2.0.0 #1373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
asbjornu merged 3 commits into from
Mar 9, 2018
Merged

Updated NuGet 4.3.0+ support of SemVer 2.0.0 #1373

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
569dfcf
Updated NuGet 4.3.0+ support of SemVer 2.0.0
Feb 16, 2018
580e8fa
Merge branch 'master' into update-nuget-support-semver2
asbjornu Mar 9, 2018
c2248cb
Merge branch 'master' into update-nuget-support-semver2
asbjornu Mar 9, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ GitVersion v3 was rewritten to be very configuration driven rather than hardcodi
Read more about [configuration](configuration.md)

## Output Variables
We recognise that a single formatted version number does not work for all cases. A simple example is NuGet, it doesn't support SemVer 2.0 meaning that the SemVer of `1.3.5-beta.10+500` needs to be formatted as `1.3.5-beta0010` so it will sort properly.
We recognise that a single formatted version number does not work for all cases. A simple example is NuGet, prior to version 4.3.0 it doesn't support SemVer 2.0 meaning that the SemVer of `1.3.5-beta.10+500` needs to be formatted as `1.3.5-beta0010` so it will sort properly.

You can just run `GitVersion.exe` in your repository to see what variables are available (by default a json object is returned).

Expand Down