-
Notifications
You must be signed in to change notification settings - Fork 747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup-java@v4 doesn't detect versions for graalvm 17 #706
Comments
Hello @corneil, Thank you for creating this issue and to comply with the GraalVM Free Terms and Conditions (GFTC) license, we recommend using GraalVM JDK 17 version 17.0.12, as this is the only version of GraalVM JDK 17 available under the GFTC license as per this documentation. This ensures compliance with the licensing requirements for GraalVM JDK 17. Additionally, we strongly encourage considering an upgrade to GraalVM JDK 21, which offers the latest features, improvements, and long-term support. GraalVM JDK 21 provides more recent advancements, and upgrading to it will help you leverage the latest capabilities and optimizations available. If you have any further questions or need assistance with setting up the appropriate version, Please feel free to reach us! |
Hello @guizmaii, we have investigated the issue, and we were unable to replicate it locally. Additionally, we have observed that workflows for Temurin in your repository are succeeding without any issues. Please find the screenshot for reference. |
Description:
Specifying simple version 17 for GraalVM distribution results in error
Error: Could not find GraalVM for SemVer 17
Task version:
v4
Platform:
Runner type:
Repro steps:
Expected behavior:
The java jdk for latest version of GraalVM should be installed. Just like it does with any other distribution. When specifying distribution
liberica
the output is:When supplying
17.0.12
distributiongraalvm
does work as expected.When supplying
21
distributiongraalvm
does work as expected.Actual behavior:
Output on console:
Extract from log file:
The text was updated successfully, but these errors were encountered: