chore: patch sov-full-node-configs to ligate-io fork (fix-forward for #42)#43
Merged
Merged
Conversation
…KindConfig type mismatch
Member
Author
|
I have read the CLA Document and I hereby sign the CLA |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Fix-forward for #42's broken build. The chain v0.3.0
ligate-rollupcrate consumessov-full-node-configsfrom the ligate-io sovereign-sdk fork, but the CLI's[patch]block didn't redirect that crate to the fork. Result: twosov_full_node_configsversions in the dep graph,SequencerKindConfig<Address>type mismatch.Same issue Stefan called out in ligate-api#70's PR body and fixed there; CLI was missed.
One-line addition to the
[patch."https://github.com/Sovereign-Labs/sovereign-sdk.git"]block.