jpb06/Bump package version
Bumping package version depending on keywords present in the commit message
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Mar 13, 2026
- License
- None
Pinned Snippet
uses: jpb06/bump-package@17ebfe09aceb4f746cc3dc23e82faa4a63284845 # v2.8.31tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| cwd | Path location of the package to bump. | — | . |
| major-keywords | Keywords triggering a major bump, separated by commas if more than one. | — | [Major]: |
| minor-keywords | Keywords triggering a minor bump, separated by commas if more than one. | — | [Minor]: |
| patch-keywords | Keywords triggering a patch bump, separated by commas if more than one. | — | [Patch]: |
| should-default-to-patch | If no keywords are present in the commits, bump anyway by doing a patch. | — | false |
| commit-user | User for the version bump commit. | — | "" |
| commit-user-email | User email for the version bump commit. | — | "" |
| debug | Debug mode. Will display event github event data. | — | false |
Outputs
| name | description |
|---|---|
| bump-performed | true if package.json has been bumped |
| new-version | Resolved new version |