[GR-67399] Add version updates to docs for GraalVM for JDK 25.

PullRequest: graal/21911

Author: olyagpl

docs/getting-started/container-images/graalvm-ce-container-images.md

@@ -16,8 +16,8 @@ There are different GraalVM Community Edition container images provided dependin
 These are: **native-image-community**, **jdk-community**, **truffleruby-community**, **nodejs-community**, and **graalpy-community**.
 The container images are multi-arch, for x64 and AArch64 processor architectures, with a choice of Oracle Linux versions 8, 9, and 10.
 
-GraalVM is installed in _/usr/lib64/graalvm/graalvm-community-java&lt;$FeatureVersion&gt;/_ where `<$FeatureVersion>` is `17`, `21`, `24`, and so on.
-For instance, GraalVM for JDK 24 is installed in _/usr/lib64/graalvm/graalvm-community-java24/_.
+GraalVM is installed in _/usr/lib64/graalvm/graalvm-community-java&lt;$FeatureVersion&gt;/_ where `<$FeatureVersion>` is `17`, `21`, `25`, and so on.
+For instance, GraalVM for JDK 25 is installed in _/usr/lib64/graalvm/graalvm-community-java25/_.
 All binaries, including `java`, `javac`, `native-image`, and other binaries are available as global commands via the `alternatives` command.
 
 > Note: For GraalVM non-RPM based images (**graalvm-community**, **python-community**, **truffleruby-community**), the installation location is under _/opt/_ (_/opt/graalvm-community-java&lt;$FeatureVersion&gt;/_, _/opt/truffleruby-&lt;$GRAALVM_VERSION&gt;/_, and _/opt/graalpy-&lt;$GRAALVM_VERSION&gt;/_ respectively).
@@ -37,45 +37,44 @@ $version[-muslib(for native image only)][-$platform][-$buildnumber]
 The following tags are listed from the most-specific tag (at the top) to the least-specific tag (at the bottom).
 The most-specific tag is unique and always points to the same image, while the less-specific tags point to newer image variants over time.
 For example:
-```
-24.0.1-ol9-20250318
-24.0.1-ol9
-24.0.1
-24-ol9
-24
+```bash
+25.0.0-ol9
+25.0.0
+25-ol9
+25
 ```
 
 ## Pulling Images
 
-1. To pull the container image for GraalVM JDK for a specific JDK feature version, such as _24_, run:
+1. To pull the container image for GraalVM JDK for a specific JDK feature version, such as _25_, run:
     ```bash
-    docker pull ghcr.io/graalvm/jdk-community:24
+    docker pull ghcr.io/graalvm/jdk-community:25
     ```
 
     Alternatively, to use the container image as the base image in your Dockerfile, use:
     ```bash
-    FROM ghcr.io/graalvm/jdk-community:24
+    FROM ghcr.io/graalvm/jdk-community:25
     ```
     You have pulled a size compact GraalVM Community Edition container image with the GraalVM JDK and the Graal compiler preinstalled.
 
-2. To pull the container image with the `native-image` utility for a specific JDK feature version, such as _24_, run:
+2. To pull the container image with the `native-image` utility for a specific JDK feature version, such as _25_, run:
     ```bash
-    docker pull ghcr.io/graalvm/native-image-community:24
+    docker pull ghcr.io/graalvm/native-image-community:25
     ```
 
     Alternatively, to pull the container image with the `native-image` utility with the `musl libc` toolchain to create fully statically linked executables, use:
     ```bash
-    docker pull ghcr.io/graalvm/native-image-community:24-muslib
+    docker pull ghcr.io/graalvm/native-image-community:25-muslib
     ```
 
     Alternatively, to use the container image as the base image in your Dockerfile, use:
     ```bash
-    FROM ghcr.io/graalvm/native-image-community:24-muslib
+    FROM ghcr.io/graalvm/native-image-community:25-muslib
     ```
 
 3. To verify, start the container and enter a Bash session:
     ```bash
-    docker run -it --rm --entrypoint /bin/bash ghcr.io/graalvm/native-image-community:24
+    docker run -it --rm --entrypoint /bin/bash ghcr.io/graalvm/native-image-community:25
     ```
 
 	To check the version of GraalVM and its installed location, run the `env` command from the Bash prompt:
@@ -96,13 +95,13 @@ For example:
 
 4. Calling `docker pull` without specifying a processor architecture pulls container images for the processor architecture that matches your Docker client. To pull a container image for a different platform architecture, specify the desired platform architecture with the `--platform` option and either `linux/amd64` or `linux/aarch64` as follows:
     ```bash
-    docker pull --platform linux/aarch64 ghcr.io/graalvm/native-image-community:24
+    docker pull --platform linux/aarch64 ghcr.io/graalvm/native-image-community:25
     ```
 
 ## Oracle GraalVM Container Images
 
 Oracle GraalVM container images are published in the [Oracle Container Registry (OCR)](https://container-registry.oracle.com/ords/ocr/ba/graalvm) and include [GFTC-licensed](https://www.oracle.com/downloads/licenses/graal-free-license.html) Oracle GraalVM.
-Learn more in the [Oracle GraalVM Container Images documentation](https://docs.oracle.com/en/graalvm/jdk/24/docs/getting-started/container-images/).
+Learn more in the [Oracle GraalVM Container Images documentation](https://docs.oracle.com/en/graalvm/jdk/25/docs/getting-started/container-images/).
 
 ### Related Documentation
 

docs/getting-started/container-images/oracle-graalvm-container-images.md

@@ -20,9 +20,9 @@ Oracle GraalVM container images are published in two OCR repositories: **jdk** a
 
 Both repositories provide container images for x64 and AArch64 processor architectures, with a choice of Oracle Linux versions 8, 9, and 10.
 
-Oracle GraalVM is installed in _/usr/lib64/graalvm/graalvm-java&lt;$FeatureVersion&gt;/_ where `<$FeatureVersion>` is `17`, `21`, `24`, and so on.
+Oracle GraalVM is installed in _/usr/lib64/graalvm/graalvm-java&lt;$FeatureVersion&gt;/_ where `<$FeatureVersion>` is `17`, `21`, `25`, and so on.
 
-For example, Oracle GraalVM for JDK 24 is installed in _/usr/lib64/graalvm/graalvm-java24/_.
+For example, Oracle GraalVM for JDK 25 is installed in _/usr/lib64/graalvm/graalvm-java25/_.
 All binaries, including `java`, `javac`, `native-image`, and other binaries are available as global commands via the `alternatives` command.
 
 ## Tags
@@ -36,43 +36,42 @@ $version[-muslib(for native image only)][-$platform][-$buildnumber]
 The following tags are listed from the most-specific tag (at the top) to the least-specific tag (at the bottom).
 The most-specific tag is unique and always points to the same container image, while the less-specific tags point to newer container image variants over time.
 ```
-24.0.1-ol9-20250318
-24.0.1-ol9
-24.0.1
-24-ol9
-24
+25.0.0-ol9
+25.0.0
+25-ol9
+25
 ```
 
 ## Pulling Images
 
-1. To pull the container image for Oracle GraalVM JDK for a specific JDK feature version, such as _24_, run:
+1. To pull the container image for Oracle GraalVM JDK for a specific JDK feature version, such as _25_, run:
     ```bash
-    docker pull container-registry.oracle.com/graalvm/jdk:24
+    docker pull container-registry.oracle.com/graalvm/jdk:25
     ```
 
     Alternatively, to use the container image as the base image in your Dockerfile, use:
     ```bash
-    FROM container-registry.oracle.com/graalvm/jdk:24
+    FROM container-registry.oracle.com/graalvm/jdk:25
     ```
 
-2.  To pull the container image for Oracle GraalVM `native-image` utility for a specific JDK feature version, such as _24_, run:
+2.  To pull the container image for Oracle GraalVM `native-image` utility for a specific JDK feature version, such as _25_, run:
     ```bash
-    docker pull container-registry.oracle.com/graalvm/native-image:24
+    docker pull container-registry.oracle.com/graalvm/native-image:25
     ```
 
     Alternatively, to pull the container image for Oracle GraalVM `native-image` utility with the `musl libc` toolchain to create fully statically linked executables, run:
     ```bash
-    docker pull container-registry.oracle.com/graalvm/native-image:24-muslib
+    docker pull container-registry.oracle.com/graalvm/native-image:25-muslib
     ```
 
     Alternatively, to use the container image as the base image in your Dockerfile, use:
     ```bash
-    FROM container-registry.oracle.com/graalvm/native-image:24-muslib
+    FROM container-registry.oracle.com/graalvm/native-image:25-muslib
     ```
 
 3. To verify, start the container and enter a Bash session:
     ```bash
-    docker run -it --rm --entrypoint /bin/bash container-registry.oracle.com/graalvm/native-image:24
+    docker run -it --rm --entrypoint /bin/bash container-registry.oracle.com/graalvm/native-image:25
     ```
 
     To check the version of Oracle GraalVM and its installed location, run the `env` command from the `bash` prompt:
@@ -95,7 +94,7 @@ The most-specific tag is unique and always points to the same container image, w
 
 4. A `docker pull` command that omits a processor architecture pulls a container image for the processor architecture that matches your Docker client. To pull a container image for a different platform architecture, specify the desired platform architecture with the `--platform` option and either `linux/amd64` or `linux/aarch64` as follows:
     ```bash
-    docker pull --platform linux/aarch64 container-registry.oracle.com/graalvm/native-image:24
+    docker pull --platform linux/aarch64 container-registry.oracle.com/graalvm/native-image:25
     ```
 
 ### Related Documentation

docs/getting-started/oci/installation-compute-instance-with-OL.md

@@ -16,7 +16,7 @@ To replicate the steps in this guide, [create a Compute instance and connect to
 
 ## Install Oracle GraalVM
 
-For convenience, the RPM package for Oracle GraalVM for JDK 24 is available in the Oracle YUM repository with the package name `graalvm-24-native-image`.
+For convenience, the RPM package for Oracle GraalVM for JDK 25 is available in the Oracle YUM repository with the package name `graalvm-25-native-image`.
 This distribution includes a JDK and Native Image.
 It is self-contained and all the required dependencies will be automatically resolved during the installation.
 
@@ -42,7 +42,7 @@ sudo yum update -y oraclelinux-release-el10
 sudo yum config-manager --set-enabled el10_codeready_builder
 ```
 ```bash
-sudo yum install graalvm-24-native-image
+sudo yum install graalvm-25-native-image
 ```
 Confirm that the installed package size is correct by entering `yes` at the prompt.
 
@@ -54,7 +54,7 @@ sudo dnf update -y oraclelinux-release-el10
 sudo dnf config-manager --set-enabled el10_codeready_builder
 ```
 ```bash
-sudo dnf install graalvm-24-native-image
+sudo dnf install graalvm-25-native-image
 ```
 
 ### Oracle Linux 9
@@ -67,7 +67,7 @@ sudo yum update -y oraclelinux-release-el9
 sudo yum config-manager --set-enabled ol9_codeready_builder
 ```
 ```bash
-sudo yum install graalvm-24-native-image
+sudo yum install graalvm-25-native-image
 ```
 Confirm that the installed package size is correct by entering `yes` at the prompt.
 
@@ -79,7 +79,7 @@ sudo dnf update -y oraclelinux-release-el9
 sudo dnf config-manager --set-enabled ol9_codeready_builder
 ```
 ```bash
-sudo dnf install graalvm-24-native-image
+sudo dnf install graalvm-25-native-image
 ```
 
 ### Oracle Linux 8
@@ -92,7 +92,7 @@ sudo yum update -y oraclelinux-release-el8
 sudo yum config-manager --set-enabled ol8_codeready_builder
 ```
 ```bash
-sudo yum install graalvm-24-native-image
+sudo yum install graalvm-25-native-image
 ```
 Confirm that the installed package size is correct by entering `yes` at the prompt.
 
@@ -104,7 +104,7 @@ sudo dnf update -y oraclelinux-release-el8
 sudo dnf config-manager --set-enabled ol8_codeready_builder
 ```
 ```bash
-sudo dnf install graalvm-24-native-image
+sudo dnf install graalvm-25-native-image
 ```
 
 ### Oracle Linux 7
@@ -126,7 +126,7 @@ sudo dnf install graalvm-24-native-image
    ```
 4. Install the latest Oracle GraalVM:
    ```
-   sudo yum install graalvm-24-native-image
+   sudo yum install graalvm-25-native-image
    ```
    Confirm that the installed package size is correct by entering `yes` at the prompt.
 
@@ -138,7 +138,7 @@ After installation, the package files are placed in the _/usr/lib64/graalvm_ dir
 
 1. Set the values of the `PATH` and `JAVA_HOME` environment variables in the bash configuration to point to the location of the Oracle GraalVM installation with the following commands:
    ```bash
-   echo "export JAVA_HOME=/usr/lib64/graalvm/graalvm-java24" >> ~/.bashrc
+   echo "export JAVA_HOME=/usr/lib64/graalvm/graalvm-java25" >> ~/.bashrc
    ```
    ```bash
    echo 'export PATH=$JAVA_HOME/bin:$PATH' >> ~/.bashrc

docs/getting-started/oci/installation-devops-build-pipeline.md

@@ -26,27 +26,27 @@ To work with a Build Pipeline, add statements to a [build specification file](ht
 The DevOps CI/CD platform reads the file and runs the commands one by one.
 You do not need to run a YUM package manager command manually.
 
-RPMs for Oracle GraalVM are available with the package names `graalvm-17-native-image`, `graalvm-21-native-image`, and `graalvm-24-native-image`.
+RPMs for Oracle GraalVM are available with the package names `graalvm-17-native-image`, `graalvm-21-native-image`, and `graalvm-25-native-image`.
 Each package includes the JDK and the Native Image tool.
 
 To install and use Oracle GraalVM in your DevOps Build Pipeline, update your build specification file as shown in the following example.
 
-1. Add a command to install Oracle GraalVM for JDK 24 with Native Image and Java Development Kit (JDK):
+1. Add a command to install Oracle GraalVM for JDK 25 with Native Image and Java Development Kit (JDK):
 
     ```yml
     steps:
     - type: Command
-        name: "Install Oracle GraalVM for JDK 24"
+        name: "Install Oracle GraalVM for JDK 25"
         command: |
-        yum -y install graalvm-24-native-image
+        yum -y install graalvm-25-native-image
     ```
 
-2. Add a command to set the value of the `JAVA_HOME` environment variable for Oracle GraalVM for JDK 24:
+2. Add a command to set the value of the `JAVA_HOME` environment variable for Oracle GraalVM for JDK 25:
 
     ```yml
     env:
     variables:
-        "JAVA_HOME" : "/usr/lib64/graalvm/graalvm-java24"
+        "JAVA_HOME" : "/usr/lib64/graalvm/graalvm-java25"
     ```
 
 3. Add the command to set the value of the `PATH` environment variable:
@@ -68,9 +68,9 @@ Here is an example of a complete [build specification file](https://github.com/o
 
 Oracle GraalVM provides more features, each of which can be installed as an add-on.
 Use the `yum list` command to get a list of the available RPMs for your installation.
-For instance, for Oracle GraalVM for JDK 24, run:
+For instance, for Oracle GraalVM for JDK 25, run:
 ```bash
-yum list graalvm-24*
+yum list graalvm-25*
 ...
 ```
 

docs/oracle-graalvm/support.md

@@ -7,14 +7,14 @@ permalink: /support/
 
 ## Available Distributions
 
-Oracle GraalVM for JDK 24 is based on Oracle JDK 24.
-Each release of Oracle GraalVM for JDK 24 includes all Oracle Java critical patch updates (CPUs), which are provided on a regular schedule to remedy defects and known vulnerabilities.
+Oracle GraalVM for JDK 25 is based on Oracle JDK 25.
+Each release of Oracle GraalVM for JDK 25 includes all Oracle Java critical patch updates (CPUs), which are provided on a regular schedule to remedy defects and known vulnerabilities.
 
-Oracle GraalVM for JDK 24 is available for Linux, macOS, and Windows on the x64 architecture, and for Linux and macOS on the AArch64 architecture.
+Oracle GraalVM for JDK 25 is available for Linux, macOS, and Windows on the x64 architecture, and for Linux and macOS on the AArch64 architecture.
 
 ## Certified Platforms
 
-Oracle GraalVM for JDK 24 is certified on the following platforms.
+Oracle GraalVM for JDK 25 is certified on the following platforms.
 
 **Linux**
 
@@ -26,7 +26,6 @@ Oracle GraalVM for JDK 24 is certified on the following platforms.
 | Oracle Linux 7                  | x64                 |
 | Red Hat Enterprise Linux 10     | AArch64, x64        |
 | Red Hat Enterprise Linux 9      | AArch64, x64        |
-| Red Hat Enterprise Linux 9      | AArch64, x64        |
 | Red Hat Enterprise Linux 8      | AArch64, x64        |
 | Red Hat Enterprise Linux 7      | x64                 |
 | Ubuntu Linux 24.10              | x64                 |
@@ -55,7 +54,7 @@ See [Oracle GraalVM Support Roadmap](https://docs.oracle.com/en/graalvm/support-
 
 ## Related Technologies
 
-Additional open source language runtimes designed for use with Oracle GraalVM for JDK 24 are available on [graalvm.org](https://www.graalvm.org/reference-manual/languages/).
+Additional open source language runtimes designed for use with Oracle GraalVM for JDK 25 are available on [graalvm.org](https://www.graalvm.org/reference-manual/languages/).
 
 ## Licensing and Support
 

docs/reference-manual/embedding/embed-languages.md

@@ -503,7 +503,7 @@ Here is a Maven profile configuration example:
                 <plugin>
                     <groupId>org.graalvm.buildtools</groupId>
                     <artifactId>native-maven-plugin</artifactId>
-                    <version>0.10.1</version>
+                    <version>${native.maven.plugin.version}</version>
                     <extensions>true</extensions>
                     <executions>
                         <execution>
@@ -1059,7 +1059,7 @@ with the corresponding `assembly.xml`:
             <handlerName>metaInf-services</handlerName>
         </containerDescriptorHandler>
     </containerDescriptorHandlers>
-</assembly
+</assembly>
 ```
 
 ## Compatibility with JSR-223 ScriptEngine
@@ -1085,6 +1085,7 @@ There are only two lines to adapt to your project:
 ```java
 public final class CHANGE_NAME_EngineFactory implements ScriptEngineFactory {
     private static final String LANGUAGE_ID = "<<INSERT LANGUAGE ID HERE>>";
+    }
 ```
 
 Rename the class as desired and change the `LANGUAGE_ID` to the desired Truffle language (for example, "python" for GraalPy or "js" for GraalJS).

docs/reference-manual/java-on-truffle/ImplementationDetails.md

@@ -32,10 +32,10 @@ This mode is not used when running in a native executable since there will be no
 
 ## Current Limitations
 
-* Espresso does not implement the [JVM Tool Interface (JVMTI)](https://docs.oracle.com/en/java/javase/22/docs/specs/jvmti.html). As a result, it does not support the `-agentlib`, or `-agentpath` VM options.
+* Espresso does not implement the [JVM Tool Interface (JVMTI)](https://docs.oracle.com/en/java/javase/25/docs/specs/jvmti.html). As a result, it does not support the `-agentlib`, or `-agentpath` VM options.
 * Espresso does not implement the `java.lang.instrument` interface. As a result it does not support the `-javaagent` VM option.
 * Espresso currently uses the standard native libraries from the Java core library. This requires allowing a polyglot `Context` native access. Because of the way these libraries are loaded (via [Truffle NFI](../../../truffle/docs/NFI.md)), running on HotSpot only works on Linux (with `glibc`). Running as part of a native executable works on Linux, Windows, and macOS but it currently limited to one context.
 * Support for [Java Management Extensions (JMX)](https://docs.oracle.com/javase/tutorial/jmx/index.html) is partial and some methods might return partial data.
 * The [Debugger Protocol Implementation (JDWP)](https://docs.oracle.com/javase/8/docs/technotes/guides/jpda/jdwp-spec.html) lacks some capabilities compared to HotSpot. It will correctly report the supported [capabilities](https://docs.oracle.com/javase/8/docs/platform/jpda/jdwp/jdwp-protocol.html#JDWP_VirtualMachine_Capabilities). In particular actions that require to enumerate all Java objects are not supported. However, it does support a few hot reloading cases that HotSpot does not.
-* When the `java.MultiThreaded` option is set to "false", [reference processing](https://docs.oracle.com/en/java/javase/22/docs/api/java.base/java/lang/ref/package-summary.html) will not happen. Depending on the application, this could create resource leaks. Note that this option is set to "false" automatically if Espresso runs in a context where a single-threaded language is enabled (for example, JavaScript).
+* When the `java.MultiThreaded` option is set to "false", [reference processing](https://docs.oracle.com/en/java/javase/25/docs/api/java.base/java/lang/ref/package-summary.html) will not happen. Depending on the application, this could create resource leaks. Note that this option is set to "false" automatically if Espresso runs in a context where a single-threaded language is enabled (for example, JavaScript).
 * Espresso does not support the [Polyglot API](https://www.graalvm.org/sdk/javadoc/org/graalvm/polyglot/package-summary.html) yet. However, it provides a guest Java Polyglot API, described in `polyglot.jar`. For more information, see [Interoperability with Truffle Languages](Interoperability.md).