[HV] 9.1.0.Final

_config/site.yml

@@ -466,9 +466,11 @@ projects:
         html: https://docs.hibernate.org/validator/{series.version}/reference/en-US/html_single/#validator-gettingstarted
         pdf: https://docs.hibernate.org/validator/{series.version}/reference/en-US/pdf/hibernate_validator_reference.pdf#validator-gettingstarted
       migration_guide:
-        html: /validator/documentation/migration-guide/#{series.version.dashes}-x
+        html: https://docs.hibernate.org/validator/{series.version}/migration/en-US/html_single
+        pdf: https://docs.hibernate.org/validator/{series.version}/migration/en-US/pdf/hibernate_validator_migration_guide.pdf
       whats_new:
-        html: "/validator/releases/{series.version}/#whats-new"
+        html: https://docs.hibernate.org/validator/{series.version}/whats-new/en-US/html_single
+        pdf: https://docs.hibernate.org/validator/{series.version}/whats-new/en-US/pdf/hibernate_validator_whats_new.pdf
       dist:
         sourceforge:
           zip: https://sourceforge.net/projects/hibernate/files/hibernate-validator/{release.version}/hibernate-validator-{release.version}-dist.zip/download

_data/projects/validator/releases/4.3/series.yml

@@ -1,4 +1,9 @@
 summary: Last Bean Validation 1.0 compatible version
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   coord:
     group_id: org.hibernate

_data/projects/validator/releases/5.0/series.yml

@@ -1,4 +1,9 @@
 summary: Reference implementation for Bean Validation 1.1
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   coord:
     group_id: org.hibernate

_data/projects/validator/releases/5.1/series.yml

@@ -1,4 +1,9 @@
 summary: Performances and memory footprint improvements
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   coord:
     group_id: org.hibernate

_data/projects/validator/releases/5.2/series.yml

@@ -1,4 +1,9 @@
 summary: Java 8 support and more
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   coord:
     group_id: org.hibernate

_data/projects/validator/releases/5.3/series.yml

@@ -1,4 +1,9 @@
 summary: Dynamic constraint payload, parameter relaxation, new api for programmatic constraint definition, new translations.
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   coord:
     group_id: org.hibernate

_data/projects/validator/releases/5.4/series.yml

@@ -1,4 +1,9 @@
 summary: JavaMoney support, annotation processor improvements.
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   coord:
     group_id: org.hibernate

_data/projects/validator/releases/6.0/series.yml

@@ -1,4 +1,9 @@
 summary: Bean Validation 2.0 support, performance improvements.
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   artifacts:
     - artifact_id: hibernate-validator

_data/projects/validator/releases/6.1/series.yml

@@ -1,4 +1,9 @@
 summary: Jakarta Bean Validation, new Quarkus-tailored bootstrap
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   repo:
     snapshots: jboss

_data/projects/validator/releases/6.2/series.yml

@@ -1,5 +1,10 @@
 summary: Keep javax.* packages, Expression Language overhaul, @SafeHtml removal
 status: limited-support
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   artifacts:
     - artifact_id: hibernate-validator

_data/projects/validator/releases/7.0/series.yml

@@ -1,4 +1,9 @@
 summary: Jakarta Bean Validation 3.0, jakarta.* packages
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   artifacts:
     - artifact_id: hibernate-validator

_data/projects/validator/releases/8.0/series.yml

@@ -1,4 +1,9 @@
 summary: Jakarta EE 10, @UUID constraint
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   artifacts:
     - artifact_id: hibernate-validator

_data/projects/validator/releases/9.0/series.yml

@@ -6,6 +6,11 @@ summary: >-
   BOM for simpler dependency management,
   dependency updates,
   improvements and bug fixes.
+links:
+  whats_new:
+    html: "/validator/releases/{series.version}/#whats-new"
+  migration_guide:
+    html: /validator/documentation/migration-guide/#{series.version.dashes}-x
 maven:
   artifacts:
     - artifact_id: hibernate-validator-bom

_data/projects/validator/releases/9.1/9.1.0.Final.yml

@@ -0,0 +1,4 @@
+date: 2025-11-04
+summary: >-
+  Misc build adjustments.
+announcement_url: https://in.relation.to/2025/11/04/hibernate-validator-9-1-0-Final/

validator/documentation/index.adoc

@@ -13,8 +13,7 @@ Frequently asked questions.
 link:https://developer.jboss.org/en/hibernate/validator[JBoss-Developer wiki]::
 Old wiki hosted at JBoss.org. Mostly out-of-date content.
 
-== Maintainers
+== Jakarta Validation
 
-* link:releasing-hibernate-validator[Releasing Hibernate Validator]
-* link:releasing-bean-validation-tck[Releasing Bean Validation TCK]
-* link:releasing-bean-validation-api-spec[Releasing Bean Validation API and spec]
+* https://jakarta.ee/specifications/bean-validation/[Jakarta Validation Specifications]
+* https://beanvalidation.org/[beanvalidation.org]

validator/documentation/migrate/index.adoc

@@ -0,0 +1,4 @@
+= Migration guides
+:awestruct-layout: project-migrate
+:awestruct-project: validator
+:page-interpolate: true

validator/documentation/releasing-bean-validation-api-spec.adoc

@@ -4,54 +4,4 @@
 
 Follow these steps for an official release.
 
-WARNING: Bean Validation has been moved to Jakarta EE thus this release process needs an update.
-
-== Prerequisites
-
-* You need to have access to http://ci.hibernate.org/: the release process is now driven by CI
-* Follow the order of operations - the API has to be released before the specification
-
-== Prepare
-
-* Make sure there are no outstanding issues in https://hibernate.atlassian.net/projects/BVAL/issues[Jira]
-* Release the https://hibernate.atlassian.net/projects/BVAL?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=released-unreleased[Jira version]
-
-== Release beanvalidation-api
-
-=== Prepare
-
-* Check that everything has been pushed to the upstream repository
-* Check that CI is green for the branch you want to release
-* Before you release try the latest snapshot of the API with the RI (if the RI is up to date with the API)
-
-=== Release
-
-* Go to CI, and select http://ci.hibernate.org/view/Validator/job/beanvalidation-api-release/[the beanvalidation-api-release job]. Click on _Build with parameters_.
-** *Be careful when filling the form with the build parameters*
-** *Fill in the DELIVERY_QUALIFIER if the release is an official JCP release step (use - if not)*
-* Release the artifacts on the JBoss Nexus repository manager. This is a two-steps process.
-** Log into https://repository.jboss.org/nexus/index.html[Nexus] and examine https://repository.jboss.org/nexus/index.html#stagingRepositories[your staging repository]. Click on the _Updated_ column 2 times to have the repositories sorted correctly.
-** You can either drop it in order to start over again or you can close and promote it making the artifacts available in the live repository. (Click _Refresh_ after each action)
-** You can find more information in the description of https://developer.jboss.org/docs/DOC-14608[the JBoss project release process]. A Maven settings.xml for testing the artifacts in the staging repository can be found https://developer.jboss.org/docs/DOC-15664[here].
-* Transfer the released issues in JIRA to the _Closed_ state. You can use this search https://hibernate.atlassian.net/browse/BVAL-560?jql=project%20%3D%20BVAL%20AND%20fixVersion%20%3D%202.0.0.Alpha2%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC[Issue Navigator - Hibernate JIRA] and select another `fixVersion`. Once you have selected the right version, click on the button with three dots at the top right of the screen and click on _Bulk update all XX issues_. Use the _Transition_ action to transition your issues from _Resolved_ to _Closed_.
-
-== Release beanvalidation-spec
-
-=== Prepare
-
-* Check that everything has been pushed to the upstream repository
-* Check that you are able to build the TCK audit file via the command ant create-tck-audit-file (a section id might be missing)
-* Check that CI is green for the branch you want to release
-* *The changelog of the spec is now updated automatically: do not update it!*
-
-=== Release
-
-* Go to CI, and select http://ci.hibernate.org/view/Validator/job/beanvalidation-spec-release/[the beanvalidation-spec-release job]. Click on _Build with parameters_.
-** *Be careful when filling the form with the build parameters.*
-** *Fill in the RELEASE_VERSION_QUALIFIER if the release is an official JCP release step*
-** *Fill in the DELIVERY_QUALIFIER if the release is an official JCP release step (use - if not)*
-* The release job pushes the specification to the website repository but there are still some manual steps:
-** Update the home page: http://beanvalidation.org/[Bean Validation - Home]
-** Update the specification page: http://beanvalidation.org/specification/[Bean Validation - Specification]
-** Once the spec is online (ie the website job triggered by the release job is finished), you can generate the HTML diffs using: https://www.changedetection.com/comparepages.html[ChangeDetection - Compare Web Pages]
-
+WARNING: Bean Validation has been moved to Jakarta EE thus, see https://github.com/jakartaee/validation/blob/main/MAINTAINERS.md[MAINTAINERS.md] for release process.

validator/documentation/releasing-bean-validation-tck.adoc

@@ -4,35 +4,4 @@
 
 Follow these steps for an official release.
 
-WARNING: Bean Validation has been moved to Jakarta EE thus this release process needs an update.
-
-== Prerequisites
-
-* You need to have access to http://ci.hibernate.org/: the release process is now driven by CI
-
-== Prepare
-
-* Update the TCK audit file (`tests/src/main/resources/tck-audit.xml`) as per the latest spec revision and check that it was identical to the preexisting file. If not, you will probably need to update the TCK assertion ids accordingly.
-* Check that everything has been pushed to the upstream repository
-* Check that CI is green
-* Check that the BV and HV versions referenced in the parent pom.xml are alright (non SNAPSHOT and pointing to the right release)
-* Before you release, deploy the TCK and run the Validator tests with this version of the TCK to check everything is OK (run the TCK in container mode)
-* Make sure there are no outstanding issues in https://hibernate.atlassian.net/browse/BVTCK[Jira]
-
-== Release
-
-* Release the https://hibernate.atlassian.net/plugins/servlet/project-config/BVTCK/versions[Jira version]
-* Do NOT update the `changelog.txt` and `README.md`, the release job does it for you.
-* Go to CI, and select the beanvalidation-tck-release job. Click on Build with parameters.
-** *Be careful when filling the form with the build parameters.*
-* Release the artifacts on the JBoss Nexus repository manager. This is a two-steps process.
-** Log into https://repository.jboss.org/nexus/index.html[Nexus] and examine https://repository.jboss.org/nexus/index.html#stagingRepositories[your staging repository]. Click on the _Updated_ column 2 times to have the repositories sorted correctly.
-** You can either drop it in order to start over again or you can close and promote it making the artifacts available in the live repository. (Click _Refresh_ after each action)
-** You can find more information in the description of https://developer.jboss.org/docs/DOC-14608[the JBoss project release process]. A Maven settings.xml for testing the artifacts in the staging repository can be found https://developer.jboss.org/docs/DOC-15664[here].
-* Transfer the released issues in JIRA to the _Closed_ state. You can use this search https://hibernate.atlassian.net/issues/?jql=project%20%3D%20BVTCK%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%202.0.0.Alpha1[Issue Navigator - Hibernate JIRA] and select another `fixVersion`. Once you have selected the right version, click on the button with three dots at the top right of the screen and click on _Bulk update all XX issues_. Use the _Transition_ action to transition your issues from _Resolved_ to _Closed_.
-
-== Publish
-
-NOTE: In the HTML version of the reference guide, some special characters and the section titles will show up not correctly when opening the file locally. This is a known issue, the documentation looks correct when retrieved via Apache.
-
-The CI job automatically pushes the distribution to SourceForge and publishes the documentation to docs.jboss.org.
+WARNING: Bean Validation has been moved to Jakarta EE thus, see https://github.com/jakartaee/validation/blob/main/MAINTAINERS.md[MAINTAINERS.md] for release process.

validator/documentation/releasing-hibernate-validator.adoc

@@ -2,54 +2,4 @@
 :awestruct-layout: project-standard
 :awestruct-project: validator
 
-== Release Process
-
-Follow these steps for an official release.
-
-=== Prerequisites
-
-You need to have access to https://ci.hibernate.org/: the release process is now driven by CI.
-
-=== Prepare
-
-* Update the version of validation-api and tck in `pom.xml` if need be
-* Update the version of tck in `pom.xml` if need be
-* Check that everything has been pushed to the upstream repository
-* Check that CI is green for the branch you want to release
-* Before you release try the latest snapshot of Validator in Core to make sure the snapshot works in Hibernate ORM.
-** Use the HV snapshot version in https://github.com/hibernate/hibernate-orm/blob/master/gradle/libraries.gradle[libraries.gradle]
-** Run either the full ORM build or hibernate-core and hibernate-entitymanager
-** A `./gradlew test` in the ORM directory should be sufficient
-* Double check that `distribution/pom.xml` and `distribution/src/main/assembly/dist.xml` list and include all the right dependencies (this is especially important when dependencies changed).
-* Make sure there are no outstanding issues in https://hibernate.atlassian.net/browse/HV[Jira]
-* On https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HV%20AND%20fixVersion%20%3D%206.0.0.Alpha1%20AND%20component%20%3D%20EMPTY%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC[Jira (adjust the fixVersion)] check that all the issues referenced in this version have a Component set
-
-=== Release
-
-* Release https://hibernate.atlassian.net/projects/HV?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=released-unreleased[the Jira version]
-* Do *NOT* update the changelog.txt and README.md, the release job does it for you.
-* Go to CI, and select https://ci.hibernate.org/view/Validator/job/hibernate-validator-release/[the hibernate-validator-release job]. Click on Build with parameters.
-** *Be careful when filling the form with the build parameters.*
-* Release the artifacts on the OSSRH repository manager. This is a two-steps process.
-** Log into https://oss.sonatype.org/[OSSRH] and examine your https://oss.sonatype.org/#stagingRepositories[staging repository].
-** You can either `Drop` it in order to start over again or you can `Close` and `Release` it making the artifacts available in the live repository. (Click `Refresh` after each action)
-* Transfer the released issues in JIRA to the Closed state. You can use this search https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HV%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%205.3.0.CR1[Issue Navigator - Hibernate JIRA] and select another fixVersion. Once you have selected the right version, click on the button with three dots at the top right of the screen and click on Bulk update all XX issues. Use the Transition action to transition your issues from Resolved to Closed.
-
-=== Publish
-
-NOTE: In the HTML version of the reference guide, some special characters and the section titles will show up not correctly when opening the file locally. This is a known issue, the documentation looks correct when retrieved via Apache. 
-
-The CI job automatically pushes the distribution to SourceForge and publishes the documentation to docs.jboss.org.
-
-=== Announce
-
-* Update the migration guide: https://github.com/hibernate/hibernate.org/blob/production/validator/documentation/migration-guide.adoc
-* Blog about the release on in.relation.to. Add the tag 'Hibernate Validator' to the  post so it will also appear on the Hibernate Validator project page.
-* Update https://github.com/hibernate/hibernate.org[hibernate.org]:
-** If it is a new major release, add a `_data/projects/validator/releases/series.yml` file and a `validator/releases/<version>/index.adoc` file
-** Add a new release file to `_data/projects/validator/releases`
-* Depending on which series you want to have displayed, make sure to adjust the displayed flag of the `series.yml` file of the old series
-* Deploy to production
-* Send an email to mailto:hibernate-dev@lists.jboss.org[hibernate-dev] and mailto:hibernate-announce@lists.jboss.org[hibernate-announce]
-* Twitter via https://twitter.com/Hibernate[Hibernate] user
-
+WARNING: The maintainer's guide is moved to the project sources: https://github.com/hibernate/hibernate-validator/blob/main/MAINTAINERS.md[MAINTAINERS.md]