[GR-70822] [GR-70870] Update labsjdk to 25+37-jvmci-25.1-b07 #12414
+492
−169
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.
Update labsjdk to 25+37-jvmci-25.1-b07 :
LabsJDK version scheme update
We restored master to JDK 25 in #12210. Thus, there are now two active branches that are built on top of JDK 25, master and release/graal-vm/25.0. The former uses LabsJDK built from https://github.com/graalvm/labs-openjdk/tree/jdk25 while the latter uses https://github.com/graalvm/labs-openjdk/tree/release/jvmci/25.0. Since these two version are incompatible in terms of JVMCI features, we need a way to distinguish them. Thus, we are reintroducing a "release name" into the LabsJDK version.
Before this PR, the
java.vm.version
system property would report:With this PR it is:
Note that this version change primarily affects the LabsJDK version, e.g., the JDK that is used to build a GraalVM. The GraalVM artifacts, such as
native-image
, can still be identified as before, e.g., via--version
:or the
java.vendor.version
property: