ci(release): auto-bump README version badges + make them static - #8
Merged
Conversation
The macOS 'release' and 'latest' badges were dynamic shields.io GitHub endpoints, which intermittently render 'Unable to select next GitHub token from pool' during shields' API rate-limit windows — so the README appeared not to update after a release. Make them static badges with the literal version baked in, and have the release bot rewrite that version in the same commit that pushes the version bump + appcast.xml. Now the README always matches the published release with zero external-API dependency. iOS keeps its dynamic App Store badge (separate pipeline). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
github-actions
Bot
added
documentation
katipally
added a commit
that referenced
this pull request
Jun 13, 2026
ci(release): auto-bump README version badges + make them static
katipally
added a commit
that referenced
this pull request
Aug 4, 2026
ci(release): auto-bump README version badges + make them static
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.
Why
After v2.7.2 shipped, the README's macOS version badges looked stale. Root cause: they were dynamic shields.io GitHub badges that intermittently render
Unable to select next GitHub token from poolwhen shields' GitHub-API token pool is rate-limited. The data was correct (latest release is v2.7.2) but the render flapped.What
release+ the download-tilelatest) are now static shields badges with the literal version — no external-API dependency, so they can never flap.release.ymlrewrites that version in the same commit that pushes the version bump +appcast.xml, so the README always matches the release just published.README.mdis added to the staged file list.Verified: static badges render cleanly, and the sed bump correctly rewrites
v2.7.2 → vNEXT.🤖 Generated with Claude Code