chrispsheehan/Get Next Release
Compute the next semver tag from commit subject prefixes since the latest semver tag
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| subjects | Optional PR title or newline-delimited commit subjects to classify instead of reading git history | no | "" |
| major_prefixes | Comma-separated custom commit types that trigger a major bump. Conventional Commit breaking markers such as feat!:, fix(scope)!:, and BREAKING CHANGE: are handled automatically. | no | "" |
| minor_prefixes | Comma-separated commit subject prefixes that trigger a minor bump | no | feat |
| patch_prefixes | Comma-separated commit subject prefixes that trigger a patch bump | no | fix |
| release_bumps | Comma-separated bump levels that create a full release | no | major,minor,patch |
| tag_prefix | Optional prefix for semver tags, for example v for tags like v1.2.3 | no | "" |
| major_alias | Whether to output a moving major-version alias for non-zero major releases, for example v1 | no | false |
Outputs
| name | description |
|---|---|
| version | Next semver tag when a matching commit exists, otherwise the current tag |
| createNewTag | Whether a new semver tag should be created |
| createNewRelease | Whether the resolved bump level should create a full release |
| currentVersion | Latest semver tag discovered on the current branch, or 0.0.1 with the configured prefix if none exists |
| majorAlias | Moving major-version alias for the resolved version, for example v1, or empty when disabled or below 1.0.0 |
| createMajorAlias | Whether the moving major-version alias should be created or updated |
| bump | Resolved bump level: major, minor, patch, or empty when no matching commit exists |