fix(package): Register workspace member renames in overlay #15228
Merged
epage merged 3 commits intorust-lang:masterfrom Feb 25, 2025
Merged
fix(package): Register workspace member renames in overlay #15228epage merged 3 commits intorust-lang:masterfrom
epage merged 3 commits intorust-lang:masterfrom
Conversation
This was reported at rust-lang#10948 (comment) I suspect there is a second bug here because my debugging only showed us doing this for `val-json` and not `concepts` and only when building `utils`. For the exact mapping between the publish payload and the index, see https://doc.rust-lang.org/cargo/reference/registry-index.html#json-schema, particularly the note about differences.
Collaborator
rustbot
added
Command-package
S-waiting-on-review
4 tasks
weihanglo
approved these changes
Feb 25, 2025
Member
There was a problem hiding this comment.
I suspect there is a second bug here because my debugging only showed us
hitting this scenario forval-jsonand notconceptsand only when buildingutils. That difference in behavior between a transitive and direct dependency is odd.
I think this patch correctly fixes the issue and the transitive-direct difference is the exactly why the behavior. The rename for a direct dependency happens in Cargo.toml, whereas for transitive Cargo consults index files (I didn't double check code logic though).
Anyway, feel free to merge this after fixing the wrongly placed change in the second commit. Thanks for this fix!
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Feb 28, 2025
Update cargo 11 commits in 1d1d646c06a84c1aa53967b394b7f1218f85db82..2622e844bc1e2e6123e54e94e4706f7b6195ce3d 2025-02-21 21:38:53 +0000 to 2025-02-28 12:33:57 +0000 - Bump `cc` to 1.2.16 to fix `x86` windows jobs in rust-lang/rust CI (rust-lang/cargo#15245) - refactor(tree): Abstract the concept of a NodeId (rust-lang/cargo#15237) - feat: implement RFC 3553 to add SBOM support (rust-lang/cargo#13709) - refactor(tree): Abstract the concept of an edge (rust-lang/cargo#15233) - chore: bump openssl to v3 (rust-lang/cargo#15232) - fix(package): Register workspace member renames in overlay (rust-lang/cargo#15228) - Implemented `build.build-dir` config option (rust-lang/cargo#15104) - feat: add completions for `--manifest-path` (rust-lang/cargo#15225) - chore: semver-check build-rs against beta channel (rust-lang/cargo#15223) - chore: depend on openssl-sys to correctly pin its version (rust-lang/cargo#15224) - chore: dont check cargo-util semver until 1.86 is released (rust-lang/cargo#15222)
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
4 participants
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 does this PR try to resolve?
This was reported at #10948 (comment)
For the exact mapping between the publish payload and the index,
see
https://doc.rust-lang.org/cargo/reference/registry-index.html#json-schema,
particularly the note about differences.
How should we test and review this PR?
Additional information
I suspect there is a second bug here because my debugging only showed us
hitting this scenario for
val-jsonand notconceptsand only when buildingutils. That difference in behavior between a transitive and direct dependency is odd.