ci: single release PR for both packages - #23
Merged
Conversation
Fold Rust releases into release-please and drop release-plz, so one combined release PR (manifest mode, cargo-workspace plugin) covers @wavekat/flow-schema and wavekat-flow. Merging it publishes whichever packages had releasable commits; tag streams are unchanged (flow-schema-vX.Y.Z / wavekat-flow-vX.Y.Z, both currently at 0.0.2). The crate's version becomes literal in its own Cargo.toml instead of workspace-inherited — release-please's Cargo updater rewrites the package manifest, not [workspace.package]. New cargo-publish job mirrors npm-publish: gated on RELEASE_ENABLED + the crate's release_created output, auth via the org-level CARGO_REGISTRY_TOKEN secret. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0177Rm5YYW6CxrGeABjazVrz
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.
Answers "why two release PRs?" — because npm and Rust each had their own tool (release-please / release-plz). This folds the Rust side into release-please so there is one combined release PR for both packages.
release-please-config.json: addcrates/wavekat-flow(release-type: rust) + thecargo-workspaceplugin (keepsCargo.lockin sync); manifest seeded at0.0.2. Manifest mode combines all packages into a single release PR by default.release-please.yml: newcargo-publishjob mirroringnpm-publish— gated onRELEASE_ENABLED+ the crate'srelease_createdoutput, auth via the org-levelCARGO_REGISTRY_TOKEN.versionis now literal incrates/wavekat-flow/Cargo.toml(was workspace-inherited) — release-please's Cargo updater rewrites the package manifest, not[workspace.package].release-plz.yml+release-plz.toml; tag streams unchanged (flow-schema-vX.Y.Z/wavekat-flow-vX.Y.Z), so changelog compare links keep working against the release-plz-era tags.Versioning stays independent per package (per the roadmap decision) — the combined PR bumps only what changed.
🤖 Generated with Claude Code
https://claude.ai/code/session_0177Rm5YYW6CxrGeABjazVrz