[dependabot]

Bumps reth-node-types from v2.8.0 to v2.9.0.

Release notes

Sourced from reth-node-types's releases.

Reth v2.9.0

Reth v2.9.0 replaces revm with evm2 as reth's EVM (#25002). This is a breaking change for SDK users who build on reth's EVM, executor or inspector types. Node operators don't need to change any config.

The release also fixes engine, RPC, storage and pipeline-unwind bugs, adds snap sync progress metrics and JIT support in reth-bb, and makes builds noticeably lighter by cutting monomorphization and unused dependencies. evm2 makes block execution about 10% faster than revm. On 500 mainnet blocks, execution throughput rose +10.0% and median block execution time fell 10.5%. On 300M-gas big blocks, throughput rose 9.3%, and 6.6% with BALs.

Action Required

SDK users: revm types are replaced by evm2 (evm2, evm2-inspectors, evm2-jit). Custom EVMs, precompiles, inspectors and executors need porting to evm2's APIs.

Backwards Compatibility

[!IMPORTANT] You can downgrade to v2.8.1.

Update Priority

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

Breaking Changes

SDK

• Replaced revm with evm2 across execution, RPC and inspectors (#25002, #28127, #28169)
• RPC crates no longer depend on reth-node-api (#28145)

Features

Sync

• Snap sync now reports progress metrics (#28059)

SDK

• reth-bb supports the evm2 JIT (#28140)

Performance

• Faster builds and smaller binaries: less per-table monomorphization in db commands and viewers, type-erased task spawns, and network and config code compiled once (#28111, #28142, #28112, #28141, #28144, #28143)
• DB table handles and metrics are indexed by table position (#28134)
• Lighter dependency tree: smolgen replaces vergen, OTLP builds only with the otlp feature, RocksDB drops unused codecs and jemalloc (#28122, #28124, #28147, #28152, #28108, #28109, #28119, #28110)

Bug Fixes

Engine & EVM

• The precompile cache now survives big-block segments (#28162)
• Recreated account state stays in the execution cache (#28148)

RPC

• Call allowance now reserves blob fees (#28113)

... (truncated)

Changelog

Sourced from reth-node-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

• c9a780f chore: release 2.9.0
• 966010c chore(deps): bump evm2 (#28169)
• a290746 fix(rpc): reserve blob fees in call allowance (#28113)
• f1cc50e feat(trie-dst): checkpoint initialized workers (#28159)
• e0378eb ci(docker): give each target its own cargo cache to stop nightly races (#28166)
• 4c1584b fix(evm): keep precompile cache across big-block segments (#28162)
• 5fc3a81 fix(db): bound safe-no-sync rollback with a sync period (#28163)
• adfcad7 fix(static-file): name segment and anchor in unwind error (#28164)
• 9d0769c ci: replace Cargo Dependabot with a weekly cargo update PR (#28157)
• 482366d chore(deps): bump matplotlib from 3.10.8 to 3.10.9 in /scripts/bench-reth-cha...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: rust. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 675f086e-c4b0-48e0-9dcd-1528cf9e7196

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn