k35o/pnpm Release

Release automation for pnpm's built-in versioning: opens a release PR from pending change intents, then publishes to npm, pushes tags, and creates GitHub Releases when it merges.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
buildCommand to run before the built-in `pnpm publish -r` in publish mode (e.g. `pnpm build`). Skipped when empty. Not run in version-PR mode.no
commit-messageCommit message for the version commit.nochore: prepare release
pr-titleTitle of the release pull request.nochore: prepare release
base-branchBase branch the release PR targets. Defaults to the branch that triggered the workflow; on non-branch triggers (tags, pull_request) it must be set explicitly.no
branch-prefixPrefix of the release branch (`<branch-prefix><base-branch>`).nopnpm-release/
cwdWorking directory of the pnpm workspace.no
setup-git-userGit identity for the version commit: `true` (github-actions bot), `false` (keep the ambient git config), or `app` (resolve the GitHub App bot user from `app-slug`).notrue
app-slugApp slug output of actions/create-github-app-token. Required when `setup-git-user` is `app`.no
create-github-releasesCreate a GitHub Release per released package.notrue
push-git-tagsPush git tags for released packages. Cannot be `false` while `create-github-releases` is `true`.notrue
mode-when-cleanWhat to do when no change intents are pending: `publish` or `none`.nopublish
commit-modeHow the version commit is created: `github-api` (default; GitHub signs the commit as the token's identity, satisfying required-signature rules) or `git-cli` (local commit and force-push).nogithub-api
auto-mergeArm GitHub auto-merge (merge commit) on the release PR.nofalse
sync-lockfileRun `pnpm install --lockfile-only` after versioning.notrue
allow-prerelease-on-latestAllow publishing a prerelease version to the `latest` dist-tag.nofalse
github-tokenToken used for the release PR, tags, and GitHub Releases.no${{ github.token }}
namedescription
modeWhat the run did: `version`, `publish`, or `none`.
published`"true"` when at least one package was published.
published-packagesJSON array of `{ name, version }` for published packages.
has-pending-changes`"true"` when the release plan was non-empty.
pr-numberNumber of the release pull request, when one was created or updated.