Hex.pm badges display "invalid response data" when a package has never had a stable release #7658
Labels
bug
Bugs in badges and the frontend
service-badge
Accepted and actionable changes, features, and bugs
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
![](https://camo.githubusercontent.com/d5cfcca951b9f24a54067f0e35c4bf6c0e83740f83055c0a7710719fa3541e16/68747470733a2f2f696d672e736869656c64732e696f2f686578706d2f762f7072696d615f6f70656e74656c656d657472795f6578)
馃挕 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: