Skip to content

docs: name the correct release tool in CLAUDE.md - #30

Merged
Herm71 merged 1 commit into
mainfrom
docs/fix-release-tool-name
Aug 4, 2026
Merged

docs: name the correct release tool in CLAUDE.md#30
Herm71 merged 1 commit into
mainfrom
docs/fix-release-tool-name

Conversation

@Herm71

@Herm71 Herm71 commented Aug 4, 2026

Copy link
Copy Markdown
Member

Why

The Release & Packaging section of CLAUDE.md said npm run release bumps the version via standard-version. It doesn't — package.json defines the script as commit-and-tag-version and carries that package as the devDependency:

"scripts":         { "release": "commit-and-tag-version" },
"devDependencies": { "commit-and-tag-version": "^12.0.0" }

standard-version was deprecated and commit-and-tag-version is 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.

-npm run release    # Bump version via standard-version (updates plugin.php header + CHANGELOG.md)
+npm run release    # Bump version via commit-and-tag-version (updates plugin.php header + CHANGELOG.md)

Verification

  • Confirmed against package.json — the release script and the devDependency both read commit-and-tag-version
  • grep -i 'standard-version' across the repo returns nothing further; this was the only stale reference
  • The surrounding npm run dryrun and npm run zip lines in that block are accurate and untouched

🤖 Generated with Claude Code

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>
@Herm71
Herm71 merged commit cc450a8 into main Aug 4, 2026
3 checks passed
@Herm71
Herm71 deleted the docs/fix-release-tool-name branch August 4, 2026 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant