froozeify/Release Semver Autotag
Automatically create/update semantic versioning shortcut tags (1, 1.2 / v1, v1.2) when a release is published
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 22, 2026
- License
- MIT
Pinned Snippet
uses: froozeify/gh-release-semver-autotag@637f4583693b9dd50b5670cb11a1dc75745cb49b # v1.0.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| token | GitHub token with contents:write permission | no | ${{ github.token }} |
| mode | Tagging mode: - semver (default) create/update prefix-stripped shortcut tags: 1, 1.2 - prefix create/update prefixed shortcut tags using the tag's own prefix (e.g. v1, v1.2) - both do both — creates 1, 1.2 and v1, v1.2 | no | semver |
| tag-prefix | Fallback prefix used in prefix/both mode when the release tag itself has no prefix (e.g. tag 1.2.3, uses this to build v1, v1.2) | no | v |
| prerelease-strategy | How to handle prerelease tags (e.g. v1.2.3-beta.1): - skip (default) do not update shortcut tags for prerelease versions - include update shortcut tags for prerelease versions too | no | skip |
| dry-run | Set to true to log what would happen without actually creating or updating any tag | no | false |
Outputs
| name | description |
|---|---|
| created-tags | Comma-separated list of tags that were created |
| updated-tags | Comma-separated list of tags that were updated |
| skipped | true if the action was skipped (non-semver tag, prerelease with skip strategy, or nothing to do) |