actions-marketplace-validations/Git Semantic Version (via branches)

Determines version of a repo based on git history

Trust Signals

name	description	required	default
test_value	Set to specify what patterns are applied against	yes	.
use_test_value	Look at `test_value` to derive how the version is bumped, instead of commit messages	yes	false
branch	Set to specify a specific branch, default is the current HEAD	yes	HEAD
tag_prefix	The prefix to use to identify tags	no	v
major_pattern	A string which, if present in a git commit, indicates that a change represents a major (breaking) change. Wrap with '/' to match using a regular expression.	yes	(MAJOR)
minor_pattern	A string which, if present in a git commit, indicates that a change represents a minor (feature) change. Wrap with '/' to match using a regular expression.	yes	(MINOR)
format	Pattern to use when formatting output version	yes	${major}.${minor}.${patch}
change_path	Path to check for changes. If any changes are detected in the path the 'changed' output will true. Enter multiple paths separated by spaces.	no	—
namespace	Use to create a named sub-version. This value will be appended to tags created for this version.	no	—
short_tags	If false, only full versions, i.e. 'v1.0.0', will be supported as tags. If true, tags will support truncated minor and patch versions such as 'v1' (default).	yes	true
bump_each_commit	If true, every commit will be treated as a bump to the version.	yes	false

name	description
major	Current major number
minor	Current minor number
patch	Current patch number
increment	An additional value indicating the number of commits for the current version
version	The version result, in the format {major}.{minor}.{patch}
version_tag	The version tag
changed	Indicates whether there was a change since the last version if change_path was specified. If no change_path was specified this value will always be true since the entire repo is considered.