feat: Update alloy after updating Substrate #128
Draft
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
1.49.0Features
|
AdaJane-SxT
force-pushed
the
feat/update-alloy
branch
from
8a6a24f to
1e6fa04
Compare
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.
Rationale for this change
In the upcoming SXT node APIs for Smart Contract Indexing, we want to use the types defined in the Alloy library to minimize transformations and configuration complexity of indexers.
What changes are included in this PR?
This PR updates the alloy version dependencies to match the ones used the in the reth-indexer.
Are these changes tested?
Existing unit tests pass