Badge Request: GitHub Package Registry - Version Badge

[calebcartwright]

📋 Description
Download count badges for packages hosted on the GitHub Package Registry

• Which service is this badge for e.g: GitHub Package Registry
• What sort of information should this badge show? Package versions/latest version

🔗 Data

• Is there a public API? Yes
• Does the API requires an API key? Auth should be used like our other GH services, specifically leveraging our BaseGraphQlService.

🎤 Motivation
Because people want them! 😄 The motivation/benefits for the version badges for the GH Package registry is the same as the other registries we support

Related: #3608 and #4071

[crimson-med]

Any update on this? I have recently been using Github Packages and would love to display version and download.

[calebcartwright]

Thanks for the bump @crimson-med! This, and other GitHub Package related badges are blocked on #4169

tl;dr - The Shields.io service leverages a pool of tokens that are used to retrieve data from the API for our GH badges, but none of those tokens have the requisite permissions needed to retrieve Package data from the GH API. It's a non-trivial problem, but one I think we should focus some attention on (would encourage folks to track #4169 for more information)

[crimson-med]

@calebcartwright Thank you for the update I have subscribed to #4169 and hopefully a solution will come to light soon.

[xavisavvy]

Adding my comment here to watch this thread. This would indeed be a useful addition.

[Devwarlt]

I'm looking forward for this addition!

[calebcartwright]

Folks, we post updates whenever they are available, so please refrain repeated "bump" comments which are not particularly helpful. You should instead use the reaction features to indicate your support for this enhancement.

If this is something you're particularly interested in, and would like to see it delivered more quickly than the maintainer team has bandwidth to do, then please consider submitting a PR

[chris48s]

While I agree with the general thrust of this (bump comments are unhelpful - we'll update if there's any progress), I think this needs clarifying: There is already an open PR for this badge #4184 but the feature is blocked on #4169 . In order to move this (and other things) forward, #4169 is the issue we'd need to help with. If someone in the community is keen to help us with that it would be a really welcome contribution, but also some design decisions about it are still unclear.

[RosieWatson]

Are there anymore updates on this?

[calebcartwright]

Are there anymore updates on this?

No, not really. Please see prior comment #4183 (comment)

We have made some changes to the backend infrastructure (notably the mechanism we use to store the github tokens) which does open up some doors in design discussions.

However, there continues to be no substantive updates and the latest status on this issue is already reflected in the above comments.

We will happily share such updates here when they occur, but in the meantime I want to reiterate that the absence of explicit updates posted by the maintainers here means that there are no updates.

[ryansonshine]

Are there anymore updates on this?

No, not really. Please see prior comment #4183 (comment)

We have made some changes to the backend infrastructure (notably the mechanism we use to store the github tokens) which does open up some doors in design discussions.

However, there continues to be no substantive updates and the latest status on this issue is already reflected in the above comments.

We will happily share such updates here when they occur, but in the meantime I want to reiterate that the absence of explicit updates posted by the maintainers here means that there are no updates.