Why did Spring Framework 7 move from Jakarta EE 10 to Jakarta EE 11?

Jakarta EE 10 was the baseline Spring 6 introduced back in 2022, and the Jakarta EE community has continued advancing the underlying specifications since then - Servlet 6.1, WebSocket 2.2, Bean Validation 3.1, and JPA 3.2 all carry refinements that Servlet 6.0 and its 2022-era siblings didn't have.

Staying on Jakarta EE 10 indefinitely would mean Spring couldn't take advantage of those specification-level improvements, and would eventually fall out of step with the application servers themselves - Tomcat and Jetty's newest major releases target the newer Jakarta EE generation, so a framework stuck on the older spec level would either need compatibility shims or would simply stop being deployable on current server versions. Moving to Jakarta EE 11 alongside the broader Spring Framework 7 generational bump lets Spring track the servlet ecosystem's own forward motion in one coordinated step rather than patching around an aging baseline indefinitely.