Spring Boot 4.1 end of support on 31 July 2027: the 2027 support calendar

Summary. Spring Boot 4.1 loses open-source (OSS) support on 31 July 2027, and Spring Framework 7.0, which sits under both Boot 4.0 and 4.1, leaves OSS support the same day. Boot 4.0 goes first: its OSS support ends on 31 December 2026, with commercial support to 31 December 2027. Boot 4.1 shipped on 10 June 2026, is on patch 4.1.2 and keeps commercial support until 31 July 2028. Boot 4.2 and Framework 7.1 are on Spring's release calendar for 19 November 2026; 4.2 then gets OSS support to 31 December 2027 and commercial support to 31 December 2028. The 3.x line is already out of OSS support: 3.5 ended on 30 June 2026 but, as the last 3.x minor, keeps commercial support until 30 June 2032. Spring's policy sets the rhythm: 13 months of OSS support per Boot minor, 12 more for subscribers, and five extra years for the last minor of a major. Java 17 remains the floor for 4.1 and 4.2, which are compatible up to Java 27. Our advice: move 4.0 services before 31 December 2026, move 4.1 services to 4.2 in the first half of 2027, budget for another upgrade by 31 December 2027, and buy commercial support only for systems that cannot keep pace.

About this article. For engineering leads and architects running Spring Boot in production. On 7 November 2026 we checked every date against Spring's support policy, the project support pages and the api.spring.io data behind them, Spring's release calendar, the Boot documentation and release notes, Broadcom's enterprise pages and Oracle's JDK release notes; legal references are the DPDP Act, 2023 as gazetted on 11 August 2023 and GDPR Article 32 (archived EUR-Lex copy). This is not legal advice, Broadcom publishes no support prices, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.

If your estate also runs Python services, our Django 6.2 LTS upgrade guide covers the matching 2027 move.

The 2027 Spring Boot calendar at a glance

The dates below come from Spring's generations data and release calendar, read on 7 November 2026.

Two facts shape late 2027. The calendar shows 4.0.10 on 19 November as the last OSS 4.0 patch before the cut-off (December brings only enterprise builds), and the generations data lists no Boot line after 4.2. Unless a newer line ships before 31 July 2027, 4.2 will be the only Boot generation with OSS support from August, and its window closes on 31 December 2027. Plan one more upgrade in late 2027, to a version with no published date yet.

Every Spring Boot generation with some support left

The generations data also records the latest public and enterprise patch for each line; Maven Central supplies the last public 2.7 release.

Spring rounds release dates to the month end, so every end date is a month's last day. Broadcom's enterprise policy gives the rule: Spring Boot 2.7.0 came out on 19 May 2022 and its OSS support ran to 30 June 2023, 13 months later rounded to the month end. The same arithmetic gives 31 July 2027 for 4.1, released on 10 June 2026, and 31 December 2027 for 4.2.

The extended label marks the last minor of a major line, the only release that gets five more years of enterprise support. No 4.x generation carries it yet, and Spring has not said which 4.x minor will be the last.

Spring Framework 7 and the Java baseline

Boot's dates follow the framework underneath: Framework 7.0.x maps to Boot 4.0.x and 4.1.x, and 7.1.x to Boot 4.2.x. So 31 July 2027 also binds applications that use Spring Framework 7.0 without Boot. Requirements below are from each line's system requirements page.

Boot itself still asks only for Java 17, so a 4.x upgrade does not force a JDK change. Dependencies can: the 4.1 release notes move the supported jOOQ version to 3.20, which needs Java 21. The 4.0 migration guide encourages the latest Java LTS release, and a Boot upgrade is a sensible moment to move production to Java 21 or 25.

The JDK build is also a licensing question. Oracle JDK 21.0.13, released on 20 October 2026, is the first JDK 21 update under Oracle's OTN licence, which keeps personal and development use free but may not cover uses the earlier terms allowed. Our Oracle JDK 21 licence and Java audit guide covers the options, including free OpenJDK builds. Broadcom's Spring subscription includes support for BellSoft's Liberica OpenJDK.

Undertow is the other casualty: it did not support Servlet 6.1, so Boot 4.0 dropped its starter and embedded server. Services on Undertow must move to Tomcat 11 or Jetty 12.1.

OSS support versus commercial support

The two tiers below come from Spring's support policy and Broadcom's enterprise pages.

Three practical points follow. First, enterprise builds come from a separate Maven repository at packages.broadcom.com, so buying support also means changing build configuration and credentials. Second, Broadcom calls its enterprise releases quarterly, the calendar lists enterprise Boot builds on 19 November and 17 December 2026, and spring.io advertises day-zero access to security patches for enterprise customers. Third, commercial support buys time, not compatibility: the code still has to move, and the gap widens with each new minor, roughly every six months.

endoflife.date also lists HeroDevs' Never-Ending Support as an extended-support option; we have not compared its terms, and its dates are not part of Spring's schedule.

Pick your path

Deadlines follow the generations data.

Upgrade checklist: Spring Boot 4.0 or 4.1 to 4.2

1. Inventory every service. Record each deployable's Boot version, Spring Cloud train, JDK and embedded server, and map it to the calendar above.

1. Move to the latest patch of your current line. That is 4.0.9 or 4.1.2, announced on 23 October 2026, with 4.0.10 and 4.1.3 on the calendar for 19 November. Patch releases carry the security fixes and the cleanest deprecation warnings.

1. Clear deprecations before each minor upgrade. Boot 4.1 removed what 4.0 deprecated, and the 4.2 milestone notes remove what 4.1 deprecated.

1. Run the properties migrator. Add spring-boot-properties-migrator as a runtime dependency; it reports renamed or removed configuration keys at startup and migrates them temporarily. Remove it when you are done. From 4.2 it can also be set to fail startup on errors or warnings.

1. Apply the 4.1 changes if you are on 4.0. The layertools jar mode is gone (use tools), -DskipTests no longer skips AOT processing of tests (use maven.test.skip), Spring Data JPA bootstrap modes behave differently, Reactor HTTP client builders now apply system proxy settings, and Derby support is deprecated because the Derby project has been retired.

1. Apply the 4.2 changes. RestTemplate support and TestRestTemplate are deprecated in favour of RestClient and RestTestClient; spring-boot-starter-amqp users must pick spring-boot-starter-rabbitmq for AMQP 0.9 or spring-boot-starter-amqp-rabbitmq for AMQP 1.0; servlet-specific Tomcat properties move under server.tomcat.servlet; and the default Buildpacks builder now produces Ubuntu 26.04 images.

1. Check dependencies Boot does not manage. Projects such as Spring Cloud carry their own versions, so confirm the compatible release train before bumping Boot. Spring Cloud 2026.0.0, whose RC2 is built on Boot 4.2.0-RC2, is also scheduled for 19 November 2026.

1. Move to 4.2.0 after general availability. Read the final 4.2 release notes at GA; until then the wiki points to the milestone notes.

1. Test on your production JDK, then roll out service by service. Keep Java 17 as the build floor if you publish libraries, canary one low-risk service, compare error rates and latency, then batch the rest.

For Maven, move the parent and add the migrator for the duration of the upgrade:

            <parent>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-parent</artifactId>
  <version>4.2.0</version>
</parent>

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-properties-migrator</artifactId>
  <scope>runtime</scope>
</dependency>
          

Gradle builds add the same module to the runtimeOnly configuration. Broadcom's enterprise offering also includes Application Advisor, which automates upgrade guidance.

For Spring Boot 3.5 teams: what the 4.x move involves

Spring's 4.0 release notes say that, as a major release, the upgrade can be more involved than usual, point to a dedicated migration guide, and recommend reaching 3.5 first. The main items from that guide:

• Start from the latest 3.5.x. Anything deprecated in 3.x is removed in 4.0, so clear those warnings first.

• Platform baseline. Java 17 or later, Kotlin 2.2 or later, GraalVM 25 or later for native images, Jakarta EE 11 and Servlet 6.1, and Spring Framework 7.x.

• Modular starters. Boot 4 ships smaller, focused modules. Features that used to work with only a third-party jar now need a starter; Flyway and Liquibase users need spring-boot-starter-flyway or spring-boot-starter-liquibase. Adding spring-boot-starter-classic restores the old classpath as an intermediate step.

• Jackson 3 by default. Packages move from com.fasterxml.jackson to tools.jackson, except the annotations, and Jackson 2 remains only as a deprecated module. @JsonComponent becomes @JacksonComponent, and replacing the auto-configured mapper now means defining a JsonMapper bean, not an ObjectMapper.

• Removed features. Undertow, embedded launch scripts for fully executable jars, Spring Pulsar Reactive auto-configuration, and direct Spring Session Hazelcast and MongoDB support. Spock integration went in 4.0 and came back in 4.1.

• Nullability. Boot 4 adds JSpecify annotations, which can break Kotlin builds and builds that run a null checker.

• The rest of the portfolio. Spring Security 7, Spring Batch 6, Spring Data 2025.1, Spring Integration 7 and Spring for Apache Kafka 4 each have their own notes.

A 3.5 team going straight to 4.2 applies the 4.0 guide, then the 4.1 and 4.2 notes, and avoids paying for a 4.0 or 4.1 hop that loses OSS support within months.

Worked example: cover bought by each upgrade

Take a service still on Boot 4.0 at the end of February 2027. The table counts months of cover from the published end dates: March to July 2027 is five months, March to December is ten.

Moving to 4.2 buys twice the cover of 4.1 for similar work, since the path from 4.0 to 4.2 includes every 4.1 change. A subscription buys the same ten months on 4.0 but leaves a bigger jump for late 2027. On 3.5, a subscription taken out now covers about 67 months, from 7 November 2026 to 30 June 2032, the realistic option for systems that are hard to change.

Compliance and procurement notes

Running a framework line with no security fixes is hard to defend in an audit. Section 8(5) of India's Digital Personal Data Protection Act, 2023 requires organisations that control personal data to protect it with reasonable security safeguards against breaches, and Article 32 of the EU GDPR requires security measures appropriate to the risk. Our DPDP Rules compliance checklist maps the Indian duties and dates. Commercial support is a contract with Broadcom, so allow time for procurement before 31 July 2027. If several frameworks are ageing out at once, our application modernisation guide covers sequencing.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our Java development team runs Spring Boot upgrades as planned programmes, from a version inventory of every service through the 3.5 to 4.x migration to wave-by-wave canary roll-outs. Talk to us at /contact-us/.

Last updated: 7 November 2026.

References

1. Spring Boot project generations (support dates data) — Spring

1. Spring Framework project generations (support dates data) — Spring

1. Spring release calendar data, June to October 2026 — Spring

1. Spring Boot 4.1.2 available now, 23 October 2026 — Spring

1. Spring release calendar data, November to December 2026 — Spring

1. Support Policy — Spring

1. Enterprise Releases and support policy — Broadcom (Spring Enterprise)

1. System Requirements, Spring Boot 4.1.2 — Spring

1. System Requirements, Spring Boot 4.2.0-RC2 — Spring

1. Spring Boot enterprise releases — Broadcom (Spring Enterprise)

1. spring-boot release metadata — Maven Central

1. System Requirements, Spring Boot 3.5.16 — Spring

1. System Requirements, Spring Boot 4.0.9 — Spring

1. Spring Boot 4.1 Release Notes — Spring Boot wiki on GitHub

1. Spring Boot 4.0 Migration Guide — Spring Boot wiki on GitHub

1. JDK 21.0.13 Release Notes, 20 October 2026 — Oracle

1. Spring Boot project page and support tab — Spring

1. Spring Boot release and support schedule — endoflife.date

1. Spring Boot 4.0.9 available now, 23 October 2026 — Spring

1. Spring Boot 4.2.0-M1 Release Notes — Spring Boot wiki on GitHub

1. Spring Boot 4.2.0-RC1 Release Notes — Spring Boot wiki on GitHub

1. Spring Boot 4.2.0-M2 Release Notes — Spring Boot wiki on GitHub

1. Spring Cloud 2026.0.0-RC2 has been released, 5 November 2026 — Spring

1. Spring Boot 4.2 Release Notes — Spring Boot wiki on GitHub

1. Application Advisor — Broadcom (Spring Enterprise)

1. Spring Boot 4.0 Release Notes — Spring Boot wiki on GitHub

1. The Digital Personal Data Protection Act, 2023 (No. 22 of 2023), Gazette of India, 11 August 2023 — Ministry of Electronics and Information Technology

1. Regulation (EU) 2016/679 (General Data Protection Regulation), archived EUR-Lex text — Publications Office of the European Union