bahulneel/Package.json Version Bump Action
Automatically bumps versions and updates dependencies in a monorepo or single-package repo using Conventional Commits.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Dec 27, 2025
- License
- MIT
Pinned Snippet
uses: bahulneel/action-version@3e77ea916d9942dc9f05e38c6a43ad6f6e984695 # v0.47.3tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| commit_template | Commit message template for version bumps. | no | chore(release): bump ${package} to ${version} (${bumpType}) |
| dependency_commit_template | Commit message template for dependency updates. | no | chore(deps): update ${depPackage} to ${depVersion} in ${package} (patch) |
| commit_format | Commit format strategy: 'template' (use templates) or 'conventional' (use conventional commit format). | no | conventional |
| create_branch | Create a separate branch for version updates. | no | false |
| branch_template | Template for the branch name when creating branches. | no | release/${version} |
| branch_cleanup | Strategy for cleaning up versioned branches: 'keep' (keep all), 'prune' (keep latest only), or 'semantic' (keep same bump type only). | no | keep |
| base | The base branch to compare commits against. | no | main |
| strategy | Strategy for same-type incremental changes: 'do-nothing' (skip), 'apply-bump' (normal semver), or 'pre-release' (use prerelease versions). | no | do-nothing |
| branch | Active branch for detecting base branch updates and prerelease finalization. | no | develop |
| tag_prereleases | Create git tags for prerelease versions. | no | false |
| release | Release mode: Create a release branch by finalizing prerelease versions. When true, bypasses flow matching and forces: strategy=finalize, create_branch=true, branch_template=release/${version}. Use this for manual release creation. | no | false |
| tactic_mergebase_lookbackcommits | Number of commits to look back when finding merge base (MergeBase tactic). Must be a positive integer. Default 10 to handle merge commits. | no | 10 |
| tactic_lastversioncommit_maxcount | Number of version commits to consider when finding last version change (LastVersionCommit tactic). Must be a positive integer. | no | 1 |
Outputs
| name | description |
|---|---|
| branch | The branch that was created or updated. |
| packages-updated | Number of packages that had their versions updated. |
| releases-created | Number of release versions created. |
| prereleases-created | Number of prerelease versions created. |
| versions-finalized | Number of prerelease versions finalized to releases. |
| test-failures | Number of packages that failed tests during updates. |
| strategy-used | The strategy that was used for version bumping. |
| changes-made | Boolean indicating if any changes were made. |