quike/action-semver

Github action to release projects using semantic-release

Trust Signals

name	description	required	default
dry-run	The objective of the dry-run mode is to get a preview of the pending release. Dry-run mode skips the following steps: prepare, publish, addChannel, success and fail. In addition to this it prints the next version and release notes to the console.	no	false
working-path	Working directory where configuration file lives	no	${{ github.workspace }}
debug-mode	Enable verbosity mode	no	false
event-name	Defines the event triggering the run.	—	${{ github.event_name }}
add-summary	Create a GitHub Job Summary.	no	true
default-config	Uses predefined configuration if config files are not present.	no	true
default-preset-info	Enables injection of the action's opinionated presetConfig and releaseRules when a plugin entry declares preset: "custom". The action then swaps the preset back to "conventionalcommits" before semantic-release loads the parser. Any other preset value (conventionalcommits, angular, eslint, ember, …) is passed through to semantic-release untouched. See docs/FAQ.md for details on the "custom" preset policy.	no	true
floating-tags	Create floating tags from major and minor versions after release.	no	false

name	description
release-published	True if a new release is performed, false otherwise.
release-version	New version or current version if not released, example: 1.2.3
release-major	New Major version of the semver, example: 1.
release-minor	New Minor version of the semver, example: .2.
release-patch	New Path version of the semver, example: .3
release-type	Type of semver promotion: major, minor or patch.
release-git-head	SHA value associated to release commit.
release-git-tag	Git Tag associated to release commit.
release-name	Display name of the release (typically the version with optional prefix).