Release workflows: use JDK 17 to match project target - #3771
Merged
Conversation
pom.xml sets <maven.compiler.release>17</maven.compiler.release> (since apache#3579, "Bump minimum Java version to 17"), but release-prepare-rc.yml and release-publish.yml still set up JDK 11. The mismatch produces "class file version 61.0 vs. 55.0" errors when the release build runs under Java 11. Update both workflows to JDK 17 (setup-java step name and java-version) so the runtime matches the compile target. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
divjotarora
approved these changes
Sep 4, 2026
Fokko
approved these changes
Sep 4, 2026
Fokko
left a comment
Fokko
left a comment
Contributor
There was a problem hiding this comment.
Thanks @RussellSpitzer and thanks @divjotarora for the review!
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Rationale for this change
Runner was using Java 17 for Compiling but 11 for running.
What changes are included in this PR?
Just always use 17.
Are these changes tested?
No
Are there any user-facing changes?