Incorrect version of jakarta.validation-api 3.1.0 instead of 3.0.2 starting with swagger-core-jakarta 2.2.25

[mjschwaiger]

Version 2.2.25 and newer of swagger-core-jakarta and define version 3.1.0 instead of 3.0.2 of component jakarta.validation-api.

The current version definition was introduced in swagger-core-jakarta:2.2.25 in pull request 4740 where ${jakarta.validation-version} was updated from 3.0.2 to 3.1.0. This may have happened accidentally.

Jakarta (Bean) Validation versions

• jakarta.validation-api:3.1.0 is the release for Jakarta 11 EE.
• jakarta.validation-api:3.0.2 is the release for Jakarta 10 EE
• jakarta.validation-api:3.0.0 is the release for Jakarta 9 EE

See https://jakarta.ee/specifications/bean-validation/ for more details.

The baseline for Spring Boot 3.x and Spring Framework 6.x is Jakarta 10 EE, so components such as swagger-core-jakarta should not update this baseline to versions based on Jakarta 11 EE, which will be the baseline for Spring Boot 4.x and Spring Framework 7.x.

The rest of the Jakarta components (e.g. jakarta.ws.rs-api:jar:3.1.0) are also based on Jakarta 10 EE.

Example: this would resolve to jakarta.validation-api:3.1.0 which is the release for Jakarta 11 EE

dependencies {
  implementation("org.springframework.boot:spring-boot-starter:3.4.3") /* based on Jakarta 10 EE */
  implementation("org.springdoc:springdoc-openapi-starter-webmvc-ui:2.8.5")
}

In fact, you would expect this to resolve to jakarta.validation-api:3.0.2.

So my suggestion would be to reverse this change and create a new version.

[T3rm1]

This project is not related to Spring. So that's not an issue. Also there are no backwards incompatible changes in Jakarta Validation 3.1. The only real issue I see is, that Jakarta Validation 3.1 now requires Java 17 instead of previously Java 8 as minimum.