Skip to content

Bump reth-db from v1.8.1 to v1.8.2 #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
dependabot wants to merge 1 commit into from
Closed

Bump reth-db from v1.8.1 to v1.8.2 #4

dependabot wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 6, 2025

Bumps reth-db from v1.8.1 to v1.8.2.

Release notes

Sourced from reth-db's releases.

Reth v1.8.2

image

Summary

[!IMPORTANT] Upgrading to this release is mandatory for node operators running Holesky.

This release includes several fixes for Fusaka hardfork on Holesky.

Update Priority

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

User Class Priority
Holesky High
Payload Builders Low
Non-Payload Builders Low

See Update Priorities for more information about this table.

All Changes

  • chore: bump alloy 1.0.37 (#18795)
  • chore: bump version to 1.8.2 (#18792)
  • fix(rpc/engine): check osaka in getBlobsV1 (#18669)
  • fix: remove cancun check (#18787)
  • fix(rpc): fix eth_config impl (#18744)
  • feat: make more EVM and RPC conversions fallible (#18685)
  • chore: bump rust to edition 2024 (#18692)

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

OP-Reth

... (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 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

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
Bump reth-db from v1.8.1 to v1.8.2
db31053 
Bumps [reth-db](https://github.com/paradigmxyz/reth) from v1.8.1 to v1.8.2.
- [Release notes](https://github.com/paradigmxyz/reth/releases)
- [Changelog](https://github.com/paradigmxyz/reth/blob/main/docs/release.md)
- [Commits](paradigmxyz/reth@e6608be...9c30bf7)

---
updated-dependencies:
- dependency-name: reth-db
  dependency-version: 9c30bf7af5e0d45deaf5917375c9922c16654b28
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Oct 6, 2025
@prestwich
Copy link
Member

prestwich commented Oct 6, 2025

@dependabot ignore the dependency

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 6, 2025

Sorry, the command you entered is not valid for this pull request. Please check the syntax and try again.

Valid commands:
For single dependency PRs, use commands like:
@dependabot ignore this major version
@dependabot ignore this minor version
@dependabot ignore this dependency

@prestwich prestwich closed this Oct 6, 2025
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 6, 2025

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@prestwich
Copy link
Member

prestwich commented Oct 6, 2025

@dependabot ignore this dependency

@dependabot dependabot bot deleted the dependabot/cargo/reth-db-v1.8.2 branch October 6, 2025 17:00
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 6, 2025

OK, I won't notify you about reth-db again, unless you re-open this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@prestwich