change groovy dependency to fixed version so we don't get the beta r… #43
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
…lease which is explicitly disallowed.
buildlackey
requested review from
vinaykumarchella and
ipapapa
and removed request for
vinaykumarchella
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.
Here are the full details of why we needed to update the dependency on groovy all:
The Groovy project released pre-release dependencies of 2.5.0 to Maven Central/JCenter in the last few days. Teams with a 2.+ or latest.release constraint on these dependencies are introducing them into the dependency graph, causing downstream projects to break.
A resolution rule has been added to reject these versions. For projects with first order dependencies, the rule will ensure that a 2.4.x version is selected. Downstream projects will not be able to resolve these versions, and will fail with: