release-plz 0.3.129 (action v0.5.101) is out!
It fixes an issue that was preventing packages to be updated correctly. In particular, if your workspace had packages depending on each other like "A -> B -> C", if C contained changes, only B was updated.
Now A is updated, too 🥳
Release-plz version 0.3.121 is out (GitHub Action version 0.5.95).
It adds support for Rust edition 2024, and most importantly adds colors to the help menu!
• make release --dry-run more informative
• don't update libraries versions on Cargo.lock update
Other
• use tera template to determine the PR body and document the default template
New release-plz version available 🤖
Binary: 0.3.117
GitHub Action: v0.5.91
Here are the main changes we shipped in the last 5 releases:
Added
• add releases to release-pr json output
• allow adding labels to Gitea release PR
Fixed
• don't fail if commit wasn't pushed to remote
• use dunce to canonicalize package paths correctly
• fix release-plz init local dependency check
• stash uncommited changes in dirty repos during the update process to prevent errors
New release-plz version available 🤖
Binary: 0.3.112
GitHub Action: v0.5.87
Fixed
• increment pre-release version correctly when dependencies change
• Fixed wrong link on github token usage for release ci.
Other
• log when a release is skipped because of release_commits
New release-plz version available 🤖
Binary: 0.3.111
GitHub Action: v0.5.86
### Added
- warn if cargo-semver-checks is not installed
- Enable `pr_labels` for GitLab backend
- add `raw_message` to commit context
1/3
The maintainers of @ratatui_rs want to add @release_plz_dev to their release pipeline.
We thought: Why not doing it in public? 😁
Join me and @orhundev on Wed at 20 UTC
👉 https://t.co/GwoWqEO2TC
Hey! 👋 Release-plz is an open source project which automates releases for Rust crates.
This account is managed by the author of release-plz, Marco.
If you want to get involved to help the developer experience of Rust maintainers, check out our good first issues on GitHub!