prerelease SemvVer tags are wrongly detected as newer than the release

[ghost]

• prerelease: v8.77.25-alpha.1
• release: v8.77.25

The shied on the readme should display the first instead of the latter.

[paulmelnikow]

Hi! Which badge are you referring to? Is the problem still observable with that package?

[ghost]

sorry, issue was not well formulated. I'll reopen with a concret example.

[SuperSandro2000]

You know you can edit issues?

[ghost]

Concrete example, look (ASAP since it may change soon) at the badge here https://github.com/dlang/phobos/blob/master/README.md. and now the tags: https://github.com/dlang/phobos/releases.

[RedSparr0w]

On mobile right now so can't look into it properly, but for anyone else looking into this issue:
I believe this is due to the way GitHubs api sends the data through (alphabetical order) rather than by date released (this is from memory of another similar issue relating to tags).

[ghost]

It's also about how the SemVer is interpreted i think. I use a library, for example, that's aware of the common -alpha.<n>, -beta.<n> and finally -rc.<n> suffixes, and assert(SemVer("1.0.0-beta.1") < SemVer("1.0.0")) works.

[RedSparr0w]

it looks like it fails fails due to not providing a strictly valid semver version 2.079.0 should be 2.79.0,
Will create a PR patching this soon.

[ghost]

Yes but while this is is right for this one i had the same issue with a repo with a valid SemVer.

[RedSparr0w]

If you could provide an example repo I can investigate further.