gregorygost/Version Tagger

GitHub Action to automate tag-based version control. For both production and development.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
token	The GitHub Token to use for reference management in the repo	yes	—
version	Version from previous action output. Pattern semver https://semver.org/: `x.y.z`	no	—
uselasttag	Use latest available tag as source version. Applies the latest available tag received from the repository for the source version. If there are no available tags, it takes the version from the base logic: `package.json` file or default version `0.1.0`	no	false
prefix	A prefix that will appear immediately before the tag version. Example: `v` => `v1.0.0`	no	—
postfix	Postfix that will appear immediately after the tag version. Example: `beta` => `v1.0.0-beta.0`	no	—
postfixnoup	Do not apply version upgrade to postfix. No number will be added to the postfix. Example: `v1.0.0-beta`, `2.5.1-rc`	no	false
metadata	Add your own metadata, or use the sliced sha1 version hash.. Example: `build123` or `fyf2c5fr` => `v1.0.0-beta.1+fyf2c5fr`	no	—
releasetype	Release type version. `major`(X.y.z) or `minor`(x.Y.z) or `patch`(x.y.Z). If not specified, then no version will be incremented. All variants: `major`, `premajor`, `minor`, `preminor`, `patch`, `prepatch`, `prerelease`. More in semver doc: https://github.com/npm/node-semver/blob/main/README.md	no	—
auto	Forced version update. DANGEROUS-1!!! May be incorrect because in some cases duplicates the version upgrade. DANGEROUS-2!!! The version in the file may not match what will be in the tags as a result. If `FALSE`, no automatic promotions will be made.	no	false
dryrun	If this value is true, the tag will not be pushed. Use for test this action	no	false

Outputs

name	description
newtag	Output of the resulting tag. Example: `v1.0.0` \| `v1.2.0-beta.5`