Repository navigation
deps(deps): bump revm from 42.0.1 to 43.0.3 - #2716
dependabot[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Summary
Thanks for the dependency bump. I found one blocking consistency issue in the dependency graph introduced by this update.
Blocking
revmis upgraded to43.0.3, butrevm-stateremains pinned as a direct dependency at42.0.0in this workspace. The lockfile confirms bothrevm-state 42.0.0andrevm-state 43.0.1are now present simultaneously, which can cause type/API incompatibilities when values cross crate boundaries (same crate name, different major API line).
Please align direct revm-* crates to the same release line (or remove the direct revm-state dependency if not strictly needed) before merge.
🧾 cargo-vet automated audit summary
CI did not commit anything. Review the patch locally and create the final signed commit yourself.
|
4b64fe3 to
10eb23d
Compare
There was a problem hiding this comment.
Summary
Thanks for the bump — there is still one blocking dependency-graph inconsistency introduced by this update.
Blocking
revmwas upgraded to43.0.3inCargo.toml, but the workspace still keeps a direct dependency onrevm-state = "42.0.0". InCargo.lock,stratusnow depends onrevm 43.0.3andrevm-state 42.0.0simultaneously, whilerevm 43.0.3itself usesrevm-state 43.0.1. This leaves tworevm-statemajor lines in the same build and can cause type/API incompatibilities if state types cross crate boundaries.
Please align revm-state with the upgraded revm line (or remove the direct revm-state dependency if not required directly).
🧾 cargo-vet automated audit summary
CI did not commit anything. Review the patch locally and create the final signed commit yourself.
|
10eb23d to
94d4f23
Compare
There was a problem hiding this comment.
Summary
Thanks for the dependency bump. I still see one blocking dependency-graph inconsistency in the current diff.
Blocking
revmis upgraded to43.0.3inCargo.toml, butrevm-stateremains a direct dependency on42.0.0. The lockfile showsstratusdepending onrevm 43.0.3andrevm-state 42.0.0simultaneously, whilerevm 43.0.3itself pullsrevm-state 43.0.1.- This leaves two
revm-statelines in the same build, which can break type compatibility ifrevm-statetypes cross crate boundaries.
Please align/remove the direct revm-state pin so the revm* stack is on one coherent version line.
🧾 cargo-vet automated audit summary
CI did not commit anything. Review the patch locally and create the final signed commit yourself.
|
Bumps [revm](https://github.com/bluealloy/revm) from 42.0.1 to 43.0.3. - [Release notes](https://github.com/bluealloy/revm/releases) - [Changelog](https://github.com/bluealloy/revm/blob/main/CHANGELOG.md) - [Commits](https://github.com/bluealloy/revm/commits) --- updated-dependencies: - dependency-name: revm dependency-version: 43.0.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
94d4f23 to
6f9b3ed
Compare
🧾 cargo-vet automated audit summary
CI did not commit anything. Review the patch locally and create the final signed commit yourself.
|
Bumps revm from 42.0.1 to 43.0.3.
Changelog
Sourced from revm's changelog.
... (truncated)
Commits
Most Recent Ignore Conditions Applied to This Pull Request