refactor: update MSRV to 1.84, enable MSRV-aware resolver #1078
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.
📬 Issue #, if available:
fixes #1077
✍️ Description of changes:
Bumping our MSRV to 1.84 so that we have access to the MSRV-aware resolver. Also, enabling it at the workspace level.
I didn't go as far as enable 2024 edition, hence explicitly setting resolver = 3 to use the MSRV-aware one anyway.
We are starting to see CI failures due to our dependencies breaking MSRV, and rather than playing whack-a-mole with fixing it, let's do the minimal bump to sidestep this issue.
MSRV 1.8.4 was released about ~11 months ago, so this is fairly conservative (and anybody on older MSRV is already having a very bad time, probably).
🔏 By submitting this pull request
cargo +nightly fmt.cargo clippy --fix.