Skip to content
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

Support semver-2.0+buildMetadata #1486

Closed
AArnott opened this issue Sep 29, 2015 · 8 comments
Closed

Support semver-2.0+buildMetadata #1486

AArnott opened this issue Sep 29, 2015 · 8 comments

Comments

@AArnott
Copy link
Contributor

AArnott commented Sep 29, 2015

This doc says Nuget will support build metadata as defined by semver 2.0.0. But in NuGet 3.2 it doesn't work:

nuget pack
Attempting to build package from 'Nerdbank.GitVersioning.nuspec'.
'1.1.48-rc+gabf25bdbae' is not a valid version string.
Parameter name: version

@emgarten
Copy link
Member

Pack is still using NuGet.Core 2.8.6 which does not support semver 2.0.0.

@emgarten
Copy link
Member

Dupe of #1359

@AArnott
Copy link
Contributor Author

AArnott commented Sep 30, 2015

But #1359 is already closed (as won't fix, evidently). Might this issue be considered as a request for a subset of semver-2.0? (one that can be done without all the breaking changes brought in by the rest of semver-2.0?

@emgarten
Copy link
Member

emgarten commented Oct 1, 2015

What subset are you looking for? build metadata?

@AArnott
Copy link
Contributor Author

AArnott commented Oct 3, 2015

Yes, per the example and issue title.

@RehanSaeed
Copy link

I'm using the latest version of nuget.exe from https://dist.nuget.org/win-x86-commandline/latest/nuget.exe and am getting the following error complaining about the version number when using the nuget publish command:

'1.0.0-1' is not a valid version string.

nuget.exe does not like the dash in the version number. There is a related issue on the ASP.NET 5 DNX GitHub repository here. I'm publishing to an internal NuGet server. Shouldn't this already be fixed?

@AArnott
Copy link
Contributor Author

AArnott commented Nov 19, 2015

@RehanSaeed Although semver allows for the prerelease identifier to start with a digit, I suspect nuget's implementation does not. I suspect 1.0.0-a1 would work.

@RehanSaeed
Copy link

Thanks @AArnott! I believe you are correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants