feat: cache VS Code Marketplace version badge via Gist#88
Merged
Conversation
Replace the unreliable vsmarketplacebadges.dev badge with a shields.io endpoint badge that reads from a GitHub Gist JSON file. The release workflow now writes the version to the same Gist used for coverage, so the badge never hits a flaky third-party service. - Add version extraction and dynamic-badges-action step to release.yml - Update README badge URL to use Gist endpoint - Remove vsmarketplacebadges.dev from lychee exclude list - Seed Gist with initial version.json for v0.0.1 Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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.
Summary
Replace the unreliable
vsmarketplacebadges.devbadge with a shields.io endpoint badge backed by a GitHub Gist JSON file. The release workflow writes the current version to the Gist after each publish, so the badge reads from a static, cached source instead of hitting a flaky third-party service.Changes
schneegans/dynamic-badges-actionto writeversion.jsonto the same Gist used for the coverage badgevsmarketplacebadges.devto shields.ioendpointreading from the Gistvsmarketplacebadges.devexclusion (no longer referenced)version.jsonfor v0.0.1Why
vsmarketplacebadges.devreturns transient HTTP 500 errors, causing the badge to show broken/stale. The Gist-backed approach is the same pattern already used for the coverage badge, so it is proven reliable.