Nemo157

This is mostly a problem for binary packages, but it does also affect library packages in some situations; e.g. it can cause issues when a different resolver is used while...

I'll update this based on the discussion in #10112 tomorrow.

To extract some discussion from #10910: The lint I propose is to emit a warning any time one of the members of a workspace has a different resolver to the...

[`ResolverBehavior::V1.to_manifest() == None`](https://github.com/rust-lang/cargo/blob/015143c4d43147db162454d067881b9b1e452276/src/cargo/core/resolver/types.rs#L124). So this will only upgrade an `edition = "2015"` crate inside a `resolver = "2"` workspace to use `package.resolver = "2"`, it will not downgrade a crate...

> I think it would be good to fix it Great, that should fix all the actual build failures I can see coming from this. > That seems like the...

Interesting, I was confused because I thought I was using this setup in a crate of mine just fine; but it looks like if you use `allsorts?/flate2_rust` it works fine,...

:+1: I want this for a similar reason (including plugin based macros for doc tests on nightly). I also noticed that the [manifest format documentation](http://doc.crates.io/manifest.html) had this in it (emphasis...

> Someone needs to implement minimal-versions-for-me-but-not-my-dependencies and see how it goes from there. I finally got round to figuring out how to do this on my project: ```sh cargo update...

Ah yes, I forgot to mention that you should start with a normal maximal versions lockfile. It also will not correctly update newly added dependencies-of-dependencies to their maximal version, but...

I'm attempting to use this to fix https://github.com/rust-lang/docs.rs/issues/1580 by setting the configured `rustc-args` for all the target and host builds, using this command I expected to see the `--cfg procmacro2_semver_exempt`...