release-please-plus/release-please-plus-action

automated releases based on conventional commits

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stalelast commit Jul 17, 2023
License
Apache 2.0
Runtime
Deprecated runtime

Pinned Snippet

workflow.ymlSHA-pinned
uses: release-please-plus/action@9c672cd1bcec347f9f37916dc8cdff8361529bf4 # v1

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
tokenGitHub token for creating and grooming release PRs, defaults to using secrets.GITHUB_TOKENno${{ github.token }}
forkshould the PR be proposed from a fork, Default to falsenofalse
cleanShould stale release PRs be closed post release? Defaults to truenotrue
package-namename of the distributions releases are being created for, e.g., "name" in package.json, or "setup.py"no
release-typewhat type of release is this, one of (ruby, python, node, terraform-module)yes
bump-minor-pre-majorshould breaking changes before 1.0.0 produce minor bumpsnofalse
bump-patch-for-minor-pre-majorshould feat changes before 1.0.0 produce patch bumps instead of minor bumpsnofalse
pathcreate a release from a path other than the repository's rootno""
changelog-pathspecify a CHANGELOG path other than the root CHANGELOG.mdno""
changelog-hostThe proto://host where commits live.no${{ github.server_url }}
commandrelease-please command to run, either "github-release", or "release-pr" (defaults to running both)no""
version-fileprovide a path to a version file to increment (used by ruby releaser)no""
extra-filesextra files to bump using the generic updaterno""
default-branchbranch to open pull release PR against (detected by default)no""
changelog-typeschanglelog commit typesno""
config-filewhere can the config file be found in the project?no""
manifest-filewhere can the manifest file be found in the project?no""
signoffAdd [`Signed-off-by`](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff) line at the end of the commit log message using the user and email provided. (format "Name \<email@example.com\>")no""
github-api-urlconfigure github API URL. Default `https://api.github.com`no${{ github.api_url }}
github-graphql-urlconfigure github GraphQL URL. Default `https://api.github.com`no${{ github.graphql_url }}
repo-urlconfigure github repository URL. Default `process.env.GITHUB_REPOSITORY`no""
monorepo-tagsadd prefix to tags and branches, allowing multiple libraries to be released from the same repositorynofalse
pull-request-title-patternadd title pattern to make release PR, defaults to using "chore${scope}: release${component} ${version}"no
pull-request-headerset release PR header, defaults to using ":robot: I have created a release *beep* *boop*"no
draftmark release as a draftno
draft-pull-requestmark pull request as a draftno
changelog-notes-typeStrategy for building the changelog contents(see https://github.com/googleapis/release-please/blob/main/docs/customizing.md#changelog-types). Default `default`. Called `changelog-type` in release-please documentation.no
versioning-strategyOverride method of determining SemVer version bumps based on commits (drr https://github.com/googleapis/release-please/blob/main/docs/customizing.md#versioning-strategies). Default `default`no
release-asmanually set version to this value, ignoring conventional commits. Absence defaults to conventional commits derived next version. Once the release PR is merged you should either remove this or update it to a higher version. Otherwise subsequent `manifest-pr` runs will continue to use this version even though it was already set in the last release.no
skip-github-releaseSkip creating GitHub Releases. Default `false`no
prereleaseIf set, create releases that are pre-major or pre-release version marked as pre-release on Github. Defaults `false`no
componentname of the component used for branch naming and release tagging, defaults to a normalized version based on the package nameno
include-v-in-taginclude "v" in tag versions. Default `true`no
tag-separatorconfigures separator character used in release tagno
snapshot-labelssets java snapshot pull request labels other than `autorelease: snapshot` no
bootstrap-shaif this is the first time running `manifest-pr` on a repo this key will limit how far back (exclusive) to pull commits for conventional commit parsing (see the manifest releaser docs https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md)no
last-release-shaoverrides the commit sha release-please will use from which to gather commits for the current release (see the manifest releaser docs https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md)no
always-link-localwhen using the `node-workspace` plugin, setting to false will only bump your local dependencies within the SemVer range (see the manifest releaser docs)[https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md) . Default `true`.no
separate-pull-requestscreate separate pull requests for each package instead of a single manifest release pull request (see the manifest releaser docs https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md). Default `false`.no
pluginssee https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md#pluginsno
labelslist of labels to apply to the release pull requests, defaults to `autorelease: pending`no
release-labelsset a pull request label other than `autorelease: tagged`no
skip-labelingif set, labels will not be applied to pull requests. Default `false`.no
sequential-callsissue GitHub API requests sequentially rather than concurrently (see the manifest releaser docs https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md). Default `false`no
group-pull-request-title-patternsets the manifest pull request title for when releasing multiple packages grouped together in the one pull requestno
release-search-depthwhen searching for the latest release SHAs, only consider the last N releasesno
commit-search-depthwhen fetching the list of commits to consider, only consider the last N commitsno
proxy-serverset proxy sever when you run this action behind a proxy. format is host:port e.g. proxy-host.com:8080no

no outputs