bdbch/Rivet Release
Create and update a Rivet version pull request, then publish after it is merged.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | GitHub token used to create branches and pull requests. | no | ${{ github.token }} |
| cwd | Working directory containing the Rivet configuration. | no | . |
| base-branch | Branch receiving the version pull request. Defaults to the branch that triggered the workflow. | no | ${{ github.ref_name }} |
| branch | Branch used for the version pull request. | no | rivet-release |
| check | Command used to determine whether Rivet needs versioning or publishing. | no | pnpm exec rivet check --json |
| version | Command that consumes Rivet release files and creates the release plan. | no | pnpm exec rivet bump |
| publish | Command that builds and publishes packages after the version PR is merged. | no | — |
| commit-message | Commit message used on the version branch. | no | chore: version packages |
| pr-title | Title of the version pull request. | no | chore: version packages |
| setup-git-user | Configure the Git author as github-actions[bot]. | no | true |
Outputs
| name | description |
|---|---|
| published | Whether the publish command ran successfully. |
| has-release | Whether Rivet found release files or a release plan. |
| pull-request-number | Number of the created or updated version pull request. |