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

Clearly call out that floating versions are not valid nuspec versions #1318

nkolev92 opened this issue Feb 19, 2019 · 1 comment


Copy link

commented Feb 19, 2019

In the dependency section in the nuspec, only version ranges are allowed.

The floating versions were added years later than the original version range design.

There's been various customers confused as to how this works because the documentation is not clear enough.


This comment has been minimized.

Copy link

commented Aug 12, 2019

Updating doc. Looks like package versioning doc already mentions this, so just updating the .nuspec reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.