chore(evm): bump the pinned evm2 revision - #380
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a3fe240c97
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| nightly wasm build picked a backend needing unstable features. Fixed upstream | ||
| in [#345](https://github.com/alloy-rs/evm2/pull/345), which the pinned revision | ||
| now carries, so the pin is about reproducibility alone. |
There was a problem hiding this comment.
This paragraph now says #345 removed the nightly-WASM restriction, but wasm/evm2/rust-toolchain.toml:1-3 and AGENTS.md:141 still state that stable Rust is required because nightly selects an unusable backend. Maintainers consulting either remaining source will receive the opposite toolchain constraint, so update both while recording this new learned fact.
AGENTS.md reference: AGENTS.md:L3-L3
Useful? React with 👍 / 👎.
1 participant
Bumps the pinned evm2 revision to pick up the wasm dispatch backend fix (#345), a
clear_transaction_staterefactor, and an execution-spec test fix.No behavior change: every recorded fixture is unchanged, so the toolchain pin is now about reproducibility alone rather than backend selection.