Repository navigation
Update Rust toolchain and dependencies - #66
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.
Summary
Routine toolchain and dependency freshness update.
Toolchain
rustup update stablereports 1.99.1 as the latest stable release, which is already whatrust-toolchainpins. The pinned toolchain is an exact stable version, already current.rust-toolchain(pins1.99.1),Cargo.toml(norust-version/MSRV field),.github/workflows/*.yaml(install the unpinned stable via rustup, no version pinned),install.sh,npm/(no Rust version pins).rust-version): not changed — the project does not declare one, and no upgraded dependency requires a newer compiler.Dependency updates
uuid1.28.0 → 1.29.0 (transitive lockfile update;cargo update). Pulled in through thedebugidchain; no direct dependency inCargo.tomlchanged.Cargo.toml:cargo upgrade --incompatiblereports all 33 direct dependencies already at their latest releases, so noCargo.tomlversion bumps were needed.Cargo.lockregenerated bycargo update(never edited by hand).Code changes
No code changes were required. No compile errors, formatting differences, or new clippy lints surfaced from the toolchain / dependency state.
Verification
cargo build --all-targets— successcargo xfmt --check— cleancargo clippy --all-targets --workspace -- -D warnings— cleancargo test— 34 passed, 0 failed