Issues

Switch to log4j2 in performance tests

Align Jakarta API versions with the Jakarta EE 11

Update version.org.jboss.logging.jboss-logging-tools from 3.0.0.Final to 3.0.1.Final

Test against latest Wildfly 33.0.0

Update to OpenJFX 17.0.12

Update Arquillian dependency management configuration

Clean up configuration of the performance tests

Update Jakarta specification names where applicable

hibernate-validator-test-utils are not compatible to current AssertJ versions

Add a nightly job to verify the build reproducibility

Update org.jboss.logging:jboss-logging-processor from 2.2.1.Final to 3.0.0.Final

Brazilian Titulo Eleitoral not correctly validating on some scenarios

Generate module-info for published artifacts

Use URI for @URL validation

New Alphanumeric CNPJ

Reproducible builds

Stop publishing test modules

Create and publish Hibernate Validator BOM

Test against latest Wildfly 32.0.1

Stop publishing and remove hibernate-validator-modules

Simplify the checks whether the path was already validated

Switch to a different sigtest-maven-plugin

Upgrade to JDK 17 as the baseline and drop JDK 11 compatibility

Test Hibernate Validator against JDK 24

Update documentation examples to use the min required Java version where applicable

Upgrade jboss-logging to latest version (3.6.0)

Add impsort and formatter plugins

Bump joda-time to 2.12.7

Bump jboss-logging to 3.5.3.Final

Bump com.fasterxml:classmate to 1.7.0

Bump javax.money:money-api to 1.1

Use Maven 3.9.6 in CI builds and as a required minimum version for the build

Update gpg plugin configuration

Upgrade to jakarta.validation-api 3.1.0

Expression Language not propagated to iterable node

Enable dependabot updates for more dependencies

Remove Security Manager usage

Update maven build configuration to address lib/plugin upgrades from Dependabot

Bitcoint address validation

CNPJ with all digits the same

Add South Korean specific RRN annotation

Test Hibernate Validator against JDK 23

Force user.country when testing

Typo in CrossParameterConstraintValidatorContextImpl, wrong element kind assertion fail message.

Typo fix for Ukrainian localization

PathImpl.createCopy() only performs a shallow copy

Some french validation messages are not quite accurate

Add an option to validate class-level constraints only if all property constraints are valid