Use the new v3 resolver for msrv compliant dependency versions #99
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.
A few characteristics of how Rust resolves dependencies were at odds in the workspace:
protocol
library project has a more conservative MSRV policy requirement than theproxy
application.When introducing the regtest library, I ran into an issue where a new transitive dependency of the
protocol
project was having its version bumped due to it also being in theproxy
project's dependency tree. This caused theprotocol
project to fail its MSRV policy.Using
resolver = 3
on rust nightly to set transitive dependency versions in lock file. While setting the workspace's resolver setting to3
, hoping over to the nightly toolchaing, and runningcargo update
is not very maintainable, I am hoping we are not adding too many dependencies to this workspace. Another option is to just run the project on the MSRV toolchain and fix each transitive version by hand and set its version withcargo update ...
. That sounds worse to me.