You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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.
lockbot
locked as resolved and limited conversation to collaborators
Nov 26, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I try to call OctoPack with a package version of "1.0.2897-3932.octopus.deploy", I get the following error:
If I understand Rule 9 in the Semver Spec correctly, my version number should be valid. Is this an error in OctoPack?
The text was updated successfully, but these errors were encountered: