You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A composite action that wraps changesets/action to version and stage-publish a changesets release, using a bundled release.mjs. createGithubReleases stays off, since a staged version isn't public until .github/actions/promote confirms npm approval.
Inputs
Input
Description
Default
github-token
Token for changesets/action (needs contents: write, pull-requests: write, issues: write)
(required)
commit-message
Commit message for the version-bump commit
ci(changesets): version packages
title
PR title for the version-bump PR
ci(changesets): version packages
Outputs
Output
Description
staged
true if release.mjs staged at least one package
staged_packages
JSON array of {name, version} staged by release.mjs
A composite action that verifies staged package versions are live on npm, tags the release, and creates GitHub Releases, using bundled verifyRegistry.mjs and createReleases.mjs. Runs after a maintainer approves the staged versions on npm and the environment review for the job calling this action.
Inputs
Input
Description
Default
staged-packages
JSON array of {name, version} staged by .github/actions/release
(required)
github-token
Token for gh release create (contents: write)
(required)
release-mode
combined for one release per version (fixed/linked packages), unset/per-package otherwise
(empty, i.e. per-package)
verify-interval-seconds
How often to re-poll npm while waiting for a staged version to propagate
300
verify-retry-attempts
How many times to poll npm before giving up
10
Outputs
Output
Description
approved
true once every staged package is confirmed live on npm