You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hex.pm badges display the "invalid response data" error when a package has only unstable (beta/rc) releases and no stable releases.
Ideally, the badge should fallback to showing the latest unstable release when there are no stable releases.
Currently, the badge looks at the latest_stable_version field returned by Hex.pm API to retrieve the latest version.
When that field is null, such as in this example, the badge could look at the latest_version field.
The text was updated successfully, but these errors were encountered:
Fs00
added
the
question
Support questions, usage questions, unconfirmed bugs, discussions, ideas
label
Feb 28, 2022
Are you experiencing an issue with...
shields.io
🐞 Description
Hex.pm badges display the "invalid response data" error when a package has only unstable (beta/rc) releases and no stable releases.
Ideally, the badge should fallback to showing the latest unstable release when there are no stable releases.
🔗 Link to the badge
https://img.shields.io/hexpm/v/prima_opentelemetry_ex.svg
💡 Possible Solution
Currently, the badge looks at the
latest_stable_version
field returned by Hex.pm API to retrieve the latest version.When that field is null, such as in this example, the badge could look at the
latest_version
field.The text was updated successfully, but these errors were encountered: