Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update workspace resolver version to 3 #915

Merged
merged 1 commit into from
Feb 24, 2025
Merged

Conversation

edmorley
Copy link
Member

For virtual workspaces (workspaces where there isn't a top level crate, only member crates), there is no top-level Rust edition property from which Cargo can infer its resolver version. Instead, one must specify the resolver version explicitly.

Now we're using Rust 2024 edition (which defaults to resolver version 3 for crates using that edition), we should update the overall workspace resolver version from 2 to 3 for parity with it.

See:
https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions

GUS-W-17894359.

For virtual workspaces (workspaces where there isn't a top level crate,
only member crates), there is no top-level Rust `edition` property from
which Cargo can infer its resolver version. Instead, one must specify the
resolver version explicitly.

Now we're using Rust 2024 edition (which defaults to resolver version
3 for crates using that edition), we should update the overall workspace
resolver version from 2 to 3 for parity with it.

See:
https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions

GUS-W-17894359.
@edmorley edmorley self-assigned this Feb 24, 2025
@edmorley edmorley marked this pull request as ready for review February 24, 2025 11:28
@edmorley edmorley requested a review from a team as a code owner February 24, 2025 11:28
@edmorley edmorley enabled auto-merge (squash) February 24, 2025 11:28
@edmorley edmorley merged commit 108faf1 into main Feb 24, 2025
5 checks passed
@edmorley edmorley deleted the edmorley/resolver-3 branch February 24, 2025 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants