Skip to content

fix(docker): pin cryo builder to rust 1.96 - #875

Draft
samcm wants to merge 1 commit into
masterfrom
fix/cryo-rust-pin
Draft

fix(docker): pin cryo builder to rust 1.96#875
samcm wants to merge 1 commit into
masterfrom
fix/cryo-rust-pin

Conversation

@samcm

@samcm samcm commented Jul 12, 2026

Copy link
Copy Markdown
Member

Pins the cryo-builder stage to rust:1.96-bookworm. The floating rust:1-bookworm tag moved to 1.97.0 between the 2026-07-09 and 2026-07-12 release runs, invalidating the cryo-buildcache layer and recompiling cryo under a rustc that rejects the IntErrorKind transmute in ethnum 1.5.0 (error[E0512]), which cryo's --locked lockfile pins. The pin should move together with the next CRYO_GIT_REF bump once cryo's lockfile carries an ethnum that builds on current stable.

Same commit is on release/glamsterdam-devnet-7 (dfbabda). release/glamsterdam-devnet-6 still has the floating tag — its next release tag will hit the same failure unless dfbabda is cherry-picked there (deliberately not pushed, since any push to that branch republishes the rolling image live devnet-6 sentries track).

https://claude.ai/code/session_019cbhUv62kwFTKQD5aM8FGC

rust:1-bookworm moved to 1.97.0 between the devnet-6 (2026-07-09, green)
and devnet-7 (2026-07-12, red) release runs, invalidating the
cryo-buildcache layer and recompiling cryo under a rustc that rejects
ethnum 1.5.0's IntErrorKind transmute (E0512). cryo's --locked install
pins ethnum, so the toolchain was the only floating input. Pin it to the
last-good 1.96 line; revisit alongside the next CRYO_GIT_REF bump.

Claude-Session: https://claude.ai/code/session_019cbhUv62kwFTKQD5aM8FGC
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant