build(deps): bump the reth group across 1 directory with 8 updates

[dependabot]

Bumps the reth group with 5 updates in the / directory:

Package	From	To
reth-chainspec	v2.1.0	v2.3.0
reth-ethereum-primitives	v2.1.0	v2.3.0
reth-evm	v2.1.0	v2.3.0
reth-evm-ethereum	v2.1.0	v2.3.0
reth-revm	v2.1.0	v2.3.0

Updates reth-chainspec from v2.1.0 to v2.3.0

Release notes

Sourced from reth-chainspec's releases.

Reth v2.3.0

Reth v2.3.0 includes several payload, engine, trie, and transaction-pool performance improvements, including parallel execution work, BAL prewarming, faster proof and trie paths, cheaper transaction-pool insertion, and reduced payload-building overhead. In our benchmark, throughput improved from ~1.4 to ~1.5 Ggas/s, an 8.1% increase.

It also fixes important correctness issues in eth_simulate, proof deserialization, chain-state overlay handling, RLPx buffering, BAL validation, and RocksDB/MDBX handling.

This release continues the Amsterdam / Block Access List rollout with expanded BAL validation, storage, networking, RPC, and payload-builder support. It also adds SSZ proxy coverage for Engine API methods, ERE file support, eth_pendingTransactions, debug account-state RPC endpoints, eth_baseFee, and snapshot overwrite support for reth download --force.

Action Required: SDK users with custom payload, transaction pool, or consensus integrations should review the breaking changes below. Node operators using default configurations do not need migration steps.

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.3.x, please downgrade to v2.2.0.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

See Update Priorities for more information about this table.

Dependencies

Compatible versions:

revm: 40.0.3 alloy-*: 2.0.5 alloy core crates: 1.6.0 alloy-evm: 0.36.0 revm-inspectors: 0.40.1

Breaking Changes

SDK

• Custom built payload types now convert directly into execution data, avoiding reconstruction from sealed blocks during local payload submission (#23928).
• EthBuiltPayload now stores the recovered block instead of a sealed-only block, keeping recovered sender data available to downstream payload users (#24403).
• TransactionPool::mark_invalid now takes an owned InvalidPoolTransactionError instead of a reference, allowing invalid transaction errors to cross thread boundaries cleanly (#24121).
• Consensus opaque error handling uses a single Other(Arc<dyn Error + Send + Sync>) path with constructor and downcast helpers (#23669).
• State hooks are now configured at the State<DB> level, ensuring everything committed to the database is propagated to the hook (#24654).
• In-memory state trie overlay ownership moved into reth-chain-state behind StateTrieOverlayManager; provider/tree wiring resolves managed overlays instead of carrying lazy overlay handles through engine state (#24184).

RPC

... (truncated)

Changelog

Sourced from reth-chainspec's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

• Create a new branch (e.g. release/vx.y.z) and open a pull request for it
• Ensure all tests and lints pass for the chosen commit
• Version bump
  • Update the version in all Cargo.toml's
• Commit the changes
  • The message format should be release: vx.y.z, substituting x.y.z for the semver.
• The PR should be reviewed to see if anything was missed
• Once reviewed, merge the PR

Releasing

• Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
• Push the tag (git push origin vx.y.z)[^1]
• Update Homebrew Tap
• Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
  • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

• A summary of the release (highlights etc.)
• The update priority (see below)
• An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits

• 9384bc5 chore(release): bump version to 2.3.0 (#25071)
• 9f2837e feat(revm): add CachedReads account capacity constructor (#25048)
• 8919e67 chore(deps): bump revm-inspectors to 0.40.1 (#25047)
• 01cbe9b fix(rlpx): bound mux outbound buffer fairly (#25031)
• e5fd762 perf(transaction-pool): specialize same-origin batch insertion (#25037)
• 3a22037 feat(net): add outbound peer rotation to prevent slot saturation (#24776)
• 84d8e47 fix(chain-state): avoid state overlay cache deadlock (#24875)
• a3482df fix(chain-state): publish deferred trie data from task (#24995)
• 949834a fix(cli): target reth download --force cleanup (#25015)
• 72fafb5 fix: remove precompile cache initial capacity (#25013)
• Additional commits viewable in compare view

Updates reth-ethereum-forks from d58c6e3 to 9384bc5

Commits

• 9384bc5 chore(release): bump version to 2.3.0 (#25071)
• 9f2837e feat(revm): add CachedReads account capacity constructor (#25048)
• 8919e67 chore(deps): bump revm-inspectors to 0.40.1 (#25047)
• 01cbe9b fix(rlpx): bound mux outbound buffer fairly (#25031)
• e5fd762 perf(transaction-pool): specialize same-origin batch insertion (#25037)
• 3a22037 feat(net): add outbound peer rotation to prevent slot saturation (#24776)
• 84d8e47 fix(chain-state): avoid state overlay cache deadlock (#24875)
• a3482df fix(chain-state): publish deferred trie data from task (#24995)
• 949834a fix(cli): target reth download --force cleanup (#25015)
• 72fafb5 fix: remove precompile cache initial capacity (#25013)
• Additional commits viewable in compare view

Updates reth-ethereum-primitives from v2.1.0 to v2.3.0

Release notes

Sourced from reth-ethereum-primitives's releases.

Reth v2.3.0

Reth v2.3.0 includes several payload, engine, trie, and transaction-pool performance improvements, including parallel execution work, BAL prewarming, faster proof and trie paths, cheaper transaction-pool insertion, and reduced payload-building overhead. In our benchmark, throughput improved from ~1.4 to ~1.5 Ggas/s, an 8.1% increase.

It also fixes important correctness issues in eth_simulate, proof deserialization, chain-state overlay handling, RLPx buffering, BAL validation, and RocksDB/MDBX handling.

This release continues the Amsterdam / Block Access List rollout with expanded BAL validation, storage, networking, RPC, and payload-builder support. It also adds SSZ proxy coverage for Engine API methods, ERE file support, eth_pendingTransactions, debug account-state RPC endpoints, eth_baseFee, and snapshot overwrite support for reth download --force.

Action Required: SDK users with custom payload, transaction pool, or consensus integrations should review the breaking changes below. Node operators using default configurations do not need migration steps.

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.3.x, please downgrade to v2.2.0.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

See Update Priorities for more information about this table.

Dependencies

Compatible versions:

revm: 40.0.3 alloy-*: 2.0.5 alloy core crates: 1.6.0 alloy-evm: 0.36.0 revm-inspectors: 0.40.1

Breaking Changes

SDK

• Custom built payload types now convert directly into execution data, avoiding reconstruction from sealed blocks during local payload submission (#23928).
• EthBuiltPayload now stores the recovered block instead of a sealed-only block, keeping recovered sender data available to downstream payload users (#24403).
• TransactionPool::mark_invalid now takes an owned InvalidPoolTransactionError instead of a reference, allowing invalid transaction errors to cross thread boundaries cleanly (#24121).
• Consensus opaque error handling uses a single Other(Arc<dyn Error + Send + Sync>) path with constructor and downcast helpers (#23669).
• State hooks are now configured at the State<DB> level, ensuring everything committed to the database is propagated to the hook (#24654).
• In-memory state trie overlay ownership moved into reth-chain-state behind StateTrieOverlayManager; provider/tree wiring resolves managed overlays instead of carrying lazy overlay handles through engine state (#24184).

RPC

... (truncated)

Changelog

Sourced from reth-ethereum-primitives's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

• Create a new branch (e.g. release/vx.y.z) and open a pull request for it
• Ensure all tests and lints pass for the chosen commit
• Version bump
  • Update the version in all Cargo.toml's
• Commit the changes
  • The message format should be release: vx.y.z, substituting x.y.z for the semver.
• The PR should be reviewed to see if anything was missed
• Once reviewed, merge the PR

Releasing

• Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
• Push the tag (git push origin vx.y.z)[^1]
• Update Homebrew Tap
• Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
  • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

• A summary of the release (highlights etc.)
• The update priority (see below)
• An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits

• 9384bc5 chore(release): bump version to 2.3.0 (#25071)
• 9f2837e feat(revm): add CachedReads account capacity constructor (#25048)
• 8919e67 chore(deps): bump revm-inspectors to 0.40.1 (#25047)
• 01cbe9b fix(rlpx): bound mux outbound buffer fairly (#25031)
• e5fd762 perf(transaction-pool): specialize same-origin batch insertion (#25037)
• 3a22037 feat(net): add outbound peer rotation to prevent slot saturation (#24776)
• 84d8e47 fix(chain-state): avoid state overlay cache deadlock (#24875)
• a3482df fix(chain-state): publish deferred trie data from task (#24995)
• 949834a fix(cli): target reth download --force cleanup (#25015)
• 72fafb5 fix: remove precompile cache initial capacity (#25013)
• Additional commits viewable in compare view

Updates reth-evm from v2.1.0 to v2.3.0

Release notes

Sourced from reth-evm's releases.

Reth v2.3.0

Reth v2.3.0 includes several payload, engine, trie, and transaction-pool performance improvements, including parallel execution work, BAL prewarming, faster proof and trie paths, cheaper transaction-pool insertion, and reduced payload-building overhead. In our benchmark, throughput improved from ~1.4 to ~1.5 Ggas/s, an 8.1% increase.

It also fixes important correctness issues in eth_simulate, proof deserialization, chain-state overlay handling, RLPx buffering, BAL validation, and RocksDB/MDBX handling.

This release continues the Amsterdam / Block Access List rollout with expanded BAL validation, storage, networking, RPC, and payload-builder support. It also adds SSZ proxy coverage for Engine API methods, ERE file support, eth_pendingTransactions, debug account-state RPC endpoints, eth_baseFee, and snapshot overwrite support for reth download --force.

Action Required: SDK users with custom payload, transaction pool, or consensus integrations should review the breaking changes below. Node operators using default configurations do not need migration steps.

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.3.x, please downgrade to v2.2.0.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

See Update Priorities for more information about this table.

Dependencies

Compatible versions:

revm: 40.0.3 alloy-*: 2.0.5 alloy core crates: 1.6.0 alloy-evm: 0.36.0 revm-inspectors: 0.40.1

Breaking Changes

SDK

• Custom built payload types now convert directly into execution data, avoiding reconstruction from sealed blocks during local payload submission (#23928).
• EthBuiltPayload now stores the recovered block instead of a sealed-only block, keeping recovered sender data available to downstream payload users (#24403).
• TransactionPool::mark_invalid now takes an owned InvalidPoolTransactionError instead of a reference, allowing invalid transaction errors to cross thread boundaries cleanly (#24121).
• Consensus opaque error handling uses a single Other(Arc<dyn Error + Send + Sync>) path with constructor and downcast helpers (#23669).
• State hooks are now configured at the State<DB> level, ensuring everything committed to the database is propagated to the hook (#24654).
• In-memory state trie overlay ownership moved into reth-chain-state behind StateTrieOverlayManager; provider/tree wiring resolves managed overlays instead of carrying lazy overlay handles through engine state (#24184).

RPC

... (truncated)

Changelog

Sourced from reth-evm's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

• Create a new branch (e.g. release/vx.y.z) and open a pull request for it
• Ensure all tests and lints pass for the chosen commit
• Version bump
  • Update the version in all Cargo.toml's
• Commit the changes
  • The message format should be release: vx.y.z, substituting x.y.z for the semver.
• The PR should be reviewed to see if anything was missed
• Once reviewed, merge the PR

Releasing

• Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
• Push the tag (git push origin vx.y.z)[^1]
• Update Homebrew Tap
• Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
  • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

• A summary of the release (highlights etc.)
• The update priority (see below)
• An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits

• 9384bc5 chore(release): bump version to 2.3.0 (#25071)
• 9f2837e feat(revm): add CachedReads account capacity constructor (#25048)
• 8919e67 chore(deps): bump revm-inspectors to 0.40.1 (#25047)
• 01cbe9b fix(rlpx): bound mux outbound buffer fairly (#25031)
• e5fd762 perf(transaction-pool): specialize same-origin batch insertion (#25037)
• 3a22037 feat(net): add outbound peer rotation to prevent slot saturation (#24776)
• 84d8e47 fix(chain-state): avoid state overlay cache deadlock (#24875)
• a3482df fix(chain-state): publish deferred trie data from task (#24995)
• 949834a fix(cli): target reth download --force cleanup (#25015)
• 72fafb5 fix: remove precompile cache initial capacity (#25013)
• Additional commits viewable in compare view

Updates reth-evm-ethereum from v2.1.0 to v2.3.0

Release notes

Sourced from reth-evm-ethereum's releases.

Reth v2.3.0

Reth v2.3.0 includes several payload, engine, trie, and transaction-pool performance improvements, including parallel execution work, BAL prewarming, faster proof and trie paths, cheaper transaction-pool insertion, and reduced payload-building overhead. In our benchmark, throughput improved from ~1.4 to ~1.5 Ggas/s, an 8.1% increase.

It also fixes important correctness issues in eth_simulate, proof deserialization, chain-state overlay handling, RLPx buffering, BAL validation, and RocksDB/MDBX handling.

This release continues the Amsterdam / Block Access List rollout with expanded BAL validation, storage, networking, RPC, and payload-builder support. It also adds SSZ proxy coverage for Engine API methods, ERE file support, eth_pendingTransactions, debug account-state RPC endpoints, eth_baseFee, and snapshot overwrite support for reth download --force.

Action Required: SDK users with custom payload, transaction pool, or consensus integrations should review the breaking changes below. Node operators using default configurations do not need migration steps.

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.3.x, please downgrade to v2.2.0.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

See Update Priorities for more information about this table.

Dependencies

Compatible versions:

revm: 40.0.3 alloy-*: 2.0.5 alloy core crates: 1.6.0 alloy-evm: 0.36.0 revm-inspectors: 0.40.1

Breaking Changes

SDK

• Custom built payload types now convert directly into execution data, avoiding reconstruction from sealed blocks during local payload submission (#23928).
• EthBuiltPayload now stores the recovered block instead of a sealed-only block, keeping recovered sender data available to downstream payload users (#24403).
• TransactionPool::mark_invalid now takes an owned InvalidPoolTransactionError instead of a reference, allowing invalid transaction errors to cross thread boundaries cleanly (#24121).
• Consensus opaque error handling uses a single Other(Arc<dyn Error + Send + Sync>) path with constructor and downcast helpers (#23669).
• State hooks are now configured at the State<DB> level, ensuring everything committed to the database is propagated to the hook (#24654).
• In-memory state trie overlay ownership moved into reth-chain-state behind StateTrieOverlayManager; provider/tree wiring resolves managed overlays instead of carrying lazy overlay handles through engine state (#24184).

RPC

... (truncated)

Changelog

Sourced from reth-evm-ethereum's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

• Create a new branch (e.g. release/vx.y.z) and open a pull request for it
• Ensure all tests and lints pass for the chosen commit
• Version bump
  • Update the version in all Cargo.toml's
• Commit the changes
  • The message format should be release: vx.y.z, substituting x.y.z for the semver.
• The PR should be reviewed to see if anything was missed
• Once reviewed, merge the PR

Releasing

• Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
• Push the tag (git push origin vx.y.z)[^1]
• Update Homebrew Tap
• Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
  • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

• A summary of the release (highlights etc.)
• The update priority (see below)
• An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits

• 9384bc5 chore(release): bump version to 2.3.0 (#25071)
• 9f2837e feat(revm): add CachedReads account capacity constructor (#25048)
• 8919e67 chore(deps): bump revm-inspectors to 0.40.1 (#25047)
• 01cbe9b fix(rlpx): bound mux outbound buffer fairly (#25031)
• e5fd762 perf(transaction-pool): specialize same-origin batch insertion (#25037)
• 3a22037 feat(net): add outbound peer rotation to prevent slot saturation (#24776)
• 84d8e47 fix(chain-state): avoid state overlay cache deadlock (#24875)
• a3482df fix(chain-state): publish deferred trie data from task (#24995)
• 949834a fix(cli): target reth download --force cleanup (#25015)
• 72fafb5 fix: remove precompile cache initial capacity (#25013)
• Additional commits viewable in compare view

Updates reth-network-peers from d58c6e3 to 9384bc5

Commits

• 9384bc5 chore(release): bump version to 2.3.0 (#25071)
• 9f2837e feat(revm): add CachedReads account capacity constructor (#25048)
• 8919e67 chore(deps): bump revm-inspectors to 0.40.1 (#25047)
• 01cbe9b fix(rlpx): bound mux outbound buffer fairly (#25031)
• e5fd762 perf(transaction-pool): specialize same-origin batch insertion (#25037)
• 3a22037 feat(net): add outbound peer rotation to prevent slot saturation (#24776)
• 84d8e47 fix(chain-state): avoid state overlay cache deadlock (#24875)
• a3482df fix(chain-state): publish deferred trie data from task (#24995)
• 949834a fix(cli): target reth download --force cleanup (#25015)
• 72fafb5 fix: remove precompile cache initial capacity (#25013)
• Additional commits viewable in compare view

Updates reth-revm from v2.1.0 to v2.3.0

Release notes

Sourced from reth-revm's releases.

Reth v2.3.0

Reth v2.3.0 includes several payload, engine, trie, and transaction-pool performance improvements, including parallel execution work, BAL prewarming, faster proof and trie paths, cheaper transaction-pool insertion, and reduced payload-building overhead. In our benchmark, throughput improved from ~1.4 to ~1.5 Ggas/s, an 8.1% increase.

It also fixes important correctness issues in eth_simulate, proof deserialization, chain-state overlay handling, RLPx buffering, BAL validation, and RocksDB/MDBX handling.

This release continues the Amsterdam / Block Access List rollout with expanded BAL validation, storage, networking, RPC, and payload-builder support. It also adds SSZ proxy coverage for Engine API methods, ERE file support, eth_pendingTransactions, debug account-state RPC endpoints, eth_baseFee, and snapshot overwrite support for reth download --force.

Action Required: SDK users with custom payload, transaction pool, or consensus integrations should review the breaking changes below. Node operators using default configurations do not need migration steps.

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.3.x, please downgrade to v2.2.0.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

See Update Priorities for more information about this table.

Dependencies

Compatible versions:

revm: 40.0.3 alloy-*: 2.0.5 alloy core crates: 1.6.0 alloy-evm: 0.36.0 revm-inspectors: 0.40.1

Breaking Changes

SDK

• Custom built payload types now convert directly into execution data, avoiding reconstruction from sealed blocks during local payload submission (#23928).
• EthBuiltPayload now stores the recovered block instead of a sealed-only block, keeping recovered sender data available to downstream payload users (#24403).
• TransactionPool::mark_invalid now takes an owned InvalidPoolTransactionError instead of a reference, allowing invalid transaction errors to cross thread boundaries cleanly (#24121).
• Consensus opaque error handling uses a single Other(Arc<dyn Error + Send + Sync>) path with constructor and downcast helpers (#23669).
• State hooks are now configured at the State<DB> level, ensuring everything committed to the database is propagated to the hook (#24654).
• In-memory state trie overlay ownership moved into reth-chain-state behind StateTrieOverlayManager; provider/tree wiring resolves managed overlays instead of carrying lazy overlay handles through engine state (#24184).

RPC

... (truncated)

Changelog

Sourced from reth-revm's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

• Create a new branch (e.g. release/vx.y.z) and open a pull request for it
• Ensure all tests and lints pass for the chosen commit
• Version bump
  • Update the version in all Cargo.toml's
• Commit the changes
  • The message format should be release: vx.y.z, substituting x.y.z for the semver.
• The PR should be reviewed to see if anything was missed
• Once reviewed, merge the PR

Releasing

• Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
• Push the tag (git push origin vx.y.z)[^1]
• Update Homebrew Tap
• Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
  • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

• A summary of the release (highlights etc.)
• The update priority (see below)
• An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits

• 9384bc5 chore(release): bump version to 2.3.0 (#25071)
• 9f2837e feat(revm): add CachedReads account capacity constructor (#25048)
• 8919e67 chore(deps): bump revm-inspectors to 0.40.1 (#25047)
• 01cbe9b fix(rlpx): bound mux outbound buffer fairly (#25031)
• e5fd762 perf(transaction-pool): specialize same-origin batch insertion (#25037)
• 3a22037 feat(net): add outbound peer rotation to prevent slot saturation (#24776)
• 84d8e47 fix(chain-state): avoid state overlay cache deadlock (#24875)
• a3482df fix(chain-state): publish deferred trie data from task (#24995)
• 949834a fix(cli): target reth download --force cleanup (#25015)
• 72fafb5 fix: remove precompile cache initial capacity (#25013)
• Additional commits viewable in compare view

Updates reth-trie-common from d58c6e3 to 9384bc5

Commits

• 9384bc5 chore(release): bump version to 2.3.0 (#25071)
• 9f2837e feat(revm): add CachedReads account capacity constructor (#25048)
• 8919e67 chore(deps): bump revm-inspectors to 0.40.1 (#25047)
• 01cbe9b fix(rlpx): bound mux outbound buffer fairly (#25031)
• e5fd762 perf(transaction-pool): specialize same-origin batch insertion (#25037)
• 3a22037 feat(net): add outbound peer rotation to prevent slot saturation (#24776)
• 84d8e47 fix(chain-state): avoid state overlay cache deadlock (#24875)
• a3482df fix(chain-state): publish deferred trie data from task (#24995)
• 949834a fix(cli): target reth download --force cleanup (#25015)
• 72fafb5 fix: remove precompile cache initial capacity (#25013)
• Additional commits viewable in compare view