Supported Versions

Spring Boot Support Policy

Spring Boot follows the VMware Tanzu OSS support policy for critical bugs and security issues.

Major versions will be supported for at least 3 years from the release date (but you must run a supported minor version).
Minor versions will be supported for at least 12 months.

Commercial support is also available from VMware which offers an extended support period.

All Spring Boot releases are publicly available from Maven Central and https://repo.spring.io. We do not have a private repository reserved only for paying customers.

End of Life

Spring Boot releases are marked as "end of life" when they are no longer supported or released in any form. If you are running an EOL version, you should upgrade as soon as possible.

Spring Boot releases are usually marked end of life 21 months after they were released.

Please note that a version can be out of support before it is end of life. During this time you should only expect releases for critical bugs or security issues.

Releases

Release Schedule

Spring Boot releases a new major or minor version every six months (in May and November). We aim to release on the Thursday after the 3rd Monday of the month. This is usually, but not always, the 3rd Thursday of the month.

Patch releases are published as necessary.

As much as possible, we recommend that all users migrate to the latest supported release.

Released Versions

The following releases are actively maintained:

Version	Released	OSS Support Until	Expected End of Life
2.5.x	20 May 2021	19 May 2022	23 February 2023
2.4.x	12 November 2020	18 November 2021	18 August 2022
2.3.x	15 May 2020	20 May 2021	24 February 2022

The following releases are end of life:

Version	Released	End of Life	Notes
2.2.x	October 2019	July 2021
2.1.x	October 2018	November 2020
2.0.x	March 2018	April 2019
1.5.x	January 2017	August 2019	Last in the `1.x` line.

Release Compatibility

As much possible, Spring Boot patch releases should be back-compatible with previous releases.

Minor and major releases might contain back-incompatible API changes. When feasible, a back-compatible API will be left in place and marked as deprecated to inform API clients that the API is no longer recommended for use. Deprecation comments will include the version in which the API was first deprecated, the suggested replacement and the version that is scheduled to remove the code. Once an API is marked as deprecated, it will be left in place for at least two minor releases. For example, an API marked @deprecated since 2.2.0 would be subject for removal in a 2.4.0 release.

Third-party dependencies

Spring Boot provides managed dependencies for many third-party libraries. These libraries are upgraded only at the patch level for any given Spring Boot patch release. Minor and major version upgrades of third-party libraries are only applied in Spring Boot minor or major releases. You should check the EOL policies of projects that you depend on since you may find that you’re using a supported version of Spring Boot against an unsupported third-party library.