Skip to content

docs: version in-tree Rust crate families as a group - #23110

Merged
sebastianst merged 1 commit into
developfrom
seb/reth-crate-group-versions
Sep 30, 2026
Merged

sebastianst merged 1 commit into
developfrom
seb/reth-crate-group-versions

Conversation

@sebastianst

Copy link
Copy Markdown
Member

Each in-tree crate family (op-reth and op-alloy) already shares a single version, the same way upstream reth versions all its crates from one workspace version. Until now the docs never said so. As a result, the reth v2.6.0 bump in #23046 moved only reth-optimism-consensus to 2.0.0, while reth-optimism-trie and reth-optimism-rpc also broke their public API and stayed at 1.11.3.

This change makes it a rule in the reth-update procedure: when one crate in a family needs a new version, the whole family moves together. The reth-update review now also flags a bump that moves only part of a family. It is a docs-only change with no effect on users.

The rule deliberately leaves out two groups: kona crates, which are versioned individually, and op-reth-proof-bench, a bench binary.

🤖 Co-created with Claude Opus 5.5

Each in-tree crate family (op-reth, op-alloy) shares one version, like
upstream reth's single workspace version. Require bumping the whole
family together in UPDATING-RETH and have the reth-update review flag
partial-family bumps.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@sebastianst
sebastianst requested a review from a team as a code owner September 30, 2026 12:35
@sebastianst
sebastianst added this pull request to the merge queue Sep 30, 2026
Merged via the queue into develop with commit 9fa52af Sep 30, 2026
103 checks passed
@sebastianst
sebastianst deleted the seb/reth-crate-group-versions branch September 30, 2026 15:15
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