earldata/Create SemVer Tags
Bump and push git tag on merge. Updates additional tags for major/minor versions eg for v1.4.6 it will add/update v1.4 and v1.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | Required for permission to tag the repo. | yes | — |
| default_bump | Which type of bump to use when none explicitly provided (default: `patch`). | no | patch |
| tag_prefix | A prefix to the tag name (default: `v`). | no | v |
| append_to_pre_release_tag | A suffix to a pre-release tag name (default: `<branch>`). | no | — |
| custom_tag | Custom tag name. If specified, it overrides bump settings. | no | — |
| custom_release_rules | Comma separated list of release rules. Format: `<keyword>:<release_type>`. Example: `hotfix:patch,pre-feat:preminor`. | no | — |
| release_branches | Comma separated list of branches (bash reg exp accepted) that will generate the release tags. Other branches and pull-requests generate versions postfixed with the commit hash and do not generate any tag. Examples: `master` or `.*` or `release.*,hotfix.*,master`... | no | master,main |
| pre_release_branches | Comma separated list of branches (bash reg exp accepted) that will generate pre-release tags. | no | — |
| create_annotated_tag | Boolean to create an annotated tag rather than lightweight. | no | false |
| dry_run | Do not perform tagging, just calculate next version and changelog, then exit. | no | false |
Outputs
| name | description |
|---|---|
| new_tag | Generated tag |
| new_version | Generated tag without the prefix |
| previous_tag | Previous tag (or `0.0.0`) |
| changelog | The conventional changelog since the previous tag |