24
Vote

Support build version information using SemVer RC1 notation

description

See discussion here:
http://nuget.codeplex.com/discussions/283794#post715745

Build information should facilitate continuous integration scenarios. This should be possible for pre-release packages as well.

In addition, it seems the pre-release version information does not allow additional dot-separated info, which is allowed by semver.org.

comments

johncrim wrote May 2, 2012 at 7:07 AM

I created issue: http://nuget.codeplex.com/workitem/2137 before seeing this. There's certainly a case that these are dups, but my bug description is more specific.

JeffHandley wrote Jan 23, 2013 at 9:07 PM

Putting into the NuGet 2.4 bucket. By the time we move on from 2.3, SemVer might have reached RTM. We don't want to implement support for build versions until SemVer hits RTM though.

forki wrote Jan 25, 2013 at 9:02 PM

My issue http://nuget.codeplex.com/workitem/2988 was warked as dup. Please check that this works as well.

ctaggart wrote Aug 29, 2013 at 5:03 PM

Build metatdata was changed for SemVer 2.0. See Phil Haack's 2013-06-18 blog post. Of importance is the section on pre-release identifiers. This issue could be changed to "Support SemVer 2.0". Or should a separate issue be created?

ctaggart wrote Aug 29, 2013 at 5:18 PM

Issue 2247 was titled "Implement semver v2.0" and was marked as a duplicate of this issue.

ctaggart wrote Dec 25, 2013 at 12:19 AM

I added Issue 3924 allow Semantic Versioning 2.0.0 characters with a patch to the regex to support it. It would be a minor step towards full SemVer 2.0.0 support and would be really nice to have in the next build.