Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
87 changes: 44 additions & 43 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ directories = "6"
displaydoc = "0.2"
educe = { version = "0.6.0", features = ["Debug"], default-features = false }
enumflags2 = "0.7"
ethereum-types = { version = "0.15", features = ["ethbloom"] }
ethereum-types = { version = "0.16", features = ["ethbloom"] }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

ethereum-types 0.16: sanity-check features and MSRV

Looks fine; please verify “ethbloom” feature still exists and there are no breaking API/MSRV bumps impacting us.


🌐 Web query:

ethereum-types 0.16 changelog breaking changes and feature list (is `ethbloom` still present?)

💡 Result:

Short answer: I can't find an ethereum-types 0.16 release. The latest published version is 0.15.1 (2024-09-12). In 0.15.1 ethbloom exists as a feature (it was made optional in 0.14.0) and the crate still exposes an "ethbloom" feature (enabled by default in 0.15.1). [1][2]

Sources

  • ethereum-types changelog (shows 0.15.1 and that ethbloom was made optional in 0.14.0). [1]
  • ethereum-types 0.15.1 features page (lists ethbloom as a feature, default-enabled). [2]

Invalid ethereum-types version bump
Cargo.toml:67 sets ethereum-types = "0.16", but no such release exists on crates.io; update to a valid version (e.g., 0.15.1).

🤖 Prompt for AI Agents
In Cargo.toml around line 67, the dependency line sets ethereum-types = "0.16"
which does not exist on crates.io; change the version to a valid release (for
example "0.15.1") and then run cargo update -p ethereum-types (or cargo update)
to refresh Cargo.lock so the lockfile matches the updated dependency.

ez-jsonrpc-types = "0.5"
fil_actor_account_state = { version = "24.1.3" }
fil_actor_cron_state = { version = "24.1.3" }
Expand Down Expand Up @@ -114,7 +114,7 @@ is-terminal = "0.4"
itertools = "0.14"
jsonrpsee = { version = "0.26", features = ["server", "ws-client", "http-client", "macros"] }
jsonwebtoken = { version = "10", features = ["rust_crypto"] }
keccak-hash = "0.11"
keccak-hash = "0.12"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

keccak-hash 0.12: confirm API compatibility

Approve, but double‑check for API or trait changes (e.g., keccak_256 signatures) and MSRV bumps.


🌐 Web query:

keccak-hash crate 0.12 release notes or changelog; any breaking changes from 0.11?

💡 Result:

I couldn't find a keccak-hash 0.12 release — the latest published release is 0.11.0 (Sep 11, 2024). No 0.12 changelog or release notes are available, so there are no documented breaking changes from 0.11 to 0.12. [1][2]

Sources:

  • Libraries.io keccak-hash releases (shows 0.11.0 as latest). [1]
  • docs.rs / crate page for keccak-hash (0.11.0). [2]

Cargo.toml: invalid keccak-hash version
keccak-hash = "0.12" references a non-existent release (latest is 0.11.0); update to a published version.

🤖 Prompt for AI Agents
In Cargo.toml at line 117, the dependency keccak-hash is pinned to a
non-existent version "0.12"; update that entry to a published release (for
example "0.11" or "0.11.0") so Cargo can resolve the crate, then run cargo
update / cargo build to verify resolution and adjust any breaking changes if
necessary.

kubert-prometheus-process = "0.2"
lazy-regex = "3"
libp2p = { workspace = true, features = [
Expand Down
Loading