degory/Create version number
Compute the next semantic version from the latest Git tag and a checked-in VERSION floor file. Patches come from the tag; a minor/major release is cut by raising the (code-owned) VERSION file in a PR. Pure computation — no tags, no GitHub API, no token.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| version | Explicit version override (e.g. 1.4.0 or v1.4.0). Used verbatim when set, bypassing the tag lookup and the VERSION floor. | no | "" |
| version-file | Path to the VERSION floor file. When it holds a strict X.Y.Z that is higher than the tag-derived patch bump, that version is used — this is how a minor/major release is declared. Missing or non-semver content is ignored (patch bump from the tag). | no | VERSION |
| prerelease | Optional prerelease suffix, appended as -<prerelease> (e.g. a build number). Use for non-release builds so they can never collide with a real release. | no | "" |
| tag-prefix | Tag prefix. | no | v |
Outputs
| name | description |
|---|---|
| tag | Version tag, e.g. v1.4.0 |
| package | Version number without the prefix, e.g. 1.4.0 |
| bump | The bump level relative to the previous release (major | minor | patch | manual) |
| previous-tag | The tag the version was computed from (empty before the first release) |