up to 6.2025.10, revert examples in docs to 6.2025.3

Author: qqmyers

.github/workflows/container_maintenance.yml

@@ -63,11 +63,11 @@ jobs:
       - discover
     outputs:
       # This is a JSON map with keys of branch names (supported releases & develop) and values containing an array of known image tags for the branch
-      # Example: {"v6.6": ["latest", "6.6-noble", "6.6-noble-r1"], "v6.5": ["6.5-noble", "6.5-noble-r5"], "v6.4": ["6.4-noble", "6.4-noble-r12"], "develop": ["unstable", "6.7-noble", "6.7-noble-p6.2025.9-j17"]}
+      # Example: {"v6.6": ["latest", "6.6-noble", "6.6-noble-r1"], "v6.5": ["6.5-noble", "6.5-noble-r5"], "v6.4": ["6.4-noble", "6.4-noble-r12"], "develop": ["unstable", "6.7-noble", "6.7-noble-p6.2025.3-j17"]}
       supported_tag_matrix: ${{ steps.execute.outputs.supported_tag_matrix }}
 
       # This is a JSON list containing a flattened map of branch names and the latest non-rolling tag
-      # Example: [ "v6.6=gdcc/base:6.6-noble-r1", "v6.5=gdcc/base:6.5-noble-r5", "v6.4=gdcc/base:6.4-noble-r12", "develop=gdcc/base:6.7-noble-p6.2025.9-j17" ]
+      # Example: [ "v6.6=gdcc/base:6.6-noble-r1", "v6.5=gdcc/base:6.5-noble-r5", "v6.4=gdcc/base:6.4-noble-r12", "develop=gdcc/base:6.7-noble-p6.2025.3-j17" ]
       rebuilt_images: ${{ steps.execute.outputs.rebuilt_images }}
 
     steps:

…c/release-notes/11827-Payara-6.2025.9.md …/release-notes/11827-Payara-6.2025.10.mddoc/release-notes/11827-Payara-6.2025.9.md renamed to doc/release-notes/11827-Payara-6.2025.10.md doc/release-notes/11827-Payara-6.2025.9.md renamed to doc/release-notes/11827-Payara-6.2025.10.md

@@ -1,3 +1,3 @@
-The recommended Payara version has been updated to Payara-6.2025.9
+The recommended Payara version has been updated to Payara-6.2025.10
 
 Standard Payara upgrade instructions - as in the 6.7 release notes should be added.

doc/sphinx-guides/source/container/base-image.rst

@@ -82,7 +82,7 @@ For now, stale images will be kept on Docker Hub indefinitely.
     Will roll over to the rolling production tag after a Dataverse release.
 - | **Flexible Stack**
   | Definition: ``<dv-major>.<dv-minor-next>-<flavor>-p<payara.version>-j<java.version>``
-  | Example: :substitution-code:`|nextVersion|-noble-p6.2025.9-j17`
+  | Example: :substitution-code:`|nextVersion|-noble-p6.2025.3-j17`
   | Summary: Rolling tag during a development cycle of the Dataverse software (`Dockerfile <https://github.com/IQSS/dataverse/tree/develop/modules/container-base/src/main/docker/Dockerfile>`__).
 
 **NOTE**: In these tags for development usage, the version number will always be 1 minor version ahead of existing Dataverse releases.

doc/sphinx-guides/source/developers/classic-dev-env.rst

@@ -93,15 +93,15 @@ On Linux, install ``jq`` from your package manager or download a binary from htt
 Install Payara
 ~~~~~~~~~~~~~~
 
-Payara 6.2025.9 or higher is required.
+Payara 6.2025.10 or higher is required.
 
 To install Payara, run the following commands:
 
 ``cd /usr/local``
 
-``sudo curl -O -L https://nexus.payara.fish/repository/payara-community/fish/payara/distributions/payara/6.2025.9/payara-6.2025.9.zip``
+``sudo curl -O -L https://nexus.payara.fish/repository/payara-community/fish/payara/distributions/payara/6.2025.10/payara-6.2025.10.zip``
 
-``sudo unzip payara-6.2025.9.zip``
+``sudo unzip payara-6.2025.10.zip``
 
 ``sudo chown -R $USER /usr/local/payara6``
 

doc/sphinx-guides/source/installation/prerequisites.rst

@@ -44,7 +44,7 @@ On RHEL/derivative you can make Java 17 the default with the ``alternatives`` co
 Payara
 ------
 
-Payara 6.2025.9 is recommended. Newer versions might work fine. Regular updates are recommended.
+Payara 6.2025.10 is recommended. Newer versions might work fine. Regular updates are recommended.
 
 Installing Payara
 =================
@@ -55,8 +55,8 @@ Installing Payara
 
 - Download and install Payara (installed in ``/usr/local/payara6`` in the example commands below)::
 
-	# wget https://nexus.payara.fish/repository/payara-community/fish/payara/distributions/payara/6.2025.9/payara-6.2025.9.zip
-	# unzip payara-6.2025.9.zip
+	# wget https://nexus.payara.fish/repository/payara-community/fish/payara/distributions/payara/6.2025.10/payara-6.2025.10.zip
+	# unzip payara-6.2025.10.zip
 	# mv payara6 /usr/local
 
 If nexus.payara.fish is ever down for maintenance, Payara distributions are also available from https://repo1.maven.org/maven2/fish/payara/distributions/payara/

doc/sphinx-guides/source/qa/test-automation.md

@@ -52,7 +52,7 @@ Go to the end of the log and then scroll up, looking for the failure. A failed A
 
 ```
 TASK [dataverse : download payara zip] *****************************************
-fatal: [localhost]: FAILED! => {"changed": false, "dest": "/tmp/payara.zip", "elapsed": 10, "msg": "Request failed: <urlopen error timed out>", "url": "https://nexus.payara.fish/repository/payara-community/fish/payara/distributions/payara/6.2025.9/payara-6.2025.9.zip"}
+fatal: [localhost]: FAILED! => {"changed": false, "dest": "/tmp/payara.zip", "elapsed": 10, "msg": "Request failed: <urlopen error timed out>", "url": "https://nexus.payara.fish/repository/payara-community/fish/payara/distributions/payara/6.2025.10/payara-6.2025.10.zip"}
 ```
 
 In the example above, if Payara can't be downloaded, we're obviously going to have problems deploying Dataverse to it!

modules/dataverse-parent/pom.xml

@@ -149,7 +149,7 @@
         <argLine>-Duser.timezone=${project.timezone} -Dfile.encoding=${project.build.sourceEncoding} -Duser.language=${project.language} -Duser.region=${project.region}</argLine>
 
         <!-- Major system components and dependencies -->
-        <payara.version>6.2025.9</payara.version>
+        <payara.version>6.2025.10</payara.version>
         <postgresql.version>42.7.7</postgresql.version>
         <solr.version>9.8.0</solr.version>
         <aws.version>2.33.0</aws.version>