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

OctoPack - Why is this not a valid version string? #2260

Closed
jkodroff opened this issue Dec 29, 2015 · 2 comments
Closed

OctoPack - Why is this not a valid version string? #2260

jkodroff opened this issue Dec 29, 2015 · 2 comments

Comments

@jkodroff
Copy link

When I try to call OctoPack with a package version of "1.0.2897-3932.octopus.deploy", I get the following error:

MSBUILD : OctoPack error OCTONUGET: '1.0.2897-3932.octopus.deploy' is not a valid version string. 
...
MSBUILD : OctoPack error OCT-1676060969: There was an error calling NuGet. Please see the output above for more details. 

If I understand Rule 9 in the Semver Spec correctly, my version number should be valid. Is this an error in OctoPack?

@jkodroff
Copy link
Author

Turns out, it is a valid string, but only for SemVer 2.0. NuGet only supports SemVer 1.0, which does not allow .-separated pre-release identifiers, which is a major bummer for me. Thus, this is not an OctoPack issue: OctoPack is complying with the NuGet spec.

There is an open issue with NuGet on getting full SemVer 2.0 support.

@lock
Copy link

lock bot commented Nov 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant