Skip to content

Bump the reth group across 1 directory with 7 updates#79

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/reth-a55a4d7ba2
Open

Bump the reth group across 1 directory with 7 updates#79
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/reth-a55a4d7ba2

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 27, 2026 •
edited
Loading

Bumps the reth group with 4 updates in the / directory: reth-evm, reth-exex-types, reth-cli-util and reth-metrics.

Updates reth-evm from v1.11.3 to v2.2.0

Release notes

Sourced from reth-evm's releases.

Reth v2.2.0

image

This release lays the groundwork for Amsterdam (EIP-7928 Block Access Lists), introducing a BAL store abstraction, P2P wire support for fetching BALs alongside full blocks, payload-builder integration, and parallel/batched BAL execution paths. It also enables Discv5 by default, adds snap/2 wire helpers, and bounds the memory footprint of the P2P transaction manager and network channels. Numerous performance improvements land in the trie, database, and re-execution paths, alongside a broad set of correctness fixes in the engine, RPC, networking, and CLI layers.

Action Required: Discv5 is now enabled by default (#23686). If you previously relied on Discv4-only behaviour, review your CLI/config flags. BAL parallel execution and storage prefetch are gated behind CLI flags and are off by default (#23764, #23770).

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.2.x, please downgrade to v2.1.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.

Features

Engine & Payload

  • Suppress persistence during payload building to reduce contention (#23618)
  • Enabled BAL building in the Ethereum payload builder (#23597)
  • New CLI flag to disable BAL storage prefetch (#23770)
  • Added DecodedBal to ExecutionEnv (#23675)

P2P / Networking

  • Discv5 is now enabled by default (#23686)
  • Support binding Discv5 and Discv4 to the same port (#23613)
  • Customizable discovery defaults (#23843)
  • Memory-bounded channel between network and transaction manager (#23802)
  • Bound memory footprint of P2P messages (#23718)
  • Avoid RLP-decoding NewBlock payloads to save CPU (#23712)
  • Added snap/2 wire helpers and messages (#23611)
  • Optionally fetch BAL with full blocks over P2P (#23629)
  • Added BAL requirement to block access list requests (#23682)
  • Enforce BAL response soft limit (#23725)
  • Added basic in-memory BAL store (#23710)
  • Added BAL request e2e coverage (#23727)
  • Scaffolded BAL store abstraction (#23596)

Performance

... (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

Updates reth-exex-types from v1.11.3 to v2.2.0

Release notes

Sourced from reth-exex-types's releases.

Reth v2.2.0

image

This release lays the groundwork for Amsterdam (EIP-7928 Block Access Lists), introducing a BAL store abstraction, P2P wire support for fetching BALs alongside full blocks, payload-builder integration, and parallel/batched BAL execution paths. It also enables Discv5 by default, adds snap/2 wire helpers, and bounds the memory footprint of the P2P transaction manager and network channels. Numerous performance improvements land in the trie, database, and re-execution paths, alongside a broad set of correctness fixes in the engine, RPC, networking, and CLI layers.

Action Required: Discv5 is now enabled by default (#23686). If you previously relied on Discv4-only behaviour, review your CLI/config flags. BAL parallel execution and storage prefetch are gated behind CLI flags and are off by default (#23764, #23770).

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.2.x, please downgrade to v2.1.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.

Features

Engine & Payload

  • Suppress persistence during payload building to reduce contention (#23618)
  • Enabled BAL building in the Ethereum payload builder (#23597)
  • New CLI flag to disable BAL storage prefetch (#23770)
  • Added DecodedBal to ExecutionEnv (#23675)

P2P / Networking

  • Discv5 is now enabled by default (#23686)
  • Support binding Discv5 and Discv4 to the same port (#23613)
  • Customizable discovery defaults (#23843)
  • Memory-bounded channel between network and transaction manager (#23802)
  • Bound memory footprint of P2P messages (#23718)
  • Avoid RLP-decoding NewBlock payloads to save CPU (#23712)
  • Added snap/2 wire helpers and messages (#23611)
  • Optionally fetch BAL with full blocks over P2P (#23629)
  • Added BAL requirement to block access list requests (#23682)
  • Enforce BAL response soft limit (#23725)
  • Added basic in-memory BAL store (#23710)
  • Added BAL request e2e coverage (#23727)
  • Scaffolded BAL store abstraction (#23596)

Performance

... (truncated)

Changelog

Sourced from reth-exex-types'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

Updates reth-execution-types from d6324d6 to 88505c7

Commits

Updates reth-trie from d6324d6 to 88505c7

Commits

Updates reth-ethereum-primitives from d6324d6 to 88505c7

Commits

Updates reth-cli-util from v1.11.3 to v2.2.0

Release notes

Sourced from reth-cli-util's releases.

Reth v2.2.0

image

This release lays the groundwork for Amsterdam (EIP-7928 Block Access Lists), introducing a BAL store abstraction, P2P wire support for fetching BALs alongside full blocks, payload-builder integration, and parallel/batched BAL execution paths. It also enables Discv5 by default, adds snap/2 wire helpers, and bounds the memory footprint of the P2P transaction manager and network channels. Numerous performance improvements land in the trie, database, and re-execution paths, alongside a broad set of correctness fixes in the engine, RPC, networking, and CLI layers.

Action Required: Discv5 is now enabled by default (#23686). If you previously relied on Discv4-only behaviour, review your CLI/config flags. BAL parallel execution and storage prefetch are gated behind CLI flags and are off by default (#23764, #23770).

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.2.x, please downgrade to v2.1.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.

Features

Engine & Payload

  • Suppress persistence during payload building to reduce contention (#23618)
  • Enabled BAL building in the Ethereum payload builder (#23597)
  • New CLI flag to disable BAL storage prefetch (#23770)
  • Added DecodedBal to ExecutionEnv (#23675)

P2P / Networking

  • Discv5 is now enabled by default (#23686)
  • Support binding Discv5 and Discv4 to the same port (#23613)
  • Customizable discovery defaults (#23843)
  • Memory-bounded channel between network and transaction manager (#23802)
  • Bound memory footprint of P2P messages (#23718)
  • Avoid RLP-decoding NewBlock payloads to save CPU (#23712)
  • Added snap/2 wire helpers and messages (#23611)
  • Optionally fetch BAL with full blocks over P2P (#23629)
  • Added BAL requirement to block access list requests (#23682)
  • Enforce BAL response soft limit (#23725)
  • Added basic in-memory BAL store (#23710)
  • Added BAL request e2e coverage (#23727)
  • Scaffolded BAL store abstraction (#23596)

Performance

... (truncated)

Changelog

Sourced from reth-cli-util'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

Updates reth-metrics from v1.11.3 to v2.2.0

Release notes

Sourced from reth-metrics's releases.

Reth v2.2.0

image

This release lays the groundwork for Amsterdam (EIP-7928 Block Access Lists), introducing a BAL store abstraction, P2P wire support for fetching BALs alongside full blocks, payload-builder integration, and parallel/batched BAL execution paths. It also enables Discv5 by default, adds snap/2 wire helpers, and bounds the memory footprint of the P2P transaction manager and network channels. Numerous performance improvements land in the trie, database, and re-execution paths, alongside a broad set of correctness fixes in the engine, RPC, networking, and CLI layers.

Action Required: Discv5 is now enabled by default (#23686). If you previously relied on Discv4-only behaviour, review your CLI/config flags. BAL parallel execution and storage prefetch are gated behind CLI flags and are off by default (#23764, #23770).

Backwards Compatibility

[!IMPORTANT] In case you need to downgrade after running 2.2.x, please downgrade to v2.1.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.

Features

Engine & Payload

  • Suppress persistence during payload building to reduce contention (#23618)
  • Enabled BAL building in the Ethereum payload builder (#23597)
  • New CLI flag to disable BAL storage prefetch (#23770)
  • Added DecodedBal to ExecutionEnv (#23675)

P2P / Networking

  • Discv5 is now enabled by default (#23686)
  • Support binding Discv5 and Discv4 to the same port (#23613)
  • Customizable discovery defaults (#23843)
  • Memory-bounded channel between network and transaction manager (#23802)
  • Bound memory footprint of P2P messages (#23718)
  • Avoid RLP-decoding NewBlock payloads to save CPU (#23712)
  • Added snap/2 wire helpers and messages (#23611)
  • Optionally fetch BAL with full blocks over P2P (#23629)
  • Added BAL requirement to block access list requests (#23682)
  • Enforce BAL response soft limit (#23725)
  • Added basic in-memory BAL store (#23710)
  • Added BAL request e2e coverage (#23727)
  • Scaffolded BAL store abstraction (#23596)

Performance

... (truncated)

Changelog

Sourced from reth-metrics'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

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Apr 27, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 27, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.67%. Comparing base (33bb3c5) to head (df872c6).

Additional details and impacted files 
@@           Coverage Diff           @@
##             main      #79   +/-   ##
=======================================
  Coverage   89.66%   89.67%           
=======================================
  Files          59       59           
  Lines       13557    13557           
=======================================
+ Hits        12156    12157    +1     
+ Misses       1401     1400    -1

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dependabot
Bump the reth group across 1 directory with 7 updates
df872c6 
Bumps the reth group with 4 updates in the / directory: [reth-evm](https://github.com/paradigmxyz/reth), [reth-exex-types](https://github.com/paradigmxyz/reth), [reth-cli-util](https://github.com/paradigmxyz/reth) and [reth-metrics](https://github.com/paradigmxyz/reth).


Updates `reth-evm` from v1.11.3 to v2.2.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d6324d6...88505c7)

Updates `reth-exex-types` from v1.11.3 to v2.2.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d6324d6...88505c7)

Updates `reth-execution-types` from `d6324d6` to `88505c7`
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Commits](paradigmxyz/reth@d6324d6...88505c7)

Updates `reth-trie` from `d6324d6` to `88505c7`
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Commits](paradigmxyz/reth@d6324d6...88505c7)

Updates `reth-ethereum-primitives` from `d6324d6` to `88505c7`
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Commits](paradigmxyz/reth@d6324d6...88505c7)

Updates `reth-cli-util` from v1.11.3 to v2.2.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d6324d6...88505c7)

Updates `reth-metrics` from v1.11.3 to v2.2.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d6324d6...88505c7)

---
updated-dependencies:
- dependency-name: reth-cli-util
  dependency-version: d58c6e3d0723a28f655e89da83c3738e47dcc364
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-ethereum-primitives
  dependency-version: d58c6e3d0723a28f655e89da83c3738e47dcc364
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-evm
  dependency-version: d58c6e3d0723a28f655e89da83c3738e47dcc364
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-execution-types
  dependency-version: d58c6e3d0723a28f655e89da83c3738e47dcc364
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-exex-types
  dependency-version: d58c6e3d0723a28f655e89da83c3738e47dcc364
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-metrics
  dependency-version: d58c6e3d0723a28f655e89da83c3738e47dcc364
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-trie
  dependency-version: d58c6e3d0723a28f655e89da83c3738e47dcc364
  dependency-type: direct:production
  dependency-group: reth
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump the reth group with 7 updates Bump the reth group across 1 directory with 7 updates May 11, 2026
@dependabot dependabot Bot force-pushed the dependabot/cargo/reth-a55a4d7ba2 branch from 00a1565 to df872c6 Compare May 11, 2026 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants