acsetter/Release Harmonizer

This action creates/updates branches and/or tags that point to the head commit of a new release.

Trust Signals

workflow.ymlSHA-pinned

uses: acsetter/release-harmonizer@4c6b70df3f8edd123e162f70cc71a92e065f1fec # v1.2.7

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
github-token	The GitHub token used to create an authenticated client.	no	${{ github.token }}
ref-type	('tag' \| 'branch') which type of ref to sync.	yes	—
sync-to	('major' \| 'minor' \| 'patch' \| 'full' \| 'all') Determines how refs are synced with the release. For example, if 'major' is specified, versions starting at 1.0.0 and up to, but not including, 2.0.0 will be synced to the same ref. Versions higher than 2.0.0 will create a new ref. Default is 'major'. - 'major' syncs releases [1.0.0, 2.0.0) to the ref '<prefix>1<suffix>' - 'minor' syncs releases [1.1.0, 1.2.0) to the ref '<prefix>1.1<suffix>' - 'patch' syncs releases [2.0.1, 2.0.2) to the ref '<prefix>2.0.1<suffix>' - 'full' syncs release '1.2.3.4' to the ref '<prefix>1.2.3.4<suffix>' - 'all' syncs all releases to the ref '<prefix><suffix>'	no	major
prefix	(string) The prefix for the ref-name. For example, the prefeix 'foo/bar' would produce branches 'foo/bar1', 'foo/bar2', and 'foo/bar3' when synced to major with a ref-type of 'branches'.	no	v
suffix	(string) The suffix for the ref-name. For example, the suffix -latest would produce refs 'v1.0-latest', 'v1.1-latest', and 'v2.2-latest' when synced to minor with the prefix 'v'.	no	""

no outputs