chore(l1): bump snapsync CL images

[iovoid]

Motivation

In our snapsync job we are CL images that are several months old.

Description

This PR bumps them to the latest version.

[github-actions]

🤖 Kimi Code Review

Review: PR #6894

File: .github/workflows/daily_snapsync.yaml

Assessment: Routine maintenance update — LGTM with minor observations.

Details:

1. Version Updates:

   • Line 117: Lighthouse v8.0.1 → v8.1.3 (minor version bump)
   • Line 167: Prysm v7.1.0 → v7.1.5 (patch version bump)

2. Compatibility Check:

   • Ensure these CL versions support the Engine API version implemented by ethrex (likely V4 for Cancun/Dencun compatibility).
   • Lighthouse v8.1.x includes Electra (Pectra) devnet preparations; verify this doesn't break snap sync against mainnet/testnet targets if the workflow runs against stable networks.

3. Security:

   • Version bumps are positive for security. Both versions include bug fixes from their respective upstream releases.

Recommendation:

• Verify in CI logs that the engine_exchangeCapabilities handshake succeeds after this change.
• Consider pinning to SHA digests instead of floating tags for reproducibility in future PRs if deterministic testing is required.

No blocking issues. This is a standard dependency hygiene update.

---

Automated review by Kimi (Moonshot AI) · kimi-k2.5 · custom prompt

[github-actions]

🤖 Claude Code Review

PR Review: chore(l1): bump snapsync CL images (#6894)

Overview

This is a routine CI maintenance PR that updates two Consensus Layer (CL) client images used in the daily snapsync workflow:

• Lighthouse: v8.0.1 → v8.1.3 (minor version bump)
• Prysm: v7.1.0 → v7.1.5 (patch version bump)

---

Analysis

Correctness

• Both bumps use explicit version tags rather than latest, which is the correct approach for reproducible CI runs.
• The image sources (registry/org) are unchanged: sigp/lighthouse and gcr.io/offchainlabs/prysm/beacon-chain — no supply-chain concerns introduced here.
• Prysm's jump from .0 to .5 is a patch series, so it should be fully backward-compatible. Lighthouse's 8.0.1 → 8.1.3 is a minor bump; lighthouse follows semver loosely but minor releases are generally non-breaking for beacon node operation.

Risk

• Low. Snapsync is a CI job, not production code. A regression would only affect CI runs and would be easily caught and rolled back.
• Keeping CL images reasonably current is important for EL/CL compatibility; the PR motivation (images several months old) is sound.

Minor observation

Consider whether digest pinning (image@sha256:...) would be preferable to tag pinning for supply-chain hardness. Tags are mutable — a registry owner could push a different image under the same tag. This is a low-priority concern for CI-only images and would add maintenance overhead, but worth noting for future policy decisions.

---

Summary

Clean, low-risk maintenance change. No correctness, security, or performance issues. Good to merge.

---

Automated review by Claude (Anthropic) · sonnet · custom prompt

[github-actions]

🤖 Codex Code Review

1. Low: this PR updates the workflow overrides but leaves the composite action’s cl_image default on the old Lighthouse tag at .github/actions/snapsync-run/action.yml:30. Today that default is masked by the explicit override at .github/workflows/daily_snapsync.yaml:117, so there is no immediate regression here, but the PR does introduce version drift: any future caller of ./.github/actions/snapsync-run that relies on the default will silently test sigp/lighthouse:v8.0.1 instead of v8.1.3. I’d either bump the default in the action in the same PR or make cl_image required.

Beyond that, no PR-specific correctness, security, or performance issues stood out. This change is CI-only and does not touch EVM, consensus, state, RLP, or transaction-validation paths. I did not run the workflow itself, so the remaining gap is runtime validation against the new Lighthouse/Prysm images.

---

Automated review by OpenAI Codex · gpt-5.4 · custom prompt

[greptile-apps]

Greptile Summary

This PR bumps two consensus layer client Docker images used in the daily snapsync CI workflow to their latest versions.

• Lighthouse (sigp/lighthouse) is updated from v8.0.1 to v8.1.3.
• Prysm beacon-chain (gcr.io/offchainlabs/prysm/beacon-chain) is updated from v7.1.0 to v7.1.5.

Confidence Score: 5/5

Safe to merge — only two Docker image tags are updated, with no changes to workflow logic, permissions, or scripts.

Both image bumps are minor patch/point releases on well-known consensus client images. The workflow structure, security guards for fork PRs, and notification paths are untouched.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/daily_snapsync.yaml	Bumps Lighthouse CL image from v8.0.1 to v8.1.3 and Prysm beacon-chain image from v7.1.0 to v7.1.5 — no logic changes.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant Trigger as Trigger (schedule/PR/dispatch)
    participant Prepare as prepare job
    participant Engine as engine-restart job
    participant SyncLH as sync-lighthouse job
    participant SyncPrysm as sync-prysm job
    participant Kurtosis as Kurtosis / Docker
    participant Slack as Slack Notification

    Trigger->>Prepare: "compute network matrix & build profile"
    Prepare-->>Engine: outputs ready
    Trigger->>Engine: restart Kurtosis engine
    Engine-->>SyncLH: engine ready
    Engine-->>SyncPrysm: engine ready

    SyncLH->>Kurtosis: run snapsync (sigp/lighthouse:v8.1.3)
    Kurtosis-->>SyncLH: sync result
    SyncLH->>Slack: notify outcome

    SyncPrysm->>Kurtosis: run snapsync (prysm/beacon-chain:v7.1.5)
    Kurtosis-->>SyncPrysm: sync result
    SyncPrysm->>Slack: notify outcome

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant Trigger as Trigger (schedule/PR/dispatch)
    participant Prepare as prepare job
    participant Engine as engine-restart job
    participant SyncLH as sync-lighthouse job
    participant SyncPrysm as sync-prysm job
    participant Kurtosis as Kurtosis / Docker
    participant Slack as Slack Notification

    Trigger->>Prepare: "compute network matrix & build profile"
    Prepare-->>Engine: outputs ready
    Trigger->>Engine: restart Kurtosis engine
    Engine-->>SyncLH: engine ready
    Engine-->>SyncPrysm: engine ready

    SyncLH->>Kurtosis: run snapsync (sigp/lighthouse:v8.1.3)
    Kurtosis-->>SyncLH: sync result
    SyncLH->>Slack: notify outcome

    SyncPrysm->>Kurtosis: run snapsync (prysm/beacon-chain:v7.1.5)
    Kurtosis-->>SyncPrysm: sync result
    SyncPrysm->>Slack: notify outcome

Loading

_{Reviews (1): Last reviewed commit: "ci(l1): bump snapsync CL images" | Re-trigger Greptile}