chore(deps): bump reth-db-api from v1.6.0 to v1.9.3

[dependabot]

Bumps reth-db-api from v1.6.0 to v1.9.3.

Release notes

Sourced from reth-db-api's releases.

Reth v1.9.3

This is on opstack patch release on top of v1.9.2 that contains fix for rollup boost that includes the new jovian fields in the payload id (paradigmxyz/reth#19726) Also updates the superchan registry with updated timestamps for jovian and isthmus (e.g. worldchain isthmus: ethereum-optimism/superchain-registry#1149) This release is recommended for opstack sepolia where jovian activates Wed 19 Nov 2025 16:00:01 UTC

For fusaka support info see also v1.9.0

Summary

Add a summary, including:

• Critical bug fixes
• New features
• Any breaking changes (and what to expect)

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

See Update Priorities for more information about this table.

All Changes

• chore: bump version v1.9.3 (#19831)
• chore(op-reth/scr): update superchain-registry (#19806)
• fix: add minbasefee for jovian attributes (#19726)

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-v1.9.3-x86_64-unknown-linux-gnu.tar.gz	PGP Signature
	aarch64	reth-v1.9.3-aarch64-unknown-linux-gnu.tar.gz	PGP Signature
	x86_64	reth-v1.9.3-x86_64-pc-windows-gnu.tar.gz	PGP Signature
	x86_64	reth-v1.9.3-x86_64-apple-darwin.tar.gz	PGP Signature
	aarch64	reth-v1.9.3-aarch64-apple-darwin.tar.gz	PGP Signature
	Docker	paradigmxyz/reth	-

... (truncated)

Changelog

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

• 27a8c0f chore: bump version v1.9.3 (#19831)
• 71c648f chore(op-reth/scr): update superchain-registry (#19806)
• a063be7 fix: add minbasefee for jovian attributes (#19726)
• 74351d9 ci: use macos-14 runner (#19658)
• a672700 revert: "refactor(prune): remove receipts log filter segment (#19184)" (#19646)
• 465d747 chore: bump op-revm v12.0.2 patch (#19629)
• 5b3cb2d chore: bump version to 1.9.2 (#19647)
• 3afe69a chore: bump version
• 35ac40a chore: bump revm v31.0.1 (#19567)
• 84785f0 chore: bump v1.9.0 (#19507)
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[wiz-b4c72f16a4]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	1
Sensitive Data	-
Secrets	-
IaC Misconfigurations	-
SAST Findings	-
Software Supply Chain Findings	-
Total	1

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

[dependabot]

Superseded by #3258.