ci(docker): bump pinned rustc to rust:1-bookworm#127
Merged
Conversation
The pinned rust:1.88 fails the release image build — ruint@1.18.0 (and other deps on current main) require rustc >= 1.90. CI uses dtolnay@stable / rust-toolchain.toml channel=stable, so this only surfaced in the Docker build. Track the latest 1.x stable like CI does so MSRV bumps don't break deploys. Already applied on `staging` to unblock the deploy build; this brings `main` in line so the next main→staging promote doesn't reintroduce the pin. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
lai3d
added a commit
that referenced
this pull request
Jun 14, 2026
… rustc bump (#127) for testnet image
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
1 participant
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.
One-line fix: the Dockerfile pinned
rust:1.88-bookworm, butruint@1.18.0(and other deps on currentmain) now require rustc ≥ 1.90, so the release image build fails atcargo chef cook. CI passes because it usesdtolnay/rust-toolchain@stable+rust-toolchain.toml(channelstable), so the gap only shows up in the Docker build.Tracking the latest 1.x stable (
rust:1-bookworm) matches CI's@stableintent and prevents future MSRV bumps from breaking deploys.This was already applied on
staging(commit there) to unblock the deploy image build; this PR bringsmainin line so the nextmain→stagingpromote doesn't reintroduce the1.88pin.🤖 Generated with Claude Code