mucsi96/Get Next Version
Calculate the next version number based on git tags and source code changes.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Apr 16, 2026
- License
- MIT
Pinned Snippet
uses: mucsi96/get-next-version@a6fd67534c756d65ef2997585c7f2efb14ef1f21 # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| prefix | Tag prefix (e.g. "v" produces tags like v-1, v-2) | yes | — |
| src | Source directory to check for changes | no | . |
| ignore | Space-separated list of paths to ignore when detecting changes | no | "" |
Outputs
| name | description |
|---|---|
| version | The next version number (empty if no changes detected) |
| tag | The next version tag including prefix (e.g. "v-2", empty if no changes detected) |
| hasNextVersion | Whether a new version should be released (true/false) |