fix(ci): use JDK 21 for CodeQL analysis#14
Merged
Merged
Conversation
The project requires Java 21 (release version 21 via fess-parent), but the CodeQL workflow set up JDK 17, causing the autobuild step to fail with "error: release version 21 not supported". Align the CodeQL setup-java version with maven.yml (JDK 21).
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
1 participant
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.
Problem
The CodeQL
Analyze (java)job fails during the autobuild step:The project requires Java 21 (release version 21 via
fess-parent), but.github/workflows/codeql-analysis.ymlsets up JDK 17, so the autobuildfails to compile. The regular build (
maven.yml) already uses JDK 21.This blocks the CodeQL check on PRs (e.g. #13).
Fix
Align the CodeQL workflow's
setup-javaversion withmaven.yml(JDK 17 -> 21).Only the CI workflow is changed; no source or behavior changes.