fix: reintroduce support for GraalVM 17 #1010
Merged
Conversation
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
|
/gcbrun |
lqiu96
pushed a commit
that referenced
this pull request
May 1, 2025
* fix: reintroduce support for GraalVM 17 * correct coment * fix copyright year * non image-dependent steps to not depend on image building step * restore step dependency * checkout fix branch for testing * clone with branch * use main branch of sdk-platform
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context doc
TL;DR: we are adding another Cloud Build job to test against GraalVM for JDK 17.
The failing linter checks will be solved in the next release cycle. They were introduced in #1003