fix: release experience polish (badge reliability + updater heading)#85
Merged
Conversation
…s badge The README release and downloads badges use shields.io's dynamic GitHub-API endpoints, which intermittently fail with "Unable to select next GitHub token from pool" when shields' shared token pool is rate-limited (the static badges on the same line never fail). Render the release badge via shields' endpoint type backed by .github/badges/release.json, which a new workflow updates on 'release: published' — so it never calls the GitHub API at render time. Add cacheSeconds=86400 to the downloads badge to cut its exposure to the same error. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChangelogMarkdown only overrode h2 (small/gray) and let h3 fall through to the browser default (large/bold), inverting the heading hierarchy in the in-app updater dialog — top-level ## sections looked smaller than their ### children. Make h2 the prominent heading and h3 the subdued subheading. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Two small, independent release-experience fixes (one commit each).
1.
fix(badges)— stop the README release/downloads badges from breakingThe
github/v/releaseandgithub/downloadsbadges use shields.io's dynamic GitHub-API endpoints, which intermittently render asUnable to select next GitHub token from poolwhenever shields' shared GitHub token pool is rate-limited. (The static/badge/...license & platform badges on the same line never fail — proof it's a shields-side issue, not ours.)endpointtype, backed by a committed.github/badges/release.json. A new workflow (update-release-badge.yml) rewrites that JSON onrelease: published, so the badge never calls the GitHub API at render time.cacheSeconds=86400, kept dynamic but far less exposed to the same failure.2.
fix(updater)— correct release-notes heading hierarchyChangelogMarkdownonly overrodeh2(rendered small/gray) and leth3fall through to the browser default (large/bold), inverting the hierarchy in the in-app updater dialog — top-level## Highlights/## What's Changedlooked smaller than their### Features/### Fixeschildren. Nowh2is the prominent heading andh3the subdued subheading.Testing
npm run test— 231 passed;tsc --noEmitclean;biome checkclean.🤖 Generated with Claude Code