feat(resolve): Direct people to working around less optimal MSRV-resolver results #14543
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?
In discussing #14414, the general problem of the resolver picking a
version older than a package needs for its MSRV (or lack of one) because of the MSRV of
other packages came up.
This tries to patch over that problem by telling users that a dependency
might be able to be newer than the resolver selected.
The message is fairly generic and might be misread to be about any MSRV
update which an MSRV
fallback
strategy allows, which would make thecount off.
The reason it is so generic is we don't know with precision why it was
held back
we aren't trying to unify the version requirements across direct
dependents at this time
change
conversation for another day
The user enabled-Zminimal-versions
Note: separate from this, we may also print the status suffix for this
case if the package was not selected for update (e.g. passing
--workspace
).How should we test and review this PR?
Additional information