Bump reth-db from v1.0.6 to v1.1.2

[dependabot]

Bumps reth-db from v1.0.6 to v1.1.2.

Release notes

Sourced from reth-db's releases.

Reth v1.1.2

Summary

This release contains performance improvements and bug fixes.

• feat(payload) : optimize new payload job by fetching only header hash instead of block (#12343)
• feat: mev_simBundle (#12218)
• fix: pending transaction ordering (#12382)

OP-Reth

This release is holocene hardfork ready

• fix: consume all payload variants (paradigmxyz/reth#12520)
• feat(spec): Holocene activation time for {OP/Base} Sepolia (paradigmxyz/reth#12453)
• feat: add payload witness fn (paradigmxyz/reth#12579)
• feat: restructure op builder (#12229)

Update Priority

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

User Class	Priority
Payload Builders	low
Non-Payload Builders	low
OP-reth	critical

See Update Priorities for more information about this table.

All Changes

• chore: bump version 1.1.2 (#12651)
• chore(sdk): make Chain generic over data primitives (#12635)
• docs: small fix in HARDFORK-CHECKLIST.md (#12646)
• chore(sdk): limit FillTxEnv to super trait of FullSignedTx (#12614)
• Typo Update private-testnet.md (#12633)
• Run kurtosis e2e test 2x/day (#12641)
• fix(discv5): warning discv5 config socket override (#12636)
• chore(witness): simplify wiped storage retrieval (#12637)
• feat(trie): turn TrieWitness methods into public functions (#12510)
• fix: correctly prune transactions during on-disk reorgs (#12630)
• feat(engine): introduce sync implementation of StateRootTask (#12378)
• feat(trie): add extend method to MultiProof (#12467)
• chore(deps): weekly cargo update (#12611)
• chore(sdk): Define MaybeSerde (#12577)
• test(tx-pool): add more unit tests for pending pool (#12603)
• test(tx-pool): add more unit tests for blob pool (#12605)
• Fix Minor Documentation Errors (#12601)
• Typo Update profiling.md (#12631)

... (truncated)

Changelog

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

• 496bf0b chore: bump version 1.1.2 (#12651)
• 06bf5c7 chore(sdk): make Chain generic over data primitives (#12635)
• e859e17 docs: small fix in HARDFORK-CHECKLIST.md (#12646)
• 641d128 chore(sdk): limit FillTxEnv to super trait of FullSignedTx (#12614)
• 7fb862c Typo Update private-testnet.md (#12633)
• f1279b3 Run kurtosis e2e test 2x/day (#12641)
• 55b5136 fix(discv5): warning discv5 config socket override (#12636)
• 8aa9b71 chore(witness): simplify wiped storage retrieval (#12637)
• 1d2934b feat(trie): turn TrieWitness methods into public functions (#12510)
• 2dc75fb fix: correctly prune transactions during on-disk reorgs (#12630)
• 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)