fix(ci): release-plz packages never-publish crates — add release=false#382
Merged
Merged
Conversation
release-plz active run #79 (commit 609f7e6) failed: cargo package failed: no matching package named uffs-broker-protocol found, location searched: crates.io index, required by uffs-broker Root cause: the release-plz.toml comments claimed that publish=false crates are auto-skipped by release-plz. That is wrong. publish=false only blocks the crates.io UPLOAD; release-plz still iterates the crate for version-bump/changelog/tag and runs its baseline cargo package step on it. That step fails for any crate carrying a versioned path-dep on an unpublished workspace member: - uffs-broker -> uffs-broker-protocol - uffs-diag -> uffs-mft + uffs-polars Fix: add explicit release=false blocks for the never-publish crates release-plz was iterating (uffs-broker, uffs-broker-protocol, uffs-security, uffs-diag, uffs-bench) plus the previously-missed CI tool uffs-manifest-audit. This leaves exactly the two publish-ready crates (uffs-time, uffs-text) in release-plz's scope, matching the 2026-05-14 publishability scrub. Corrected the two stale comment blocks that asserted the wrong auto-skip behavior.
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.
Problem
release-plz active run #79 (the merge of #380) failed:
Root cause
The
release-plz.tomlcomments claimedpublish = falsecrates are auto-skipped by release-plz. That is wrong.publish = falseonly blocks the crates.io upload; release-plz still iterates the crate for version-bump/changelog/tag and runs its baselinecargo packagestep on it. That step fails for any crate carrying a versioned path-dep on an unpublished workspace member:uffs-broker→uffs-broker-protocoluffs-diag→uffs-mft+uffs-polarsFix
Add explicit
release = falseblocks for the never-publish crates release-plz was iterating (uffs-broker,uffs-broker-protocol,uffs-security,uffs-diag,uffs-bench) plus the previously-missed CI tooluffs-manifest-audit. This leaves exactly the two publish-ready crates (uffs-time,uffs-text— both dependency-free, package cleanly) in release-plz's scope, matching the 2026-05-14 publishability scrub.Also corrected the two stale comment blocks that asserted the wrong auto-skip behavior (per rule: CI proved the contract wrong → update docs).
Verification
cargo package -p uffs-broker --allow-dirty --no-verifyreproduces the exact failure (even with--no-verify— the error is at metadata-prep, not the verify build).uffs-text/uffs-timehave no internaluffs-*deps → package cleanly.release = false).Follow-up to #380.