Last call for testing of MSRV-aware Resolver

announcements
1

We are looking to stabilize this and it would be a big help for people to try it out, giving any feedback on it, including the naming.

At the most basic level, this is

$ rustup update
$ CARGO_RESOLVER_INCOMPATIBLE_RUST_VERSIONS=fallback cargo +nightly -Zmsrv-policy generate-lockfile

For more details, see our call-for-testing issue

5 Likes
2

Slight gotcha (that I didn't expect) is that in a workspace it will pick the oldest MSRV of all the crates. Even if that crate doesn't depend on whatever it is that is downgraded. Eg. in the following virtual workspace:

crates/a (MSRV 1.80.0, depends on tokio)
crates/b (MSRV 1.65.0, does not depend on tokio, even indirectly)
Cargo.lock
Cargo.toml

It will pick a version of tokio that works for 1.65.0 (even though this isn't needed when publishing to crates.io)

That seems a bit broken?

3

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.