Self-hosted badge data via shields endpoint badges - #56
Merged
Conversation
A daily workflow queries the Marketplace stats API once, writes shields endpoint JSON to the badges branch, and the README's Marketplace installs/rating badges render from that — removing the dependency on the third-party vsmarketplacebadges.dev service. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the last third-party badge middleman. We're two generations into single-maintainer VS Marketplace badge services dying (apphb → shields retirement → vsmarketplacebadges.dev); this makes the repo self-sufficient:
Badge Dataworkflow (daily cron + manual dispatch): queries the MarketplaceextensionqueryAPI once per day (vs once per README view — far gentler on the undocumented API than any badge service can be), formats the numbers, and force-pushesinstalls.json/rating.jsonin shields endpoint schema to an orphanbadgesbranch.vsmarketplacebadges.devbadges (Marketplace installs, rating) now render viaimg.shields.io/endpointfrom that branch. Same labels and colors as before.badgesbranch is already seeded and verified end-to-end — shields is currently rendering133.97Kfrom it, so the badges render correctly the moment this merges.After merge: nothing required — the cron takes over (09:23 UTC daily). The workflow can also be run manually from the Actions tab anytime.
Left alone: CI, release, Open VSX, Spectra Assure, and stars badges — those sources are all first-party or documented.