update the Gradle wrapper to v7.6.4 #2197
Merged
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
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.
We can't easily upgrade to Gradle 8, but at least we can use the latest release of Gradle 7.
Upgrading to 7.6.4 addresses some security vulnerabilities. See the release notes for details.
Upgrading is a simple matter of changing the properties file: the upgrade does not involve any changes to the Gradle JAR. (@tonihele I ran the update command twice, just in case.)
Long-term, we should clean up the project so it can migrate to Gradle 8 ... and perhaps Kotlin-based Gradle as well, since that's where the world appears to be headed.