Wrong semantic colouring for badge of GitHub Release

[akiirui]

Are you experiencing an issue with...

shields.io

🐞 Description

For the GitHub releases badge, it should use orange if the latest release is a pre-release and blue otherwise. So blue if this is off, orange if it is on (from #10268 (comment))

Such as https://github.com/mpv-player/mpv/releases/tag/v0.39.0, it isn't mark as "pre-release", but badge uses "orange" by the default.

🔗 Link to the badge

https://img.shields.io/github/v/release/mpv-player/mpv

💡 Possible Solution

It should be blue.

[chris48s]

With the GitHub releases badge, we'll defer to the pre-release flag checkbox for stable releases.
For a semver-like version number, we'll assume it is a pre-release if its a zero-version (like in this case) or has a tag like -alpha -beta, etc.
In this case, we're considering 0.39.0 pre-release/unstable because the major version is zero
https://semver.org/#spec-item-4
If you want to override it, you are free to do that: https://img.shields.io/github/v/release/mpv-player/mpv?color=blue

[akiirui]

Okay thanks for your answer.