-
Notifications
You must be signed in to change notification settings - Fork 28
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
Old versions don't seem to work anymore. #56
Comments
Hi @mbien, sorry for the delay. This has fallen off my radar. For JDK 11, you still need to select a GraalVM version: - name: Set up old GraalVM 11
uses: graalvm/setup-graalvm@v1
with:
version: '22.3.3'
java-version: '11' I guess we could make your snippet work as well. The question is: what GraalVM release and distro for JDK 11 do you expect if you just want JDK 11? Maybe you don't actually care? |
@fniephaus thanks! I must have used the wrong combination of the properties (I tried a few times). The readme could be a bit clearer, but since the old versions are all EOL it is probably not worth updating it. can confirm that this works for old versions: - name: Set up old GraalVM 11
uses: graalvm/setup-graalvm@v1
with:
java-version: '11'
version: '22.3.3' for new: - name: Set up new GraalVM 17
uses: graalvm/setup-graalvm@v1
with:
java-version: '17.0.8'
distribution: 'graalvm-community'
- name: Get latest JDK 17
uses: actions/setup-java@v3
with:
# java-version: 17.0.8
java-version: 17
distribution: 'zulu' so if closing, thanks again! |
Due to the alignment with OpenJDK, we've made some adjustments in the latest GraalVM release, for example the
Correct, and that's exactly why |
The readme mentions that 'old' versions can be still used for the
java-version
field, quote:'8', '11', '16', '19' are supported for older GraalVM releases.
but it doesn't seem to work?
result:
The text was updated successfully, but these errors were encountered: