Creuto is now an OpenAI Select Partner Read More

Software Architecture & Technical

Spring Boot 3.5 end of life: aim for 4.1, not 4.0

Spring Boot 3.5 end of life passed on 30 June 2026 and 4.0 follows on 31 December. See the dates, what breaks, and why 4.1 is the target.

Spring Boot 3.5 end of life: aim for 4.1, not 4.0

Spring Boot 3.5 end of life arrived on 30 June 2026, and Spring Boot 4.0's open-source support ends on 31 December 2026, so a team that lands on 4.0 this month gets about six weeks of free fixes. Aim for 4.1, which runs to 31 July 2027, and treat 4.0 as a stop on the way.

We have not run a Spring Boot 4 migration for a client, so this post rests on Spring's own documentation and release notes, read on 17 November 2026. Where a figure comes from a third-party aggregator instead, we say so.

The Spring Boot 3.5 end of life dates, side by side

Spring's support policy gives each minor version at least 12 months of open-source support, ships a new major or minor every May and November, and points to commercial support for anything longer. Spring's per-version table renders in the browser and we could not read it, so the dates below come from endoflife.date. Each open-source window is about 13 months, which fits that policy. Confirm the 4.1 date on spring.io before it goes into a plan. All dates are as of 17 November 2026.

LineOpen-source support endsCommercial support ends
Spring Boot 2.730 Jun 202330 Jun 2029
Spring Boot 3.431 Dec 202531 Dec 2026
Spring Boot 3.530 Jun 202630 Jun 2032
Spring Boot 4.031 Dec 202631 Dec 2027
Spring Boot 4.131 Jul 202731 Jul 2028
Spring Framework 6.230 Jun 202630 Jun 2032
Spring Framework 7.031 Jul 202731 Jul 2028

Two things stand out. Spring Framework 7.0 outlives Spring Boot 4.0 by seven months, so the Boot line is the one that expires first. And the commercial window for Boot 3.4 closes on 31 December 2026, the same day the free window for 4.0 does. The Spring Framework versions page agrees on the 6.2 date and names 7.1 as the next feature branch for November 2026.

Boot itself is moving too. Spring published 4.2.0-RC2 on 6 November, and the 4.2 release notes say they will appear once it ships. We found no published support dates for 4.2, so the plan below targets 4.1 and treats 4.2 as the next step.

Why aim for 4.1, not 4.0

The 3.5-to-4.0 move is the large one, and a programme that finishes in January lands on a line with no free fixes. The step from 4.0 to 4.1 is smaller. The 4.1 release notes list what changes on that hop:

  • Everything deprecated in 4.0 is removed, so any call to a deprecated method fails to compile.
  • Passing -DskipTests no longer skips AOT processing of tests; the Maven plugin now reacts only to maven.test.skip.
  • The deferred Spring Data JPA bootstrap mode throws if no suitable AsyncTaskExecutor bean exists.
  • jOOQ 3.20 is now the supported version, and it requires Java 21 or later.

The strongest case for stopping at 4.0 is that Spring documents the hops separately: the 4.0 migration guide starts from the latest 3.5.x, and the 4.1 notes start from 4.0. We found no Spring statement about going from 3.5 straight to 4.1, so we would run it as two steps inside one programme. Migrate to the latest 4.0.x with the guide, then take 4.1.x before release. Stopping at 4.0 is only the right call when a dependency you cannot replace has no 4.1-compatible release yet. In that case 4.0 is a temporary landing with a hard stop on 31 December.

What the move to Spring Boot 4 breaks

The official guide and the Spring Framework 7.0 release notes name the changes that cost real time:

  • Baselines. Boot 4.0 requires Java 17 or later, Jakarta EE 11, a Servlet 6.1 baseline and Spring Framework 7.x. The Framework team recommends JDK 25 for production use with 7.x.
  • Servers and persistence. Framework 7 raises the minimums to Tomcat 11.0 or Jetty 12.1, JPA 3.2 with Hibernate ORM 7.1 or 7.2, and Bean Validation 3.1. Undertow support is dropped because Undertow is not yet compatible with Servlet 6.1.
  • The javax leftovers. Framework 7 no longer supports the javax.annotation and javax.inject annotations. Code still using @PostConstruct or @Inject from those packages must move to the jakarta equivalents.
  • Jackson 3. Jackson 3 becomes the preferred JSON library, and the group ID changes from com.fasterxml.jackson to tools.jackson, except for jackson-annotations. Defining an ObjectMapper bean no longer customises the auto-configured mapper; you define a JsonMapper or XmlMapper instead. A deprecated spring-boot-jackson2 module exists as a stop-gap and Spring says it will be removed in a future release.
  • Starters. Boot is now modular, with a starter per technology. Classic starters (spring-boot-starter-classic and spring-boot-starter-test-classic) keep an old build working, but the guide recommends moving off them eventually.
  • Tests. @MockBean and @SpyBean are removed in favour of @MockitoBean and @MockitoSpyBean, and @SpringBootTest no longer provides MockMvc unless you add @AutoConfigureMockMvc.
  • Quiet defaults. Liveness and readiness probes are now enabled by default,, and the temporary spring-boot-properties-migrator module reports renamed properties at startup.

Spring Security 7 and Jackson 3: the part the Boot guide defers

Boot 4.0 ships with Spring Security 7.0, and the Boot guide leaves its changes to the Spring Security migration guide. That guide says 6.5 is the last 6.x release and recommends updating to 6.5 and using its preparation steps first. After that, take the latest patch of Boot 4.0 and the latest Spring Security 7.

The Jackson change reaches into security code. Configuration that used an ObjectMapper with SecurityJackson2Modules should become a Jackson 3 JsonMapper.Builder with SecurityJacksonModules, and the authorization server now uses Jackson 3 by default. Spring says Jackson 3 support writes a format compatible with the deprecated Jackson 2 one, so objects serialised with Jackson 2 should still deserialise. If you persist security objects such as sessions, test that on real data rather than assume it. We did not read the Servlet and Reactive steps in that guide, so budget time to read them.

Which route your estate takes

Where you areSupport positionRoute
Boot 3.5Open-source support ended 30 Jun 2026Update to the latest 3.5.x, clear deprecation warnings, migrate to 4.0.x, then take 4.1.x
Boot 4.0Open-source support ends 31 Dec 2026Move to 4.1.x using the 4.1 release notes
Boot 3.4Commercial support ends 31 Dec 2026Reach 3.5.x first, then follow the 3.5 route
Boot 2.7 or olderOpen-source support ended 30 Jun 2023 for 2.7The 4.0 guide starts from 3.5.x, so a 3.x leg comes first; we have not covered that leg here

What to do with services you cannot move this quarter

Your applications keep running after an end-of-life date, but open-source support is what delivers fixes for critical bugs and security issues, so a vulnerability found on 3.5 from now on gets no free patch. Start with an inventory: which services run which line, which face the internet, and which use Undertow, Jackson 2 customisation or security configuration. Those three decide how hard each service is to move.

For the services that must wait, there are paid options. Spring's own support page advertises extended support beyond open-source end of life from the Spring maintainers. Third-party vendors sell it too: HeroDevs, OpenLogic and TuxCare each describe long-term support for end-of-life Spring lines on their own sites. We have not evaluated any of them, none of those pages states a price, and the commercial dates in the table above are endoflife.date's, not a promise from any one vendor. Treat a support contract as a bridge with an end date written down, not as the plan.

Spring is not the only runtime on a calendar this quarter. We have covered .NET 8 end of support on 10 November and Angular 20 end of life on 28 November in the same terms, and Windows Server 2016 end of support, where the application is the problem. If several of these land on one team, the sequencing matters more than any single date.

Scoping a Spring Boot migration plan with us

If you are weighing a Spring Boot 3.5 to 4.1 migration, we can help you inventory the services, sequence the moves and decide which ones to bridge. Our legacy application modernization team scopes plans like this from your dependency list and Spring's own guides, so the 31 December and 31 July dates stay visible in the plan.

Frequently asked questions

Spring Boot 3.5's open-source support ended on 30 June 2026, according to endoflife.date, which fits Spring's policy of at least 12 months per minor version. Spring Framework 6.2 ended the same month. The same source lists commercial support for 3.5 running to 30 June 2032.

Spring Boot 4.0 is supported by the open-source project until 31 December 2026, according to endoflife.date, which is about six weeks after this post's date. Its commercial support is listed to 31 December 2027. Teams migrating now should plan to land on 4.1, which is listed to 31 July 2027.

Aim for 4.1. Spring documents the 3.5 to 4.0 move in one guide and the 4.0 to 4.1 move in the 4.1 release notes, so run them as two steps in one programme. Stop at 4.0 only if a dependency has no 4.1-compatible release, and then set 31 December 2026 as the hard stop.

Spring Boot 4.0 requires Java 17 or later, according to Spring's migration guide, and the Spring Framework team recommends JDK 25 for production use with Framework 7. Spring Boot 4.1 supports jOOQ 3.20, which requires Java 21 or later, so a jOOQ user needs Java 21.

A Spring Boot 3.5 application keeps running, but the open-source project no longer issues fixes for critical bugs and security issues on that line. Fixes then come only from a paid commercial support contract, so write an end date for each exception and track the services that rely on one.

Written by

Akash Mohapatra

Akash Mohapatra

Co Founder & Director

16 Nov 2026

·

7 min read

Share

LET'S CONNECT

Connect with Creuto!

Ready to take the first step towards unlocking opportunities, realizing goals, and embracing innovation? We're here and eager to connect.