Octo.exe semantic version support with dashes followed by zero padded version values

Legacy Modelling
1

Octo.exe is unable to package a project that attempts to use a version of, say, “1.0.0-03” but succeeds with “1.0.0.03”. No urgency as we’ve switched our versions to use the “.” over the “-”.

failure_to_parse_1.0.3-03_but_not_1.0.3.03.png

2

Hi Kevin,

Thanks for getting in touch! Great to hear your switch to use a . in your version numbers is working. The reason why your initial 1.0.0-03 version can’t be packaged is because pre-releases with a leading 0 (-03) aren’t considered valid SemVer. Some valid versions I’ve been able to successfully package are 1.0.0-0.3, 1.0.0-3, or 1.0.0-alpha. Would something like that be a better option? You can also refer to more info about SemVer on their website: http://semver.org/#spec-item-9

I hope that helps! Let me know if you have any further questions.

Best regards,

Kenny

3

Sure enough…

“Numeric identifiers MUST NOT include leading zeroes”

Thanks for the clarification. Please close this thread as it’s not a bug after all!

4

Hi Kevin,

That’s no problem at all! Please don’t hesitate to reach out if you have any further questions or concerns. :slight_smile:

Best regards,

Kenny