point to v1.89.0 of the rust toolchain to resolve edition2024 build failure in CI#225
Merged
alexjg merged 2 commits intoautomerge:mainfrom Feb 19, 2026
Merged
Conversation
Contributor
Author
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.
Fix: Update Rust toolchain to 1.85.0
A CI build associated with another PR was failing the
clippyjob due to a transitive dependency (crypto-common v0.2.0-rc.5) requiring Cargo'sedition2024feature, which was not stabilized until Rust 1.85.0.Per the Rust docs,
edition2024requires Rust 1.85.0+.Furthermore, we actually need to bump to 1.89.0 due to an additional error (when attempting to run with 1.85.0):
Changes
Updated the pinned Rust toolchain from
1.81.0to1.89.0in all three CI jobs (automerge-dependencies,rustfmt,clippy).