[0.2.1 -> main] Change to BSL licensing scheme; update silkworm submodule #56
Conversation
This file contains 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
[0.2.1] Change to BSL licensing scheme
…odule-and-spring-dependency [0.2.1] Update silkworm submodule and Spring dependency
for the main branch of evm-bridge-contracts.
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.
Forwards PRs #54 and #55 to
mainbranch.However, instead of using the silkworm submodule commit of #55, the silkworm submodule is updated to use the current head of the
masterbranch of the silkworm repo.Additionally, the changes of #55 to use the latest Spring 1.x version as the Spring dependency are reverted back for the
mainbranch of theevm-bridge-contractsrepo. Themainbranch of theevm-bridge-contractsrepo continues to use themainbranch of Spring for its Spring dependency.