tradeshift/Semantic release

Create a semantic release without choking on registry configs

Trust Signals

name	description	required	default
branches	The branches on which releases should happen. It will override the branches attribute in your configuration file. Support for semantic-release above v16. See https://semantic-release.gitbook.io/semantic-release/usage/configuration#branches for more information.	no	—
branch	The branch on which releases should happen. It will override the branch attribute in your configuration file. If the attribute is not configured on both sides, the default is master. Support for semantic-release older than v16.	no	—
dry_run	Whether to run semantic release in `dry-run` mode. It will override the dryRun attribute in your configuration file	no	—
extends	One or several sharable configurations, https://semantic-release.gitbook.io/semantic-release/usage/configuration#extends	no	—
registry	Override the registry to publish to e.g. npm.pkg.github.com instead of registry.npmjs.com	no	—
npm_publish	Whether to run npm publish as part of semantic-release (default false). Enable to publish package.	no	—
check_name	Will post changelog under this check name if set. Useful w/ dry_run / PRs.	no	—
working_directory	Specify another working directory for semantic release. Default one is provided by github.	no	—

name	description
new_release_published	Whether a new release was published
new_release_version	Version of the new release
new_release_major_version	Major version of the new release
new_release_minor_version	Minor version of the new release
new_release_patch_version	Patch version of the new release
new_release_channel	The distribution channel on which the last release was initially made available (undefined for the default distribution channel).
new_release_notes	The release notes for the new release.