PR #5204 incorrectly bumped op.clients.reth.client_version (op-reth image)
from v2.4.3 to v2.5.2. The us-docker.pkg.dev/oplabs-tools-artifacts/images/op-reth
registry has no v2.5.2 tag, causing deploy failures on chains like bob.sepolia
and soneium.mainnet that inherit the default op-reth client without override.
This reverts only the op-reth version change, keeping the intended top-level
reth (ghcr.io/paradigmxyz/reth) bump to v2.5.2 intact.
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
The false default forced every op-node restart to walk back to the finalized head
before driving the EL. On nodes whose derivation lags days behind their serving
gossip head (hashkey us-40: 510k blocks / 12 days), that froze the EL for hours
while dRPC de-routed the sole US provider. true resumes at the unsafe head in
minutes; safe/finalized still verify and catch up in the background. ronin
already ran true per-chain (same lesson); xlayer keeps its deliberate false pin.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
claude
robandClaude Opus 4.8