Repository navigation
Update Rust toolchain and dependencies - #62
Merged
Merged
Conversation
This file contains hidden or 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
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.
Toolchain
No change. The project pins
1.99.1inrust-toolchain, which is already the latest stable release (1.99.1, released 2026-10-13).rustup update stablereported no newer version, so nothing was bumped.rust-version(MSRV) is not set inCargo.toml, so it was not changed.Dependency updates
Cargo.toml:tokio = { version = "1.53.3", ... }→"1.54.0".Transitive updates from
cargo update(driven by the tokio bump and fresh registry resolution):rustls-webpkiv0.103.15 → v0.103.16webpki-root-certsv1.0.9 → v1.0.10webpki-rootsv1.0.9 → v1.0.10All other direct dependencies are already at their latest releases (
cargo upgrade --dry-runreported no further changes).Code changes
No code changes were required.
Un-upgraded dependencies
None.