libafl_{cc,derive}: Bump MSRV to 1.82 for home crate update
#2775
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
With the upcoming 2024 edition we should also set `resolver = "3"` in the workspace's Cargo.toml to opt into a new MSRV-aware dependency resolver. This would fix the breakage we encountered with dependencies that bump their MSRV in a minor version update.
Mrmaxmeier
force-pushed
the
bump-msrv
branch
from
e1112e9 to
00c846a
Compare
Mrmaxmeier
force-pushed
the
bump-msrv
branch
from
00c846a to
651302e
Compare
|
thank you! |
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.
This brings the MSRV in line with the other core crates (
libafl,libafl_bolts), which (sadly) is outside of the "packaged Rust in distros" range (Ubuntu 24.04 is at1.80, 25.04 is at1.81🫠).With the upcoming 2024 edition we should also set
resolver = "3"in the workspace's Cargo.toml at some point to opt into the new MSRV-aware dependency resolver. This would fix the breakage we encountered with dependencies that bump their MSRV in a minor version update.CC #2754