Skip to content

fix(ci): use simple release-type with workspace-version extra-file - #100

Merged
aram-devdocs merged 1 commit into
mainfrom
fix/release-please-simple-type
Apr 24, 2026
Merged

fix(ci): use simple release-type with workspace-version extra-file#100
aram-devdocs merged 1 commit into
mainfrom
fix/release-please-simple-type

Conversation

@aram-devdocs

Copy link
Copy Markdown
Owner

Summary

Follow-up to #99. Removing the cargo-workspace plugin wasn't enough — the rust release-type itself walks each member's Cargo.toml and rejects version.workspace = true with value at path package.version is not tagged.

Switch the root package to release-type: simple (language-agnostic) and add an extra-files entry that rewrites the single [workspace.package] version = "x.y.z" line in the root Cargo.toml. Workspace inheritance cascades that version to every member crate automatically — release-please only ever has to touch one file.

Test plan

  • Trigger release-please.yml after merge and confirm it either opens a release PR or reports no releasable changes.

🤖 Generated with Claude Code

…ersion

The `rust` release-type walks every workspace member's Cargo.toml and
rejects `version.workspace = true` because it can't read a literal
version there. All Plumb crates inherit the workspace version by design.

Switch to release-type `simple` (single-package, non-language-aware)
and use an `extra-files` entry to rewrite the `[workspace.package]
version` in the root Cargo.toml. Workspace inheritance cascades the
new version to every member automatically.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@aram-devdocs
aram-devdocs merged commit 547aeab into main Apr 24, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant