[GR-70822] [GR-70870] Update labsjdk to 25+37-jvmci-25.1-b07

[graalvmbot]

Update labsjdk to 25+37-jvmci-25.1-b07 :

• Adopt [GR-70612] Propagate exceptions faithfully from HotSpot to libgraal when thrown in a canCallJava scope graalvm/labs-openjdk#13

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:

25+37-LTS-jvmci-b07

With this PR it is:

25+37-LTS-jvmci-25.1-b07

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:

$ native-image --version
native-image 25 2025-09-16
OpenJDK Runtime Environment GraalVM CE 25.1.0-dev+37.1 (build 25+37-jvmci-25.1-b07)
OpenJDK 64-Bit Server VM GraalVM CE 25.1.0-dev+37.1 (build 25+37-jvmci-25.1-b07, mixed mode, sharing)

or the java.vendor.version property:

jshell> System.getProperty("java.vendor.version")
$1 ==> "GraalVM CE 25.1.0-dev+37.1"

[zapster]

@zakkak @simonis FYI re LabsJDK version scheme update

(sorry for not pinging you pre merge. I thought I did, but apparently not.)

[simonis]

@zapster, thanks for the heads-up!. Doesn't this Graal change require a corresponding change in labsjdk, which changes java.vm.version accordingly? I can't see any such change in https://github.com/graalvm/labs-openjdk/commits/jdk25/.

Also, is my understanding correct, that this change only affects GraalVM master and https://github.com/graalvm/labs-openjdk/tree/jdk25 and will not be downported to release/graal-vm/25.0 and https://github.com/graalvm/labs-openjdk/tree/release/jvmci/25.0 respectively?

[zapster]

Doesn't this Graal change require a corresponding change in labsjdk, which changes java.vm.version accordingly?

The version string is a JDK build-time flag, so no change required in the JDK sources. There has been corresponding change to the builder config, however that config is not yet open source. There is work ongoing to make the builder config available to the public, likely by moving it into the labs-openjdk repo. Note that our current builder config hard-codes our internal infrastructure definitions and mixes it with the general JDK build configuration, so that needs to be cleaned up before it makes sense to publish it. We will make sure to let you and other community members know when it is ready.

Also, is my understanding correct, that this change only affects GraalVM master [...] and will not be downported to release/graal-vm/25.0

Yes, from all that we know today, that is correct.