lando/Prepare Release Action

An action that can automate release steps and sync them back to the releasing repo.

Trust Signals

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

Inputs

name	description	required	default
version	The version of the thing to be released. Must be a semver valid string.	no	${{ github.event.release.tag_name }}
bundle-dependencies	A toggle to autoset bundleDependencies in package.json.	no	false
commands	A list of commands to run to prepare the release.	no	—
lando-plugin	A special easy-mode setting to prepare and valdiate Lando plugins.	no	false
meta	A list of path=value strings to merge into the package.json	no	—
root	The location of the code being prepared for release.	no	${{ github.workspace }}
sync	A toggle to enable/disable code syncing.	no	true
sync-branch	The target branch to use when syncing changes back to the repo .	no	${{ github.event.release.target_commitish \|\| github.event.pull_request.head.ref \|\| github.ref_name }}
sync-email	The email to use when syncing changes back to the repo.	no	41898282+github-actions[bot]@users.noreply.github.com
sync-message	The commit message to use when syncing changes back to the repo.	no	release v%s generated by @lando/prepare-release-action
sync-tags	A list of other tags to sync back to the repo.	no	—
sync-token	A Personal Access Token to use for git sync ops.	yes	${{ github.token }}
sync-username	The username to use when syncing changes back to the repo.	no	github-actions[bot]
update-files	The files to operate on with update-files-meta and update-files-header.	no	—
update-files-header	A header to prepend to update-files after they've been operated on with update-files-meta.	no	—
update-files-meta	The find/replace metadata to be used when updating update-files.	no	—
version-match	A regex to help find the latest tag. Only used when version=dev.	no	v[0-9].*

Outputs

no outputs