Automating Rust Releases with Release-plz

Releasing a new version of a Rust crate is tedious and error-prone, just like most IT manual tasks. For every package you want to release, you need to:
Check for breaking changes and increase the `Cargo.toml` version accordingly.
Update the changelog.
Publish to [crates.io](https://crates.io).
Create and push the git tag.
Meet release-plz, a Rust open-source project that automates these tasks. It allows maintainers to release Rust packages from CI, saving valuable time and removing the fear of making typos and other careless mistakes typical of manual releases from the terminal. Release-plz makes releasing Rust packages as easy as clicking the pull request 'merge' button.

In this talk, I will show:

How release-plz works.
Why using release-plz (convenience, security, and API breaking change detection)
How you can integrate release-plz in your project.
How you can configure release-plz to fit your use case (e.g., cargo workspaces and build artifacts)

Comments