chore: add release-plz workflow for automated releases#33
Open
chore: add release-plz workflow for automated releases#33
Conversation
Frando
force-pushed
the
chore/release-please
branch
from
22a78ad to
2acd044
Compare
Automates version bumping, changelog generation (using the existing cliff.toml), and crates.io publishing. On every push to main, release-plz creates or updates a release PR. Merging the PR creates a GitHub Release with tag and publishes to crates.io. Only the patchbay crate is released. Other workspace members (runner, vm, cli, server, utils) are excluded. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Frando
force-pushed
the
chore/release-please
branch
from
2acd044 to
8028fe0
Compare
Frando
changed the title
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
1 participant
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.
Adds a release-plz workflow that automates the release process. On every push to main, release-plz scans conventional commits and maintains a release PR with version bumps, changelog updates (using the existing cliff.toml format), and lockfile changes. Merging that PR creates a GitHub Release and publishes to crates.io.
Only the patchbay crate is released. Other workspace members (runner, vm, cli, server, utils) are excluded via release-plz.toml.
Requires one secret: CARGO_REGISTRY_TOKEN (crates.io API token) in the repo settings. GITHUB_TOKEN is automatic.
Replaces the manual workflow of creating a release-prep branch, running cargo-cliff, bumping versions, and running cargo-release.