Repository navigation
docs: use native GitHub release download totals - #168
Merged
Merged
Conversation
Count all release assets, including checksum files, through the native Shields GitHub downloads badge. Keep the localized npm labels and compact number formatting, and remove the custom counter, its tests, and the badge publishing workflow. Verified both localized GitHub badges change from 20k to 24k against 23,968 downloads across 31 published releases. Both npm badges still display 17k, and no references to the custom badge data remain.
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
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.
What
Use the native Shields GitHub total-download badge in both READMEs. The total now includes all published release assets, including checksum files, with the same compact number formatting and localized labels. The npm badges are unchanged.
Remove the custom release counter, its tests, and the scheduled badge publishing workflow. The README no longer depends on the
badgesbranch or a custom JSON endpoint.Why
Counting every release asset makes the native badge sufficient and removes the separate data branch and refresh workflow.
Validation
Live HTTP checks of both English and Chinese badge SVGs produced:
The GitHub API independently reports 23,968 downloads across 31 published releases: 19,634 archive downloads plus 4,334 checksum downloads. The fetched SVGs and comparison JSON are preserved as local verification evidence.
Checklist
git diff --checkpasses.Product code is unchanged; product integration and paid live-provider suites were not rerun. Regular PR CI runs the deterministic suite.
The remote
badgesbranch remains available for the current default-branch README until this PR is merged. It can be removed after the default branch uses the native badge and any old publishing run has finished.