Why is v2.5.0 "newer" than v3.1.0

[aarcro]

Seriously.

[TWiStErRob]

#wrongforum ;)

It's a maintenance release to reduce warnings in the ecosystem. It just happened to be released after 3.1.0, which puts it as the latest release in the Releases view. This should work itself out in a few weeks when they publish 3.2 or 3.1.x.

If you want you can go to GitHub Discussions and report this.

@rentziass you might want to re-tag 3.1.0 so it's on top, but it might involve force pushing or recreating the tag/release.

[rentziass]

I'd refrain from changing history, v2.5.0 was indeed our latest release but it was only a backport to help v2 users not get swamped with warnings. Thanks for the help @TWiStErRob!

[taig]

https://github.blog/changelog/2022-10-21-explicitly-set-the-latest-release/

[TWiStErRob]

No way! 😂