cloudposse/auto-release

Automatically draft release notes for your next release as Pull Requests are merged into main. Optionally, automatically publish a release for every Pull Request.

Trust Signals

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

Inputs

name	description	required	default
token	Standard GitHub token (e.g., secrets.GITHUB_TOKEN)	no	${{ github.token }}
publish	Whether to publish a new release immediately	no	false
prerelease	Boolean indicating whether this release should be a prerelease	no	""
latest	A string indicating whether the release being created or updated should be marked as latest.	no	""
summary-enabled	Enable github action summary.	no	true
config-name	If your workflow requires multiple release-drafter configs it is helpful to override the config-name. The config should still be located inside `.github` as that's where we are looking for config files.	no	configs/draft-release.yml

Outputs

name	description
id	The ID of therelease that was created or updated.
name	The name of the release
tag_name	The name of the tag associated with the release.
body	The body of the drafted release.
html_url	The URL users can navigate to in order to view the release
upload_url	The URL for uploading assets to the release, which could be used by GitHub Actions for additional uses, for example the @actions/upload-release-asset GitHub Action.
major_version	The next major version number. For example, if the last tag or release was v1.2.3, the value would be v2.0.0.
minor_version	The next minor version number. For example, if the last tag or release was v1.2.3, the value would be v1.3.0.
patch_version	The next patch version number. For example, if the last tag or release was v1.2.3, the value would be v1.2.4.
resolved_version	The next resolved version number, based on GitHub labels.
exists	Tag exists so skip new release issue