-
Notifications
You must be signed in to change notification settings - Fork 640
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.
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
NuGet version is gone, and there will be changes... #201
Comments
Or we can just bring back NuGetVersion then when v3 drops we release v2 of GitVersion which switches NuGet from LegacySemVerPadded to SemVer? |
To make it backwards compatible for me I added this code to the VariableProvider class:
|
Not sure bringing back The other thing is should we pad the NuGet version by default, or should we have a NuGetPadded |
The padded is only needed if you have tags greater than 10. i.e
|
unfortunately we cannot determine when padding will be needed. so we always add it |
It's just so I can go on vacation in 2 hours and I don't have to change a zillion of builds. I am not saying Version should go back in the official version, I have just built my own version for the sake of backwards compatibility. I prefer padding all the time instead of switching when the moon and sun are on the same level but only in August. |
And what does "0.2.0-unstable.10+10" mean? I can understand the 10 (that is the no of commits), but +10? |
given nugets history of dodgy versioning i suspect there will be more dodgy work arounds that will need to be applied to future nuget implementations of semver. so i am leaning towards naming them explicitly like @GeertvanHorrik any drawbacks people can see? thoughts? |
@GeertvanHorrik how did you get that version number? For develop you should get Lets take a beta. |
@SimonCropp I am happy with adding NuGetVersionV2 for now, then when v3 drops we figure it out then. OR we just add NuGetVersion back now, and it is for the latest version of NuGet. So when NuGet v3 drops we go to v2 and have a breaking change |
@GeertvanHorrik basically the +metadata is a way to include additional metadata which doesn't change the semantic version. so |
It's the result of SetBuildVersion call. When I debug with this url: /url https://github.com/Orcomp/C5Intervals /b develop /output buildserver Caused by a call to semanticVersion.ToString("f") |
Interesting, I think that is a bug possibly. But that is a separate discussion |
@JakeGinnivan Created new issue for the possible bug: #202 |
I think we should do this:
All agree? |
seams reasonable to me |
Code is ready, but awaiting other pull request first. |
In VariableProvider, at the bottom (before return variables):
|
I propose we lowercase it as well to avoide Beta/beta sorting issues? Sent from my iPhone
|
Good idea. Only the NuGetVersion items? |
I'd say only nuget* since this only a nuget snag Sent from my iPhone
|
Once my other pull request is accepted, I will start a new one introducing this (don't want to mess around with too many branches with an upstream master). |
@GeertvanHorrik have merged your other PR |
Already pushing new fixes. Was more work then I expected with all the unit tests... |
So GitVersion_NuGetVersion is gone but can be used by "LegacySemVerPadded". Apparently it will be changed for v3, so the idea is to introduce 2 new variables:
GitVersion_NuGetVersionV2 => synonym for LegacySemVerPadded
GitVersion_NuGetVersionV3 => synonym for ???
The text was updated successfully, but these errors were encountered: