fix: avoid incorrectly unchanged cargo workspace crates#2749
Open
jolars wants to merge 1 commit into
Open
Conversation
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
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.
Fixes #2748
Summary
This PR fixes a manifest-mode bug where a root Rust release candidate (path:
".") could retain workspace member Cargo.toml updates generated by the Rust
strategy, causing member versions to be rewritten to the root version and
diverging from per-path manifest decisions.
What changed
targeting workspace member manifests, while keeping the root Cargo.toml
update.
handling intact.
Tests
Added regression test:
This test verifies root candidates no longer include unintended member
Cargo.toml bumps.