ci(release): automate releases with release-plz #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/release-plz"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automates releases with release-plz — the Release-PR ceremony, replacing the manual
just release.Flow: feature PR (CI) → merge → release-plz opens a Release PR (version + CHANGELOG from Conventional Commits) → merge it → release-plz tags
vX.Y.Z→release.ymlbuilds + publishes. No hand tagging.release-plz.yml(master push),release-plz.toml(publish=false,v{{version}}tag).release/bump/bump-pre; keptunstable+re-release..DS_Store. Verified release-plz runs locally on this repo; the Forgejo PR/tag step is exercised on the first master push after merge.Replace the manual `just release` (local bump + tag + push, which fought the PR-only trunk flow) with release-plz's Release-PR model: - release-plz.yml (on push to master) opens/updates a Release PR that bumps Cargo.toml + CHANGELOG from Conventional Commits; merging that PR pushes the vX.Y.Z tag, which release.yml builds + publishes. No hand tagging. `--forge gitea`, GIT_TOKEN from FORGEJO_TOKEN. - release-plz.toml: publish=false (app, never crates.io), git_tag_name="v{{version}}" (matches release.yml's tag trigger), git_release_enable=false (release.yml still creates the release + attaches artifacts). - justfile: drop `release`/`bump`/`bump-pre`; keep `unstable` (ad-hoc test cuts) + `re-release`. CLAUDE.md "Release process" rewritten. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>Subsumed into the 0.3.0 giga PR #10 — closing.
Pull request closed