Skip to content

Bump op-node to v1.19.5 (PLAT-740) - #140

Merged
sameersubudhi merged 1 commit into
mainfrom
plat-740-bump-op-node-to-v1195
Aug 21, 2026
Merged

Bump op-node to v1.19.5 (PLAT-740)#140
sameersubudhi merged 1 commit into
mainfrom
plat-740-bump-op-node-to-v1195

Conversation

@sameersubudhi

@sameersubudhi sameersubudhi commented Aug 21, 2026

Copy link
Copy Markdown
Member

Summary

Bumps client version:

Upstream marks it optional, recommended for sequencers — the headline change is sequencer block production (#22241, #22238) plus its same-release freeze fix (#22360), none of which the Lisk image reaches (verifier only, no --sequencer.enabled). op-reth stays at v2.4.2.

Changes

# File Change
1 reth/Dockerfile VERSION=v1.19.4v1.19.5; COMMIT30f5d5836cab8ee44cf118d70831be6d0f0a9d9c
2 README.md op-node client version + release link → v1.19.5

Checks

# Check Result
1 COMMIT pin Matches the dereferenced annotated tag op-node/v1.19.5 (30f5d5836cab8ee44cf118d70831be6d0f0a9d9c)
2 op-node-lisk-sepolia.patch vs v1.19.5 op-node/rollup/derive/system_config.go git apply --check clean (hunk offset +6) — no patch update needed
3 GOLANG_VERSION=1.26 Still aligned with op-node's go.mod (go 1.26.0, toolchain go1.26.5)
4 superchain-registry submodule pin (embedded superchain-configs.zip) Advanced 3d974557715c7d; only removes sepolia-dev-0 devnet configs and registry docs/tooling — lisk and lisk-sepolia untouched
5 just build-superchain-go recipe at v1.19.5 Present
6 Other version references (docker-compose.yml, .env.*, entrypoints, workflows) None
7 op-reth Already at latest upstream (v2.4.2) — no bump

No entrypoint, flag, env or peer-config change; no data migration.

Release

Draft v0.4.27 is staged against main and covers this PR only — v0.4.26 is at main head, so there are no other unreleased changes. Publish after merge.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation

    • Updated the documented op-node client version to v1.19.5.
  • Maintenance

    • Updated the included op-node source to v1.19.5 for improved version consistency.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 40031db5-171c-4dcd-afa0-c9b54f60b87c

📥 Commits

Reviewing files that changed from the base of the PR and between 9522f7d and 50b97fe.

📒 Files selected for processing (2)
  • README.md
  • reth/Dockerfile

Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.


📝 Walkthrough

Walkthrough

The PR updates documented and Docker-build references from op-node v1.19.4 to v1.19.5. The Dockerfile also uses the new pinned commit.

Changes

op-node Version Update

Layer / File(s) Summary
Align op-node version references
README.md, reth/Dockerfile
The README documents op-node v1.19.5. The Dockerfile uses v1.19.5 and commit 30f5d5836cab8ee44cf118d70831be6d0f0a9d9c.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 50b97

This PR only updates the op-node image and documented version from v1.19.4 to v1.19.5 without changing runtime configuration, entrypoints, flags, or data handling; no actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: nazgolze

Poem

A rabbit checks the version line,
Then pins the node commit just right.
From four to five, the docs agree,
The Docker build hops happily.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely identifies the primary change: updating op-node to v1.19.5.
Description check ✅ Passed The description explains the changes and lists validation checks, but it does not use the template headings or explicitly state the problem and test procedure.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch plat-740-bump-op-node-to-v1195

Comment @coderabbitai help to get the list of available commands.

@sameersubudhi sameersubudhi self-assigned this Aug 21, 2026
@sameersubudhi
sameersubudhi requested a review from Nazgolze August 21, 2026 08:41
@sameersubudhi
sameersubudhi enabled auto-merge (squash) August 21, 2026 08:43
@sameersubudhi
sameersubudhi merged commit c74a67f into main Aug 21, 2026
3 checks passed
@sameersubudhi
sameersubudhi deleted the plat-740-bump-op-node-to-v1195 branch August 21, 2026 09:10
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.

2 participants