Stub crashes if semver segment has leading zero

[cbenard]

If you use a datestamp version like 2018.0418.1, the YourAppName.exe stub that shortcuts point to will crash on startup, logging the BEX error like people had when they used a 4 part version in #905.

Can this be fixed by updating the semver you depend on?

Ideally, we wouldn't have to use 2018.418.1, because with an ordinal sort, 418 (Apr 18) > 1001 (Oct 1). I'm assuming semver is knowledgeable and does a numeric value compare and not an ordinal sort, but the version is used elsewhere as well.

Thank you.

[cbenard]

@paulcbetts Hi Paul. I'm not trying to bother you too much, but it's been a month. Have you had a chance to see if a newer semver library can fix this crash?

[anaisbetts]

This won't be fixed because it is explicitly against the SemVer specification (https://semver.org/):

2. A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.

[cbenard]

Understood. Thanks for clarification.