Skip to content

Bump op-node to v1.19.2#134

Merged
sameersubudhi merged 1 commit into
mainfrom
feature/plat-640
Jul 9, 2026
Merged

Bump op-node to v1.19.2#134
sameersubudhi merged 1 commit into
mainfrom
feature/plat-640

Conversation

@sameersubudhi

@sameersubudhi sameersubudhi commented Jul 9, 2026

Copy link
Copy Markdown
Member

Bumps op-node from v1.19.1 to v1.19.2.

File Change
reth/Dockerfile VERSIONv1.19.2, COMMITda197e45ed44b9fca258b3b0d0709e8dfca1c7cd (peeled op-node/v1.19.2 tag)
README.md version + release-tag URL → v1.19.2

Release: https://github.com/ethereum-optimism/optimism/releases/tag/op-node/v1.19.2

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the documented and build-pinned op-node release to v1.19.2.
    • Refreshed the referenced source commit to match the newer release.
    • The release documentation and build process now point to the latest verified version.

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

coderabbitai Bot commented Jul 9, 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: dbd97c0a-0198-4873-9297-26a7b998c22d

📥 Commits

Reviewing files that changed from the base of the PR and between 0476e26 and 464bc40.

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

📝 Walkthrough

Walkthrough

This PR bumps the pinned op-node dependency version from v1.19.1 to v1.19.2, updating the ENV VERSION and ENV COMMIT values in reth/Dockerfile and the corresponding version reference and link in README.md.

Changes

op-node Version Bump

Layer / File(s) Summary
Update pinned op-node version and commit
reth/Dockerfile
ENV VERSION changed from v1.19.1 to v1.19.2 and ENV COMMIT changed to match the new tag, affecting the git rev-parse verification during build.
Update documented version reference
README.md
The documented op-node source version and release link updated from v1.19.1 to v1.19.2.

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

Possibly related PRs

  • LiskHQ/lisk-node#123: Both PRs update the pinned op-node version/commit in reth/Dockerfile and README.md.
  • LiskHQ/lisk-node#126: Both PRs update ENV VERSION/ENV COMMIT for op-node in reth/Dockerfile and the matching README.md reference.
  • LiskHQ/lisk-node#132: Both PRs bump the pinned op-node ENV VERSION/ENV COMMIT and update README.md accordingly.

Poem

A hop, a skip, a version bump,
v1.19.2 gives my heart a thump!
New commit hash, tidy and neat,
Dockerfile and docs now both complete. 🐇

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description covers the version bump but omits the required problem, solution, and testing sections from the template. Add the template sections: What was the problem?, How was it solved?, and How was it tested?, including the issue number if applicable.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: bumping op-node to v1.19.2.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 feature/plat-640

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

@sameersubudhi sameersubudhi self-assigned this Jul 9, 2026
@sameersubudhi sameersubudhi requested a review from Nazgolze July 9, 2026 07:31
@sameersubudhi sameersubudhi merged commit be59420 into main Jul 9, 2026
3 checks passed
@sameersubudhi sameersubudhi deleted the feature/plat-640 branch July 9, 2026 08:07
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