Use GraalVM for JDK 21 in GitHub workflow #2765
Merged
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.
Purpose
Upgrade to GraalVM for JDK 21 to avoid being stuck on old JDK 17 version
Description
GraalVM for JDK 17 does not receive any updates anymore (at least not under the "GraalVM Free Terms and Conditions")
See https://github.com/graalvm/setup-graalvm/tree/v1.2.4?tab=readme-ov-file#notes-on-oracle-graalvm-for-jdk-17
As mentioned there in the README and in graalvm/setup-graalvm#107 (comment), we will always be using Oracle GraalVM under the "GraalVM Free Terms and Conditions". After that expires (which for JDK 21 will be in September 2026, see also GraalVM licensing FAQ) we will simply be stuck on an unmaintained GraalVM version (unless we already migrated to GraalVM for JDK 25 in the meantime), but we won't accidentally use GraalVM under the Oracle Technology Network License Agreement and violate it by accident.