docs: name the correct release tool in CLAUDE.md - #30
Merged
Conversation
The Release & Packaging section said `npm run release` bumps the version via standard-version. It does not -- package.json defines the script as `commit-and-tag-version` and carries that package as the devDependency. standard-version was deprecated and commit-and-tag-version is its maintained fork, so the name was probably correct once and went stale across the switch. Harmless until someone tries to look up the tool's configuration or CLI flags, at which point the two projects' docs have diverged enough to mislead. Noticed while rewriting the README in #29, which names the tool correctly. This removes the disagreement between the two files. 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
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
The Release & Packaging section of
CLAUDE.mdsaidnpm run releasebumps the version viastandard-version. It doesn't —package.jsondefines the script ascommit-and-tag-versionand carries that package as the devDependency:standard-versionwas deprecated andcommit-and-tag-versionis its maintained fork, so the name was likely accurate once and went stale across the switch. Harmless until someone tries to look up the tool's configuration or CLI flags — the two projects' docs have diverged enough by now to send you the wrong way.Noticed while rewriting the README in #29, which names the tool correctly. This removes the disagreement between the two files.
What changed
One line in
CLAUDE.md. No code, no behavior change.Verification
package.json— thereleasescript and the devDependency both readcommit-and-tag-versiongrep -i 'standard-version'across the repo returns nothing further; this was the only stale referencenpm run dryrunandnpm run ziplines in that block are accurate and untouched🤖 Generated with Claude Code