bump-version

Automate a package.json version bump end-to-end by reading and updating the version field, running lint, format, tsc, and tests, then creating a branch, PR, and git release tag. This ensures a clean, auditable software release workflow.

Yes, you can specify an exact version number for your package.json bump. Invoke the command with the target version string appended, and the workflow will update the package.json file accordingly instead of auto-incrementing the patch version.

Pre-flight checks for a package version bump require verifying a clean working tree and confirming you are on the correct branch. The workflow then rebases onto the latest main branch before updating package.json and running quality checks.

Yes, the version bump workflow runs quality checks before creating a release tag. It executes lint, format, and TypeScript checks, followed by the test suite, ensuring code quality passes before branching, committing, and pushing the release tag.

The best way to handle local cleanup after merging a release PR is to reset the local state. The version bump workflow includes a cleanup step that automatically resets your local environment after the pull request is successfully merged.

You need to create a feature branch for a package version bump to maintain an auditable release process. Branching isolates the package.json update, quality checks, and test results before opening a pull request and pushing the final release tag.