cargo-bins/Cargo Release PR
Create a PR for a release of a Rust/Cargo crate, using cargo-release
View on GitHubTrust Signals
- Scorecard Score
- Scorecard 4–6scored Jul 6, 2026
- Maintenance Recency
- Activelast commit Jun 19, 2026
- License
- GPL 3.0
- Runtime
- Deprecated runtime
Pinned Snippet
uses: cargo-bins/release-pr@0c019c0e5a6b9f722578d231d43ba900cacc5ffa # v2.1.3tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | GitHub token to interact with the API | yes | — |
| crate-name | Crate to release, if the repo has more than one | no | — |
| crate-path | Path to the crate; defaults to resolving it from workspace | no | — |
| crate-release-all | Release all crates in the workspace | yes | false |
| version | Version to release, or one of the keywords `major`, `minor`, `patch` | yes | — |
| pr-title | Literal or template for the title of the PR | yes | release: <%= crates.length === 1 ? crates[0].name : '' %> v<%= version.actual %> |
| pr-label | Label name to apply to created PR | no | — |
| pr-draft | Create the release PR as Draft | yes | false |
| pr-modifiable | Allow maintainers to modify the release PR | yes | true |
| pr-template | Template for the body of the PR (mutually exclusive with `pr-template-file`) | no | — |
| pr-template-file | Template file for the body of the PR (mutually exclusive with `pr-template`) | no | — |
| pr-merge-strategy | Merge strategy that should be used (`squash`, `merge`, `rebase`, `bors`) | yes | squash |
| pr-release-notes | Include a release notes section in the PR body | yes | false |
| pr-meta-comment | Include release metadata as JSON-in-comment in the PR body | yes | true |
| git-user-name | Name of the git user that will commit the release | yes | github-actions |
| git-user-email | Email of the git user that will commit the release | yes | github-actions@github.com |
| check-semver | Run cargo-semver-checks before committing to the release | yes | false |
| check-package | Run `cargo publish --dry-run` before committing to the release | yes | false |
| base-branch | Name of the PR's base branch (where it will merge). Defaults to repo's default branch. | no | — |
| branch-prefix | Prefix of the release branch created for the PR | yes | release |
Outputs
| name | description |
|---|---|
| pr-branch | Branch name of the release PR |
| pr-url | URL to the release PR |
| version | The version created for the PR |