Repository navigation
chore(0.3.2): publish what 0.3.1 did not - #50
Merged
Merged
Conversation
0.3.1 was published from main before #41 merged. The npm tarball got the badge fixes; the repo at the same version number also had the logo, the FAQ, the demo section and the corrected token numbers. Same version string, two different contents — which is its own small instance of the thing this package exists to prevent. This bump makes the published README match the repo again. No code change: 72 tests, 0 vulnerabilities, 0 runtime dependencies. Worth noting for next time, and now written down in CONTRIBUTING: npm renders the README from the published tarball, so a docs change reaches GitHub on merge and npm only on publish. Publishing and merging are not interchangeable, and publishing first silently pins a version number to content that no longer exists anywhere. Co-Authored-By: Claude Opus 5 (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.
0.3.1was published frommainbefore #41 merged. The npm tarball got the badge fixes; the repo at the same version number also had the logo, the FAQ, the demo section and the corrected token numbers.Same version string, two different contents — a small instance of exactly what this package exists to prevent.
0.3.10.3.1This bump makes them match. No code change — 72 tests, 0 vulnerabilities, 0 runtime dependencies.
For next time (now in CONTRIBUTING): npm renders the README from the published tarball, so a docs change reaches GitHub on merge and npm only on publish. Publishing before merging pins a version number to content that exists nowhere.
🤖 Generated with Claude Code