chore: bump MSRV to 1.60.0 #1620
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Why not jump to 1.62.0 (2022-06-30) or 1.62.1 (2022-07-19)? |
|
I went the lowest I could go in this case, just to try and maximize the MSRV window. I can't really think of a reason to support a newer version other than getting new features or our dependencies breaking MSRV. |
WesleyRosenblum
approved these changes
Feb 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of changes:
One of our indirect dependencies (miniz_oxide) now uses a feature from 1.60. Since 1.57 is now over a year old, it's probably time to bump. Otherwise, it's going to be a pain to fix this dependency.
Call-outs:
I went ahead and fixed all of the latest clippy warnings and added a MSRV to the clippy config.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.