step-security/Changesets

A GitHub action to automate releases with Changesets

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
github-tokenThe GitHub token to use for authentication. Defaults to the GitHub-provided token.no${{ github.token }}
publishThe command to use to build and publish packagesno
versionThe command to update version, edit CHANGELOG, read and delete changesets. Default to `changeset version` if not providedno
cwdSets the cwd for the node process. Default to `process.cwd()`no
commitThe commit message. Default to `Version Packages` no
titleThe pull request title. Default to `Version Packages`no
setupGitUserSets up the git user for commits as `"github-actions[bot]"`. Default to `true`notrue
createGithubReleasesA boolean value to indicate whether to create Github releases after `publish` or notnotrue
commitModeAn enum to specify the commit mode. Use "git-cli" to push changes using the Git CLI, or "github-api" to push changes via the GitHub API. When using "github-api", all commits and tags are signed using GitHub's GPG key and attributed to the user or app who owns the GITHUB_TOKEN. nogit-cli
branchSets the branch in which the action will run. Default to `github.ref_name` if not providedno
prDraftControls draft PR behavior. Use "create" to create new version PRs as draft, or "always" to also convert existing version PRs back to draft when updating them.no
namedescription
publishedA boolean value to indicate whether a publishing is happened or not
publishedPackagesA JSON array to present the published packages. The format is `[{"name": "@xx/xx", "version": "1.2.0"}, {"name": "@xx/xy", "version": "0.8.9"}]`
hasChangesetsA boolean about whether there were changesets. Useful if you want to create your own publishing functionality.
pullRequestNumberThe pull request number that was created or updated