We’ve recently made an intentional change where we append the build number after the pre-release tag. Everything was working perfectly, until we hit build number 100. All new new builds are now considered (via their version) older then build number 99.
Is this type of versioning not supported?
Hi,
Thanks for reaching out! Octopus reads your version alpha-numerically, and uses periods to deliminate version numbers. The solution would be to use a period instead of the dash (-) after your pre-release tag, and Octopus will sort the version numerically, and the versions will be read correctly. For your example, it will look like 1.0.0-feature-WSAPI6.100.
If you’d like more information on how we handle version numbers, you can find more here 
http://semver.org/
Let me know how you go!
Kenny
