[1.0.2 -> main] Update versions/branches to use for CI dependencies #300
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
[1.0.2] Update versions/branches to use for CI dependencies
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 #299 to
mainbranch.This means we continue using the latest stable versions of Spring (1.x) and CDT (4.x) rather than the versions in the respective repo's
mainbranch. Unless we have a good reason to use the latest head of Spring development for our EOS EVM Node integration tests, it is a better idea to stick with a stable version.However, we do want to use the
mainbranch for the EOS EVM Contract and EOS EVM Miner dependencies.