You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`main`| version `2.x` supporting Spring Boot `4.x`|[][maven-central]|
198
-
|`release-v1.*.x`| version `1.x` supporting Spring Boot `3.x`|[][maven-central]|
197
+
|`main`| version `2.x` supporting Spring Boot `4.x`|[][maven-central]|
198
+
|`release-v1.*.x`| version `1.x` supporting Spring Boot `3.x`|[][maven-central]|
199
199
200
200
## Problem4J Links
201
201
@@ -239,14 +239,14 @@ version. By default, the version is derived from git commit hash.
|`main`| version `2.x` supporting Spring Boot `4.x`|[][maven-central]|
17
-
|`release-v1.*.x`| version `1.x` supporting Spring Boot `3.x`|[][maven-central]|
16
+
|`main`| version `2.x` supporting Spring Boot `4.x`|[][maven-central]|
17
+
|`release-v1.*.x`| version `1.x` supporting Spring Boot `3.x`|[][maven-central]|
18
18
19
19
Bugfixes for `1.x` should be merged into the lowest applicable `1.x` release branch. From there, they are cascaded
20
20
forward into newer version branches if applicable, so fixes propagate through the release line without being duplicated
@@ -35,8 +35,8 @@ issue is critical or a change can be backported with minimal effort.
0 commit comments