rmeneely/Git Next Version
Determine the next version based upon last git tag and provided increment
View on GitHubTrust Signals
- Scorecard Score
- Scorecard 2–4scored Jul 6, 2026
- Maintenance Recency
- Stalelast commit Nov 8, 2022
- License
- MIT
Pinned Snippet
uses: rmeneely/git-next-version@137f4036fd148c7faf9d01b3b73e4345b38037f6 # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| tag_pattern | The tag pattern to match | no | v[0-9]*.[0-9]*.[0-9]* |
| increment | The semantic version increment - major, minor, patch, none | no | minor |
| auto_increment | Determine the next version based on commit messages | no | false |
| auto_increment_major_version_pattern | The commit message pattern to match major version commits | no | major:|breaking:|incompatible: |
| auto_increment_minor_version_pattern | The commit message pattern to match minor version commits | no | minor:|feature: |
| auto_increment_limit | The highest level of auto increment allowed - major, minor, patch | no | minor |
| new_prefix | Sets new prefix for the next version | no | "" |
| remove_prefix | Removes last version prefix for the next version | no | false |
| new_suffix | Sets new suffix for the next version | no | "" |
| remove_suffix | Removes last version suffix for the next version | no | false |
| last_version | Defines the last version instead of searching for it | no | "" |
| next_version | Defines the next version instead of calculating it | no | "" |
| set_next_version_tag | Create a version tag of NEXT_VERSION | no | false |
Outputs
| name | description |
|---|---|
| last_version | The LAST_VERSION |
| next_version | The NEXT_VERSION |