Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hex.pm badges display "invalid response data" when a package has never had a stable release #7658

Closed
Fs00 opened this issue Feb 28, 2022 · 1 comment 路 Fixed by #7685
Closed
Labels
bug Bugs in badges and the frontend service-badge Accepted and actionable changes, features, and bugs

Comments

@Fs00
Copy link

Fs00 commented 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.

@Fs00 Fs00 added the question Support questions, usage questions, unconfirmed bugs, discussions, ideas label Feb 28, 2022
@calebcartwright calebcartwright added bug Bugs in badges and the frontend service-badge Accepted and actionable changes, features, and bugs and removed question Support questions, usage questions, unconfirmed bugs, discussions, ideas labels Mar 1, 2022
@PyvesB
Copy link
Member

PyvesB commented Mar 5, 2022

Thanks for reporting this @Fs00 , we'll get a fix landed soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bugs in badges and the frontend service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants