Bump op-node to v1.19.7 and op-reth to v2.4.4 (PLAT-794)

[sameersubudhi]

What was the problem?

This PR resolves PLAT-794.

op-node and op-reth were pinned to v1.19.6 / v2.4.3. Upstream cut op-node/v1.19.7 (optional — production-build dependency cleanup, no runtime change) and op-reth/v2.4.4 (recommended — observability only, adds canonical-head basefee/gas/blob-gas metrics restoring op-geth-equivalent visibility).

Neither release is breaking, and neither needs an env, peer, entrypoint or flag change.

How was it solved?

• reth/Dockerfile — op-node VERSION → v1.19.7, op-reth VERSION → op-reth/v2.4.4, both COMMIT → 7e167ae.
• README.md — client versions and the op-reth source-tree link.

Upstream cut both releases from the same monorepo commit, so the two COMMIT pins share 7e167ae. That value is the peeled commit (refs/tags/<tag>^{}), not the annotated tag object — pinning the tag SHA is what broke the build in PLAT-788, since the Dockerfile asserts git rev-parse HEAD equals COMMIT.

The new op-reth gauges are served on the existing metrics endpoint (host 7301) with no config change. They only advance once the node follows the chain over the Engine API, so they stay flat during snapshot restore and backfill — worth knowing before treating a flat series as a fault.

How was it tested?

CI builds the image on linux/amd64 and linux/arm64, which exercises both clone-and-verify steps and both compilations.

Verified against upstream before pinning:

Check	Result
Tag peeling (git ls-remote ^{})	Both tags peel to commit 7e167ae
op-node-lisk-sepolia.patch	Applies — system_config.go byte-identical across v1.19.6/v1.19.7 (blob 7b368b2)
dockerfile-lisk-sepolia.patch	git apply --check passes (sepolia CI path)
GOLANG_VERSION=1.26	Matches upstream go.mod (go 1.26.0)
RUST_VERSION=1.95	Matches rust/rust-toolchain.toml (channel = "1.95")
superchain-registry submodule	Unchanged at 08d6a44 — lisk / lisk-sepolia resolution untouched

Release draft v0.4.29 is prepared against main and will be published after this merges.

Summary by CodeRabbit

• Documentation

  • Updated documented source versions to Optimism v1.19.7 and op-reth v2.4.4.
  • Refreshed the op-reth source-tree link.

• Chores

  • Updated container builds to use Optimism v1.19.7 and op-reth v2.4.4.
  • Builds now use the corresponding pinned source revision for consistent, reproducible releases.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 39931110-7f84-4222-ac0f-b253e6e52c1a

📥 Commits

Reviewing files that changed from the base of the PR and between 6493784 and 6b72086.

📒 Files selected for processing (2)

• README.md
• reth/Dockerfile

Included review availability: 2 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 Docker build now uses op-node v1.19.7 and op-reth v2.4.4, both pinned to commit 7e167ae2e15b7bf7dfaf238e514155e4bc904ed6. README version and source references match these updates.

Changes

Version pin updates

Layer / File(s)	Summary
Update versions and references reth/Dockerfile, README.md	The Docker build uses op-node v1.19.7 and op-reth v2.4.4 with the specified commit pin. README version and source-tree references use the updated versions.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 6b720

The dependency and documentation updates are consistent and introduce no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely identifies the two dependency updates that are the main changes in the pull request.
Description check	✅ Passed	The description includes all required sections: problem, solution, and testing. It provides specific implementation details, validation results, and the linked issue.
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…
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-794-bump-op-node-to-v1197-and-op-reth-to-v244

---

_{A rabbit checks the version trail
New pins hop into the build
README paths align
Two releases stand in line
The burrow ships with care}

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