[0.2.1 -> main] Update EVM Contract dependency; Fix Spring version dependency #58
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
…ndency [0.2.1] Update EVM Contract dependency
Also fix Spring dependency to latest stable 1.x version.
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 #57 to the
mainbranch.However, it reverts the dependency on EVM Contract back to
mainsince that is appropriate for themainbranch ofevm-bridge-contracts.If those were the only changes, this PR should have no diff.
However, this PR also changes the version dependency for Spring. It goes against the decision in #56 to keep the Spring dependency the same (still depending on the
mainbranch). There does not seem to be a strong reason for why themainbranch of EVM Bridge Contracts should depend on themainbranch of Spring. It makes more sense for it to depend on the latest stable version.