claude-version-bump-reuse

To sync Claude Code version references, update package.json first and then propagate the new version through MACRO.VERSION via src/bootstrapMacro.ts to align code, docs, and CLI outputs across the repository.

Package.json serves as the single source of truth by acting as the authoritative version owner, pushing the defined semver string through bootstrap macros to overwrite all downstream CLI and documentation references.

The best way to verify version consistency is by running bun run version and bun run dev:restore-check --version to confirm the new version string is reflected across CLI entrypoints and documentation outputs.

No, the version propagation path automates CLI entrypoint updates by routing the package.json version through src/bootstrapMacro.ts into MACRO.VERSION, eliminating manual file edits during release bumps.

Docs show a different version because the propagation path from package.json to MACRO.VERSION has not been executed or validated, requiring you to run the synchronization process and verify with bun run version.

This workflow is tailored for Claude Code projects using a specific macro bootstrapping path, so standard semver projects without src/bootstrapMacro.ts may not benefit from this automated synchronization approach.