Repository navigation
ci: automate releases with release-plz - #16
Merged
Merged
Conversation
Replace the local cargo-release flow (release.toml, just release recipes) with release-plz running in CI, mirroring the setup proven in rust-ontogen: a bot opens a 'chore: release' PR on pushes to main; merging it tags, publishes to crates.io, and creates a GitHub Release. Changelog generation stays on the existing cliff.toml. See RELEASE.md for the full flow and one-time prerequisites.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the local cargo-release flow with release-plz running in CI, mirroring the setup proven in rust-ontogen.
What changes
release-plz.toml— publish to crates.io on release-PR merge, GitHub Release per release,cargo-semver-checksgate, changelog via the existingcliff.toml..github/workflows/release-plz.yml— runs the release-plz action on every push tomain.release.tomlremoved — cargo-release is retired; one release path only.justfile—release/release-dry-runrecipes dropped;changelogandsemver-checkkept as local previews.RELEASE.md— documents the end-to-end flow and prerequisites.Flow after merge
Push to
main→ bot opens/updates achore: releasePR (version bump + changelog) → merging that PR tagsv{version}, publishes to crates.io, and creates a GitHub Release.Prerequisites
CARGO_REGISTRY_TOKENsecret — not set yet. Needed only at the publish step:gh secret set CARGO_REGISTRY_TOKEN -R sksizer/rust-path-opener.Existing
v{version}tags (latestv0.5.0, matching crates.io) are the baseline release-plz will diff from.