chore(deps): bump reth-libmdbx from v1.1.2 to v1.3.7

[dependabot]

Bumps reth-libmdbx from v1.1.2 to v1.3.7.

Release notes

Sourced from reth-libmdbx's releases.

Reth v1.3.7

Summary

This release contains a fix for a critical bug introduced in v1.3.6 (#15484), anyone who upgraded to v1.3.6 must upgrade to 1.3.7.

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

See Update Priorities for more information about this table.

All Changes

• chore: release 1.3.7 (#15485)
• fix: set None storage lookup to NotCached (#15484)

Binaries

See pre-built binaries documentation.

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

System	Architecture	Binary	PGP Signature
	x86_64	reth-v1.3.7-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	reth-v1.3.7-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	reth-v1.3.7-x86_64-pc-windows-gnu.tar.gz	PGP Signature
	x86_64	reth-v1.3.7-x86_64-apple-darwin.tar.gz	PGP Signature
	aarch64	reth-v1.3.7-aarch64-apple-darwin.tar.gz	PGP Signature
System	Option	-	Resource
	Docker		paradigmxyz/reth
	Docker (Reproducible)		paradigmxyz/reth-reproducible

Reth v1.3.6

Summary

[!CAUTION] Reth v1.3.6 has a bug which causes block verification to fail. Do not upgrade to v1.3.6 - upgrade to v1.3.7 instead.

Includes fix for opstack eth_simulateV1

... (truncated)

Changelog

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

• ed7da87 chore: release 1.3.7 (#15485)
• 3521c7a fix: set None storage lookup to NotCached (#15484)
• 60ff71b chore: release 1.3.6 (#15483)
• f60f558 fix: actually override simulated (#15482)
• 5658b78 benchmark for blob tx pool truncate (#15461)
• db269f3 docs: Document double option for get_storage method using enum (#15443)
• 6b06fdf chore: rm unused warning (#15474)
• 6086768 feat(examples): add custom NetworkPrimitives and Networkbuilder to custom-nod...
• 98692cf refactor: simplify hardfork determination (#15451)
• b6146e3 chore: bump version 1.3.5 (#15469)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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]

Superseded by #36.