$ the-wire · showcase
Kubernetes probe groups keep their defaults; multi-segment health paths land
By RepoJournal · Filed · About Spring · Composed from the cited sources · methodology
Spring Boot fixed the health-group regression that could take down Kubernetes probes, and Spring Security's 7.2 milestone work has already propagated into Spring Session and Boot's build.
Retain probe defaults when configuring other properties on probe health groups spring-projects/spring-boot
Configuring `additional-path` or any unrelated property on the `liveness` or `readiness` health groups used to redefine them with an empty `include` set, matching every indicator (including `diskSpace` and `rabbit`) and letting unrelated failures trip Kubernetes probes. `AvailabilityProbesHealthEndpointGroups` now retains the probe defaults so those groups keep matching only `livenessState`/`re...
Support multi-segment additional health endpoint paths spring-projects/spring-boot
A health group's `additional-path` now accepts multi-segment values on either the main or management server, with routing resolving the group by longest matching prefix. Spring MVC's exact-path handling now forwards the complete path consistently with WebFlux and Jersey, and a shared integration fixture covers all three web stacks.
Start building against Spring Security 7.2.0-M2 snapshots spring-projects/spring-boot
Boot's build now points at Spring Security 7.2.0-M2 snapshots, matching the milestone Spring Session has already adopted in its own Security bump.
Update Spring Security to 7.2.0-M1 (#3969) spring-projects/spring-session
Spring Session moved to Spring Security 7.2.0-M1, alongside a Lettuce bump to 7.7.0.RELEASE and Jackson to 3.1.6. Applications tracking the milestone train should expect to align Spring Security across Boot and Session rather than run them a version apart.
Deprecate AppOptics as it has retired spring-projects/spring-boot
AppOptics is deprecated across Boot because the service has retired, and the `spring-data-envers` links are gone from the docs now that the module lives inside spring-data-jpa. The rest of the wire is housekeeping: Reproducible Builds configuration landed in Spring Security, spring-security-kerberos, and Spring LDAP, the latter also picking up Micrometer 1.18.0-M1 and Micrometer Tracing 1.8.0-M1.