docs(cargo): correct stale publishable-set comment (2 crates, not 5)#385
Merged
Conversation
toolchain-sync probes candidate nightlies in a per-candidate scratch
CARGO_TARGET_DIR, then commits the bump and exits without touching the
main caches. Both retain the OLD nightly's artifacts, so the next
build dies with E0514 'found crate X compiled by an incompatible
version of rustc' (observed: assert_cmd/winnow/tempfile/toml_parser).
Two caches must be invalidated, not one:
1. cargo clean — main target/ rlibs/rmeta carry the old rustc
commit-hash; cargo fingerprints do not force a
full rebuild across a nightly bump.
2. sccache --stop-server — the long-lived sccache daemon caches its
compiler-version detection keyed by the rustc
binary mtime/size. Under rustup, rustc is a
toolchain-agnostic proxy (~/.cargo/bin/rustc ->
rustup) whose bytes never change across a bump,
so the daemon keeps serving the OLD nightly's
objects and re-poisons target/ right after a
cargo clean. Restarting forces a fresh rustc -vV
probe. A full 30 GiB cache wipe is unnecessary.
Both run only in the 'found newer nightly' success branch, not the
'no bump available' branch.
cargo metadata --no-deps proves only uffs-text and uffs-time resolve to publish=ANY; the other 17 members are publish=false. The root manifest comment still claimed uffs-broker, uffs-broker-protocol, and uffs-security were publish=true, but all three were since flipped back to publish=false (name-squat reservations / internal-only — see each crate's per-manifest rationale and crates-io-publishability-deep-dive.md 7.3-7.5). Point readers at 'cargo metadata --no-deps' as the live source of truth.
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.
What
The root
Cargo.tomlpublish-policy comment claimed five crates werepublish = true(uffs-broker,uffs-broker-protocol,uffs-security,uffs-text,uffs-time).Why it's wrong
cargo metadata --no-depsis authoritative and shows only two members resolve topublish = ANY:publishuffs-textuffs-time[](publish = false)uffs-broker,uffs-broker-protocol, anduffs-securitywere flipped back topublish = false(publish.workspace = true) with "Intentionally NOT published" rationale (name-squat reservations / internal-only — see each crate's per-manifest comment andcrates-io-publishability-deep-dive.md§7.3–7.5). The root comment was never updated.Change
Comment-only correction in root
Cargo.toml; points readers atcargo metadata --no-depsas the live source of truth. No manifest semantics change.Verification
Full pre-push gate green (cargo-check, lint-tests, tests, lint-ci-windows, deny, vet).