zerowiggliness/Another Release Please

Creates or updates a release pull request using another-release-please

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
commandComma-separated list of commands to run in order: release-pr, calculate-next, or release (e.g. "release,release-pr" runs release then release-pr)norelease,release-pr
providerVersion control provider to usenogithub
tokenGitHub token used to interact with the repositoryno${{ github.token }}
repositoryRepository in owner/repo formatno${{ github.repository }}
target-branchTarget branch for the release PR (defaults to the repository default branch)no${{ github.event.repository.default_branch }}
current-branchThe branch that the workflow is currently running on. Used with release-branches to determine whether the action should run.no${{ github.ref_name }}
release-branchesComma-separated list of branch name glob patterns on which releases are permitted (e.g. "master,release/v*,**/release"). When set, the action only runs its commands if the current-branch matches at least one pattern. When unset or empty, the action runs on every branch.no${{ github.event.repository.default_branch }}
pr-branchDestination branch for the pull request. Defaults to target-branch. Use this for GitFlow-style setups where the analyzed branch and the PR destination differ.no
prereleaseCalculate a prerelease versionno
prerelease-calculate-nextCalculate a prerelease version for the calculate-next command. Defaults to the value of the prerelease input when not set.no
dry-runRun without making any changesno
debugEnable detailed debug loggingno
versionerVersioning strategy to useno
version-prefixPrefix for version tags (e.g. "v" produces "v1.2.3")no
issue-url-templateURL template for issue/ticket references. Use {id} as the placeholder (e.g. "https://jira.example.com/browse/{id}"). Default sets to provider specific issue URL (e.g. GitHub issues)no
typeOverride the manifest type for every packageno
use-file-systemUse the local filesystem to scan and read files instead of provider APIs. Reduces API calls and can improve performance, but may not work in all environments (e.g. some CI setups). Requires code to be checked out.notrue
include-choresInclude chore: commits in release eligibility and bump calculationno
update-all-versionsBump every manifest even when no changed files were found under that manifest pathno
write-local(calculate-next only) Write updated version files to the local filesystem instead of committing them to the branchnofalse
namedescription
created'true' if the release command created a release, 'false' otherwise
created-pr'true' if the release-pr command created/updated a pull request, 'false' otherwise
current-versionThe current version at the time of the last version-aware command
next-versionThe next version calculated by the last version-aware command
manifest-current-versionAn array of current versions collected from the manifest file. Each entry is also available as an individual output manifest-current-version-0, manifest-current-version-1, etc.
manifest-next-versionAn array of next versions collected from the manifest file. Each entry is also available as an individual output manifest-next-version-0, manifest-next-version-1, etc.