WEB3-418: Update Alloy to v0.14 #547
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nategraf
approved these changes
Apr 24, 2025
|
e2e test is failing with an interesting error https://github.com/risc0/risc0-ethereum/actions/runs/14671053586/job/41177454463 |
Apparently there was a new version of Teku that required a different configuration. So I've pinned the clients used in E2E to fixed versions to avoid similar problems in the future. |
nategraf
approved these changes
May 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the primary
alloy-*dependencies across the workspace from v0.12/v0.8 versions to v0.14/v1.0.This significant dependency upgrade necessitated substantial refactoring throughout the
risc0-steelcodebase to adapt to the new Alloy APIs and patterns. Key consequences include:abi_decode), and type definitions.EvmFactoryabstraction (EthEvmFactory,OpEvmFactory) to handle different EVM environments (Ethereum, Optimism) in a way compatible with the updated dependencies.EvmEnv,Contract, and significantly changing theCallBuilderAPI.revm(to v22.0) for compatibility.Breaking Changes:
CallBuilderAPI has changed: configuration now requires direct modification of the publictxfield (e.g.,builder.tx.caller = ...) instead of using fluent methods.EvmFactory, adapting to new Alloy types).[Unreleased]changelog section for a detailed list of breaking changes introduced as part of this Alloy version bump.Examples and documentation have been extensively updated to align with Alloy v0.14/v1.0 and the resulting API adjustments.