pzerelles/Changesets
A GitHub action to automate releases with Changesets
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| publish | The command to use to build and publish packages | no | — |
| release | The command to use to release packages | no | — |
| version | The command to update version, edit CHANGELOG, read and delete changesets. Default to `changeset version` if not provided | no | — |
| cwd | Sets the cwd for the node process. Default to `process.cwd()` | no | — |
| commit | The commit message. Default to `Version Packages` | no | — |
| title | The pull request title. Default to `Version Packages` | no | — |
| setupGitUser | Sets up the git user for commits as `"github-actions[bot]"`. Default to `true` | no | true |
| createGithubReleases | A boolean value to indicate whether to create Github releases after `publish` or not | no | true |
| branch | Sets the branch in which the action will run. Default to `github.ref_name` if not provided | no | — |
Outputs
| name | description |
|---|---|
| published | A boolean value to indicate whether a publishing is happened or not |
| publishedPackages | A JSON array to present the published packages. The format is `[{"name": "@xx/xx", "version": "1.2.0"}, {"name": "@xx/xy", "version": "0.8.9"}]` |
| hasChangesets | A boolean about whether there were changesets. Useful if you want to create your own publishing functionality. |
| pullRequestNumber | The pull request number that was created or updated |