Upgrade gradle to 9.3.0 #8713
Merged
Upgrade gradle to 9.3.0 #8713
+2
−2
Conversation
This file contains hidden or 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
jwren
approved these changes
Jan 20, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Our CI environment is using Java 25 and I suspect it is easier and better to upgrade gradle than to specify a older version of Java. This isn't ready to merge yet - making a PR to check the presubmits.
Although, to be clear, I didn't change the java version setting in
gradle.properties(Java 21). I think this means that the CI environment can run gradle with Java 25, but gradle then uses Java 21 to build our plugin, so our plugin should stay the same (hopefully).