chore(deps): bump alloy-consensus-any from 1.7.3 to 1.8.3#195
chore(deps): bump alloy-consensus-any from 1.7.3 to 1.8.3#195dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [alloy-consensus-any](https://github.com/alloy-rs/alloy) from 1.7.3 to 1.8.3. - [Release notes](https://github.com/alloy-rs/alloy/releases) - [Changelog](https://github.com/alloy-rs/alloy/blob/main/CHANGELOG.md) - [Commits](alloy-rs/alloy@v1.7.3...v1.8.3) --- updated-dependencies: - dependency-name: alloy-consensus-any dependency-version: 1.8.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Closing: cannot bump alloy independently from reth — see #154 for details. Will update together when reth releases with a compatible alloy version. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
|
Reopening: the alloy 1.x bumps are semver-compatible and CI passes. The incompatibility described in #154 only applies to alloy-evm (0.x breaking change). |
Bumps alloy-consensus-any from 1.7.3 to 1.8.3.
Release notes
Sourced from alloy-consensus-any's releases.
... (truncated)
Changelog
Sourced from alloy-consensus-any's changelog.
... (truncated)
Commits
3bcda29chore: release 1.8.3867951bfix(signer-gcp): use rustls instead of native-tls for gcloud-sdk (#3844)c36b7b2chore: release 1.8.2b479971chore: release 1.8.261768dachore: release 1.8.22f6826ffix(serde): fix off-by-one in JsonStorageKey length check (#3843)9282f7brevert: "fix(serde): validate JsonStorageKey length during deserialization" (...e90f33echore: release 1.8.151bf871revert: "chore: bump ethereum_ssz to 0.10 and tree_hash to 0.12" (#3839)929312bchore: release 1.8.0Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)