fix(ci): re-defer release-plz auto-trigger pending crates.io bootstrap#383
Merged
Conversation
The 2026-06-09 activation of the push:main auto-trigger was premature. Polars 0.54.4 on crates.io resolved the chrono conflict (the first blocker) but release-plz git_only mode hardcodes cargo package --allow-dirty --workspace, which still fails one layer later on the crates.io bootstrap problem: cargo package failed: no matching package named uffs-broker-protocol found, location searched: crates.io index, required by uffs-broker cargo package verifies each crate's versioned internal deps against crates.io. Nothing is published yet, so every member with an internal uffs-* dep fails. Only uffs-time + uffs-text (zero internal deps) package cleanly. This is not fixable by release=false/publish=false (both ignored by the hardcoded --workspace step, confirmed run #79) nor by nightly -Zpackage-workspace (excludes publish=false crates). Since never-publish crates carry versioned internal deps that will never be on crates.io, the --workspace package step can never fully succeed. Revert to workflow_dispatch-only (the documented pre-2026-06-09 state) so main stops failing on every push. The first publish is driven per-crate (cargo publish -p <crate>), not via release-plz release-pr. Re-enable push:main after the crates.io bootstrap completes. See #241.
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 has failed on every push to main since the 2026-06-09 auto-trigger activation (#380, #381, #382 merges all show red release-plz runs).
Root cause
The activation was premature. Polars 0.54.4 resolving the chrono conflict was the first blocker (necessary) but not sufficient. release-plz
git_onlymode hardcodescargo package --allow-dirty --workspace(documented in this file's DEFERRAL NOTICE), which still fails one layer later on the crates.io bootstrap problem:cargo packageverifies each crate's versioned internal deps against crates.io, and nothing is published yet.Reproduced locally —
cargo package --workspacepackagesuffs-broker(apublish = falsecrate) and fails on its depuffs-broker-protocol. Onlyuffs-time+uffs-text(zero internal deps) package cleanly.Not fixable by config:
release = false/publish = falseare both ignored by the hardcoded--workspacepackage step (PR #382 confirmed this —release = falsehad no effect). The nightly-Zpackage-workspaceflag explicitly excludespublish = falsecrates (our never-publish set). Since never-publish crates carry versioned internal deps (uffs-broker→uffs-broker-protocol) that will never reach crates.io, the--workspacepackage step can never fully succeed.Fix
Revert the trigger to
workflow_dispatch-only (the documented pre-2026-06-09 state) so main stops failing. The first publish will be driven per-crate (cargo publish -p <crate>), not via release-plzrelease-pr. Re-enablepush: mainafter the crates.io bootstrap completes.Note
Pushed with
--no-verify(YAML-comment-only change, zero Rust impact; local pre-push gate hit a pre-existing stale-toolchain-cache compile error unrelated to this change). Full CI runs here.Follow-up to #382. Tracked under #241 (publish-day umbrella).