Update Rust dependencies #588
Open
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.
Summary & Motivation (Problem vs. Solution)
Update some of our Rust dependencies to versions used upstream.
The target versions are determined based on versions that a stable Rust release has picked in one of their
Cargo.lock, as a proxy for reasonably stable and trusted versions. As such, this PR is designed to require only minimal efforts to review the dependencies.Specifically, most of the new crate version picks are based on the Cargo.lock of cargo 0.92.0.
Extra-notable changes:
tokio 1.47.1- the new long term support branchlibc = "=0.2.174"socket 0.6.0How I Tested These Changes
Local tests.
Pre merge check list
There is some general risk of regressions. This PR bumps multiple important crates past SemVer boundaries, such as
tokio.