search

flashbots / rbuilder

rbuilder is a blazingly fast, state of the art Ethereum MEV-Boost block builder written in Rust
Apache License 2.0
186 stars 21 forks source link

chore(deps): bump reth-node-core from v0.2.0-beta.6 to v1.0.0 #3

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 2 weeks ago

Bumps reth-node-core from v0.2.0-beta.6 to v1.0.0.

Release notes

Sourced from reth-node-core's releases.

Reth v1.0.0

image

Reth 1.0: Production-ready:

  • Stable: Since releasing reth 0.2.0-beta.6 in April 2024, there have been no crash reports, a requirement for any high uptime deployment of Reth. This is a significant improvement over previous versions that occasionally experienced crashes in reorg-related edge cases.
  • Efficient Resource Usage: We've successfully addressed memory leaks in critical components such as the network and the mempool, and optimized Reth’s resource utilization across the board.
  • No performance regressions: With our tooling improving, we’re able to confidently ship releases that consistently improve performance from previous releases.

While we expect Reth the node to run stable, we will introduce more breaking internal API changes.

Summary

Update Priority

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

User Class Priority
Payload Builders medium
Non-Payload Builders medium
OP-Reth high

See Update Priorities for more information about this table.

All Changes

  • feat(rpc): remove ipc future and now using ServerHandle and StopHandle from jsonrpsee (#9044)
  • chore: release 1.0.0 (#9045)
  • feat: add AnyNodeTypes type (#9034)
  • refactor(rpc): add builder pattern for EthHandlers (#9035)
  • Change the wrong 'Child' and 'Auxiliary' usage (#9033)
  • chore(deps): weekly cargo update (#9036)
  • chore: remove some more usages of BytesMut (#9025)
  • chore(deps): rm reth-rpc-types dep from reth-network (#9023)
  • chore(deps): replace fnv with fx (#9024)
  • chore(op): add link to op labs bedrock datadir download (#9014)
  • chore: rm default serde feature in reth-dns (#9021)
  • chore: rm serde for network builder (#9020)
  • chore: remove unused type (#9019)
  • chore: remove serde from ChainSpec (#9017)
  • chore: rename net-common to banlist (#9016)
  • chore: remove AllGenesisFormats (#9013)
  • chore: move different chain hardfork sets to reth-ethereum-forks (#8984)
  • chore: move ratelimit type to tokio util (#9007)
  • chore(deps): rm provider dep (#9006)
  • chore(deps): rm unused dev deps (#9005)
  • chore: remove proptest arbitrary from codec derive and tests (#8968)

... (truncated)

Changelog

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


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 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[bot] commented 2 weeks ago

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.