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.

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

Jump to bottom

When will nuget.com server support SemVer 2.0.0 ? #8121

Closed
lovettchris opened this issue May 9, 2019 · 4 comments
Closed

When will nuget.com server support SemVer 2.0.0 ? #8121

lovettchris opened this issue May 9, 2019 · 4 comments
Labels
Area:PackageDefinition Area:Protocol Client/Server protocol /code around it Resolution:Question This issues appears to be a question, not a product defect

Comments

@lovettchris
Copy link

lovettchris commented May 9, 2019 •
edited
Loading

I see the nice long spec but that was two years ago. When is it going to happen?
@nkolev92
Copy link
Member

nuget.org supports Semver2, see the tracking issue #1359.

The feature has been live for about ~2 years now.
Clients newer than 4.3 & VS 2017 update 3 also support it.

@nkolev92 nkolev92 added Area:PackageDefinition Area:Protocol Client/Server protocol /code around it Resolution:Question This issues appears to be a question, not a product defect labels May 10, 2019
@lovettchris
Copy link
Author

Huh, weird, I just tried to publish a package with the version "8.0.0-1" and the "nuget push" failed saying the version was invalid.

@nkolev92
Copy link
Member

Unfortunately you are hitting NuGet/NuGetGallery#6948.

Feel free to comment on the issue there.

@lovettchris
Copy link
Author

Yes, I see the comment " /// which do not support a . in release labels, or release labels starting with numeric characters. ". I'll try "8.0.0-a1" instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area:PackageDefinition Area:Protocol Client/Server protocol /code around it Resolution:Question This issues appears to be a question, not a product defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nkolev92 @lovettchris