[BUG] Wrong sorting of versions

[eluchsinger]

I have a version 1.9 that is listed before 1.14.

Right now it is:

• 1.9
• 1.8
• 1.7
• ...
• 1.2
• 1.14
• 1.13

[ljharb]

fwiw a version includes the patch number; omitting it makes it invalid semver.

[cookpete]

Numeric versions (without the v prefix) are sorted numerically here:

https://github.com/CookPete/auto-changelog/blob/85bd07328c0871b230f4a8309ba79e05d32fe46f/src/releases.js#L56-L58

I guess that needs changing to infer semver even without the v prefix, now that we have that feature.

[eluchsinger]

I didn't completely understand if this is a bug or it's desired behavior.

I am using GitVersion. The Version numbers are generated automatically... I have to investigate, what is causing the missing patch number.

[cookpete]

I am using GitVersion. The Version numbers are generated automatically

It might just be that GitVersion doesn't use semver for some reason, which is fine.

I think it's ok to update the logic and assume that 1.14 will always be a later version than 1.2.

[cookpete]

This should be fixed in [email protected]