Skip to content

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

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

build(deps): bump the reth group across 1 directory with 8 updates#245
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/reth-4056a05a23

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 15, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

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

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

Release notes

Sourced from reth-chainspec's releases.

Reth v2.4.0

image

Performance

Reth v2.4.0 reduces mean newPayload latency by 6.2% compared with v2.3.0.

Experimental revmc JIT EVM support is added and can be activated with --jit.enabled flag.

Networking and transaction propagation get a large set of throughput-oriented improvements: faster pooled transaction recovery (#26304), cached full transaction propagation encoding (#26012), and multiple ECIES / P2PStream allocation reductions.

Features

We continue with Amsterdam and EIP-7928 Block Access List development.

reth p2p bootnode --v5 now co-locates discv4 and discv5 on a single UDP port (--addr), matching go-ethereum and reth's own networking stack, with IPv4/IPv6 support (#26089)

RPC compatibility was improved with eth_sendRawTransactionSync timeout support, geth-aligned raw transaction handling, empty-proof normalization for eth_getProof, and several eth_simulate, eth_estimateGas, fee-history, and txpool fixes.

ParallelStateRoot deprecation

SDK/library users that depend on trie internals should update usages of ParallelStateRoot, ParallelSparseTrie, and ParallelStateRootError that were removed in this version.

Deployments still passing --engine.legacy-state-root should remove it or use --engine.state-root-fallback if they intentionally need synchronous state-root computation.

Update Priority

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

User Class Priority
Payload Builders High
Non-Payload Builders High

Breaking Changes

Runtime / Configuration

  • Dropped the legacy parallel state-root runtime path; --engine.legacy-state-root is hidden and now only warns if passed, with the sparse trie task as the normal path and serial fallback retained (#26069).

SDK / State Root APIs

  • Refactored state-root strategy APIs to support custom out-of-tree state-root implementations (#26085).
  • Removed ParallelStateRoot; downstream users should migrate to the sparse trie task or the serial fallback path (#26121).
  • Renamed ParallelStateRootError to StateRootTaskError (#26132).
  • Removed ParallelSparseTrie; ArenaParallelSparseTrie is now the default sparse trie implementation used by engine sparse-trie paths (#25453).
  • Changed PayloadValidator::validate_block_post_execution_with_hashed_state to receive a lazy overlay-aware parent-state provider and return PostExecutionValidationError; custom implementations overriding this method must update their signatures (#26330).

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

Updates reth-ethereum-forks from d58c6e3 to 943af24

Commits

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

Release notes

Sourced from reth-ethereum-primitives's releases.

Reth v2.4.0

image

Performance

Reth v2.4.0 reduces mean newPayload latency by 6.2% compared with v2.3.0.

Experimental revmc JIT EVM support is added and can be activated with --jit.enabled flag.

Networking and transaction propagation get a large set of throughput-oriented improvements: faster pooled transaction recovery (#26304), cached full transaction propagation encoding (#26012), and multiple ECIES / P2PStream allocation reductions.

Features

We continue with Amsterdam and EIP-7928 Block Access List development.

reth p2p bootnode --v5 now co-locates discv4 and discv5 on a single UDP port (--addr), matching go-ethereum and reth's own networking stack, with IPv4/IPv6 support (#26089)

RPC compatibility was improved with eth_sendRawTransactionSync timeout support, geth-aligned raw transaction handling, empty-proof normalization for eth_getProof, and several eth_simulate, eth_estimateGas, fee-history, and txpool fixes.

ParallelStateRoot deprecation

SDK/library users that depend on trie internals should update usages of ParallelStateRoot, ParallelSparseTrie, and ParallelStateRootError that were removed in this version.

Deployments still passing --engine.legacy-state-root should remove it or use --engine.state-root-fallback if they intentionally need synchronous state-root computation.

Update Priority

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

User Class Priority
Payload Builders High
Non-Payload Builders High

Breaking Changes

Runtime / Configuration

  • Dropped the legacy parallel state-root runtime path; --engine.legacy-state-root is hidden and now only warns if passed, with the sparse trie task as the normal path and serial fallback retained (#26069).

SDK / State Root APIs

  • Refactored state-root strategy APIs to support custom out-of-tree state-root implementations (#26085).
  • Removed ParallelStateRoot; downstream users should migrate to the sparse trie task or the serial fallback path (#26121).
  • Renamed ParallelStateRootError to StateRootTaskError (#26132).
  • Removed ParallelSparseTrie; ArenaParallelSparseTrie is now the default sparse trie implementation used by engine sparse-trie paths (#25453).
  • Changed PayloadValidator::validate_block_post_execution_with_hashed_state to receive a lazy overlay-aware parent-state provider and return PostExecutionValidationError; custom implementations overriding this method must update their signatures (#26330).

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

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

Release notes

Sourced from reth-evm's releases.

Reth v2.4.0

image

Performance

Reth v2.4.0 reduces mean newPayload latency by 6.2% compared with v2.3.0.

Experimental revmc JIT EVM support is added and can be activated with --jit.enabled flag.

Networking and transaction propagation get a large set of throughput-oriented improvements: faster pooled transaction recovery (#26304), cached full transaction propagation encoding (#26012), and multiple ECIES / P2PStream allocation reductions.

Features

We continue with Amsterdam and EIP-7928 Block Access List development.

reth p2p bootnode --v5 now co-locates discv4 and discv5 on a single UDP port (--addr), matching go-ethereum and reth's own networking stack, with IPv4/IPv6 support (#26089)

RPC compatibility was improved with eth_sendRawTransactionSync timeout support, geth-aligned raw transaction handling, empty-proof normalization for eth_getProof, and several eth_simulate, eth_estimateGas, fee-history, and txpool fixes.

ParallelStateRoot deprecation

SDK/library users that depend on trie internals should update usages of ParallelStateRoot, ParallelSparseTrie, and ParallelStateRootError that were removed in this version.

Deployments still passing --engine.legacy-state-root should remove it or use --engine.state-root-fallback if they intentionally need synchronous state-root computation.

Update Priority

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

User Class Priority
Payload Builders High
Non-Payload Builders High

Breaking Changes

Runtime / Configuration

  • Dropped the legacy parallel state-root runtime path; --engine.legacy-state-root is hidden and now only warns if passed, with the sparse trie task as the normal path and serial fallback retained (#26069).

SDK / State Root APIs

  • Refactored state-root strategy APIs to support custom out-of-tree state-root implementations (#26085).
  • Removed ParallelStateRoot; downstream users should migrate to the sparse trie task or the serial fallback path (#26121).
  • Renamed ParallelStateRootError to StateRootTaskError (#26132).
  • Removed ParallelSparseTrie; ArenaParallelSparseTrie is now the default sparse trie implementation used by engine sparse-trie paths (#25453).
  • Changed PayloadValidator::validate_block_post_execution_with_hashed_state to receive a lazy overlay-aware parent-state provider and return PostExecutionValidationError; custom implementations overriding this method must update their signatures (#26330).

... (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-evm-ethereum from v2.1.0 to v2.4.0

Release notes

Sourced from reth-evm-ethereum's releases.

Reth v2.4.0

image

Performance

Reth v2.4.0 reduces mean newPayload latency by 6.2% compared with v2.3.0.

Experimental revmc JIT EVM support is added and can be activated with --jit.enabled flag.

Networking and transaction propagation get a large set of throughput-oriented improvements: faster pooled transaction recovery (#26304), cached full transaction propagation encoding (#26012), and multiple ECIES / P2PStream allocation reductions.

Features

We continue with Amsterdam and EIP-7928 Block Access List development.

reth p2p bootnode --v5 now co-locates discv4 and discv5 on a single UDP port (--addr), matching go-ethereum and reth's own networking stack, with IPv4/IPv6 support (#26089)

RPC compatibility was improved with eth_sendRawTransactionSync timeout support, geth-aligned raw transaction handling, empty-proof normalization for eth_getProof, and several eth_simulate, eth_estimateGas, fee-history, and txpool fixes.

ParallelStateRoot deprecation

SDK/library users that depend on trie internals should update usages of ParallelStateRoot, ParallelSparseTrie, and ParallelStateRootError that were removed in this version.

Deployments still passing --engine.legacy-state-root should remove it or use --engine.state-root-fallback if they intentionally need synchronous state-root computation.

Update Priority

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

User Class Priority
Payload Builders High
Non-Payload Builders High

Breaking Changes

Runtime / Configuration

  • Dropped the legacy parallel state-root runtime path; --engine.legacy-state-root is hidden and now only warns if passed, with the sparse trie task as the normal path and serial fallback retained (#26069).

SDK / State Root APIs

  • Refactored state-root strategy APIs to support custom out-of-tree state-root implementations (#26085).
  • Removed ParallelStateRoot; downstream users should migrate to the sparse trie task or the serial fallback path (#26121).
  • Renamed ParallelStateRootError to StateRootTaskError (#26132).
  • Removed ParallelSparseTrie; ArenaParallelSparseTrie is now the default sparse trie implementation used by engine sparse-trie paths (#25453).
  • Changed PayloadValidator::validate_block_post_execution_with_hashed_state to receive a lazy overlay-aware parent-state provider and return PostExecutionValidationError; custom implementations overriding this method must update their signatures (#26330).

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

Updates reth-network-peers from d58c6e3 to 943af24

Commits

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

Release notes

Sourced from reth-revm's releases.

Reth v2.4.0

image

Performance

Reth v2.4.0 reduces mean newPayload latency by 6.2% compared with v2.3.0.

Experimental revmc JIT EVM support is added and can be activated with --jit.enabled flag.

Networking and transaction propagation get a large set of throughput-oriented improvements: faster pooled transaction recovery (#26304), cached full transaction propagation encoding (#26012), and multiple ECIES / P2PStream allocation reductions.

Features

We continue with Amsterdam and EIP-7928 Block Access List development.

reth p2p bootnode --v5 now co-locates discv4 and discv5 on a single UDP port (--addr), matching go-ethereum and reth's own networking stack, with IPv4/IPv6 support (#26089)

RPC compatibility was improved with eth_sendRawTransactionSync timeout support, geth-aligned raw transaction handling, empty-proof normalization for eth_getProof, and several eth_simulate, eth_estimateGas, fee-history, and txpool fixes.

ParallelStateRoot deprecation

SDK/library users that depend on trie internals should update usages of ParallelStateRoot, ParallelSparseTrie, and ParallelStateRootError that were removed in this version.

Deployments still passing --engine.legacy-state-root should remove it or use --engine.state-root-fallback if they intentionally need synchronous state-root computation.

Update Priority

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

User Class Priority
Payload Builders High
Non-Payload Builders High

Breaking Changes

Runtime / Configuration

  • Dropped the legacy parallel state-root runtime path; --engine.legacy-state-root is hidden and now only warns if passed, with the sparse trie task as the normal path and serial fallback retained (#26069).

SDK / State Root APIs

  • Refactored state-root strategy APIs to support custom out-of-tree state-root implementations (#26085).
  • Removed ParallelStateRoot; downstream users should migrate to the sparse trie task or the serial fallback path (#26121).
  • Renamed ParallelStateRootError to StateRootTaskError (#26132).
  • Removed ParallelSparseTrie; ArenaParallelSparseTrie is now the default sparse trie implementation used by engine sparse-trie paths (#25453).
  • Changed PayloadValidator::validate_block_post_execution_with_hashed_state to receive a lazy overlay-aware parent-state provider and return PostExecutionValidationError; custom implementations overriding this method must update their signatures (#26330).

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

Updates reth-trie-common from d58c6e3 to 943af24

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels May 15, 2026
@dependabot dependabot Bot changed the title build(deps): bump the reth group with 8 updates build(deps): bump the reth group across 1 directory with 8 updates Jun 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/cargo/reth-4056a05a23 branch from eccbb38 to e07fbf4 Compare June 12, 2026 08:58
@dependabot
build(deps): bump the reth group across 1 directory with 8 updates
c0d45d9 
Bumps the reth group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [reth-chainspec](https://github.com/paradigmxyz/reth) | `v2.1.0` | `v2.4.0` |
| [reth-ethereum-primitives](https://github.com/paradigmxyz/reth) | `v2.1.0` | `v2.4.0` |
| [reth-evm](https://github.com/paradigmxyz/reth) | `v2.1.0` | `v2.4.0` |
| [reth-evm-ethereum](https://github.com/paradigmxyz/reth) | `v2.1.0` | `v2.4.0` |
| [reth-revm](https://github.com/paradigmxyz/reth) | `v2.1.0` | `v2.4.0` |



Updates `reth-chainspec` from v2.1.0 to v2.4.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d58c6e3...943af24)

Updates `reth-ethereum-forks` from `d58c6e3` to `943af24`
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Commits](paradigmxyz/reth@d58c6e3...943af24)

Updates `reth-ethereum-primitives` from v2.1.0 to v2.4.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d58c6e3...943af24)

Updates `reth-evm` from v2.1.0 to v2.4.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d58c6e3...943af24)

Updates `reth-evm-ethereum` from v2.1.0 to v2.4.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d58c6e3...943af24)

Updates `reth-network-peers` from `d58c6e3` to `943af24`
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Commits](paradigmxyz/reth@d58c6e3...943af24)

Updates `reth-revm` from v2.1.0 to v2.4.0
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@d58c6e3...943af24)

Updates `reth-trie-common` from `d58c6e3` to `943af24`
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Commits](paradigmxyz/reth@d58c6e3...943af24)

---
updated-dependencies:
- dependency-name: reth-chainspec
  dependency-version: 88505c7fcbfdebfd3b56d88c86b62e950043c6c4
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-ethereum-forks
  dependency-version: 88505c7fcbfdebfd3b56d88c86b62e950043c6c4
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-ethereum-primitives
  dependency-version: 88505c7fcbfdebfd3b56d88c86b62e950043c6c4
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-evm
  dependency-version: 88505c7fcbfdebfd3b56d88c86b62e950043c6c4
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-evm-ethereum
  dependency-version: 88505c7fcbfdebfd3b56d88c86b62e950043c6c4
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-network-peers
  dependency-version: 88505c7fcbfdebfd3b56d88c86b62e950043c6c4
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-revm
  dependency-version: 88505c7fcbfdebfd3b56d88c86b62e950043c6c4
  dependency-type: direct:production
  dependency-group: reth
- dependency-name: reth-trie-common
  dependency-version: 88505c7fcbfdebfd3b56d88c86b62e950043c6c4
  dependency-type: direct:production
  dependency-group: reth
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/reth-4056a05a23 branch from e07fbf4 to c0d45d9 Compare July 17, 2026 08:58
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