duplocloud/Duplocloud Version Bump

Duploclouds own version action to bump a semantic version in a Github repo to make a proper release. This will sign commits and generate release notes too.

Trust Signals

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

Inputs

name	description	required	default
version	Bump the version to the specified semantic version. The following special values are supported: major, minor, patch, premajor, preminor, prepatch.	—	patch
headline	The headline of the release. This will be used as the title of the release in Github.	no	—
notes	The notes of the release. This will be added below the changelog and PRs in the release notes. This is good for any static content.	no	—
changelog	The path to the changelog file. If not provided, the action will look for a CHANGELOG.md file in the root of the repository.	—	CHANGELOG.md
files	A list of files or globs to files which should be committed first before bumping the version. This is useful if you want to update the version in multiple files before creating a release. Ultimately the commit the new tag will reference will only have these files as changes.	—	—
push	If the action should push the changes to the repository. If set to false, only the new version will be outputted without making any real changes.	—	false
dist	Path to the folder any generated files should be placed in. The final release notes can be outputed to this directory if needed. By default this is null and any generated file is only in the output of the action.	—	dist
token	The Github token to use for the action. This is required to make changes to the repository. Ideally this is coming from a Github Application using the actions/create-github-app-token@v1 action.	no	—
working-directory	The working directory to run the action in. This is useful if the action should be run in a subdirectory of the repository. For example another repo was cloned one directory down and the action should be run in that directory.	—	.
repository	The repository to push any changes to. A good use case is a homebrew repo where this repo made the formulae changes and the homebrew repo should be updated with a new release as well.	—	${{ github.repository }}

Outputs

name	description
version	The new version foir this release.
tag	The git tag for this release.
previous-version	The previous version of the repository.
previous-tag	The previous git tag of the repository.
release-notes	The generated release notes.