chore(deps): bump reth-engine-local from v2.5.0 to v2.5.1

[dependabot]

Bumps reth-engine-local from v2.5.0 to v2.5.1.

Release notes

Sourced from reth-engine-local's releases.

Reth v2.5.1

Maintenance Release

• Finalizes pending payload builds when resolved early, preserving accumulated work instead of discarding it.
• Correctly handles whole-storage trie wipes during batched persistence.

Update Priority

If you are running on a low-core machine (<5 cores), the update is mandatory as it fixes a regression.

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

All Changes

• [feat(payload): finalize pending build on resolve (#26759)](paradigmxyz/reth#26759)
• [fix(provider): handle storage wipes in batched persistence (#26750)](paradigmxyz/reth#26750)

Binaries

See pre-built binaries documentation.

The binaries are signed with the PGP key: 50FB 7CC5 5B2E 8AFA 59FE 03B7 AA5E D56A 7FBF 253E

Reth

System	Architecture	Binary	PGP Signature
	x86_64	reth-v2.5.1-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	reth-v2.5.1-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	reth-v2.5.1-aarch64-apple-darwin.tar.gz	PGP Signature
	Docker	paradigmxyz/reth	-

Changelog

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

• 6dec1b9 chore: fix formatting regression
• b7a801d chore: bump versions
• b682925 fix(provider): handle storage wipes in batched persistence (#26750)
• ab93ecc feat(payload): finalize pending build on resolve (#26759)
• See full diff 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.