-
Notifications
You must be signed in to change notification settings - Fork 177
Supported Versions
Spring Cloud follows the VMware Tanzu OSS support policy for critical bugs and security issues.
- Major versions are supported for at least 3 years from the release date (but you must run a supported minor version).
- Minor versions are supported for at least 12 months.
Commercial support is also available from VMware, which offers an extended support period.
All Spring Cloud releases are publicly available from Maven Central and https://repo.spring.io. We do not have a private repository reserved only for paying customers.
We recommend that all users migrate to the latest GA release.
Release Trains are a collection of individual projects. As such, release trains do not have a support timeline of their own but, rather, have a cumulative support timeline based on each included project.
While release trains do not have a support timeline, you can assume all the projects within a given release train are still supported if the latest Spring Boot version supported by a given release train is still supported. In general projects within a given Spring Cloud release train will no longer be supported within 3 months after Spring Boot ends its support. Spring Boot support timelines can be found here.
For example, Spring Cloud 2021.0 (Jubilee) supports Spring Boot 2.7.x and 2.6.x. You can assume that all the projects within the Spring cloud 2021.0 release train are still supported as long as Spring Boot 2.7.x is still supported.
The following table is a list of Spring Cloud Release Trains, the supported Spring Boot versions, and the included projects. Each project has a link to the official support timelines on https://spring.io. The header row is the Release Train name. For Release Trains with CALVER, the codename is included in parenthesis. The first column is the project name with a link to the support page. This table may include Release Trains that are under current development. The Release Train for these are in italics. For convenience, Release Trains outside of the OSS support policy are marked with strikethrough (please see the project page for up-to-date information).
| 2023.0 (Leyton) | 2022.0 (Kilburn) | 2021.0 (Jubilee) | ||||||
|---|---|---|---|---|---|---|---|---|
| spring-boot | 3.2.x | 3.1.x/3.0.x | 2.7.x/2.6.x | 2.5.x/2.4.x | 2.3.x/2.2.x | 2.1.x | 2.0.x | 1.5.x |
| spring-cloud-bus | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.3.x |
| spring-cloud-circuitbreaker | 3.1.x | 3.0.x | 2.1.x | 2.0.x | 1.0.x | - | - | - |
| spring-cloud-cli | - | - | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.4.x |
| spring-cloud-cloudfoundry | - | - | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.1.x |
| spring-cloud-commons | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.3.x |
| spring-cloud-config | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.4.x |
| spring-cloud-consul | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.3.x |
| spring-cloud-contract | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.2.x |
| spring-cloud-function | 4.1.x | 4.0.x | 3.2.x | 3.1.x | 3.0.x | 2.0.x | 1.0.x | 1.0.x |
| spring-cloud-gateway | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.0.x |
| spring-cloud-kubernetes | 3.1.x | 3.0.x | 2.1.x | 2.0.x | 1.1.x | 1.0.x | - | - |
| spring-cloud-netflix | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.4.x |
| spring-cloud-openfeign | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | - | - |
| spring-cloud-security | - | - | - | - | 2.2.x | 2.1.x | 2.0.x | 1.2.x |
| spring-cloud-sleuth | - | - | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.3.x |
| spring-cloud-stream | 4.1.x | 4.0.x | 3.2.x | 3.1.x | Horsham.x | Fishtown.x | Elmhurst.x | Ditmars.x |
| spring-cloud-task | 3.1.x | 3.0.x | 2.4.x | 2.3.x | 2.2.x | 2.1.x | 2.0.x | 1.2.x |
| spring-cloud-vault | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.1.x |
| spring-cloud-zookeeper | 4.1.x | 4.0.x | 3.1.x | 3.0.x | 2.2.x | 2.1.x | 2.0.x | 1.2.x |
Two community-supported projects, Spring Cloud AWS and Spring Cloud GCP, were included in various release trains. These projects are not included in the table above, as they are not subject to the VMware Tanzu OSS support policy.
Based on their individual project support timelines, Hoxton, Greenwich, Finchley, Edgware, Dalston, Camden, Brixton, and Angel are all EOL.
In early 2020, the release train versioning scheme changed. We now follow Calendar Versioning or calver for short. We follow the YYYY.MINOR.MICRO scheme, where MINOR is an incrementing number that starts at zero each year. The MICRO segment corresponds to suffixes previously used: .0 is analogous to .RELEASE and .2 is analogous to .SR2. Pre-release suffixes also change from using a . to a - for the separator, for example 2020.0.0-M1 and 2020.0.0-RC2. We will also stop prefixing snapshots with BUILD- -- for example, 2020.0.0-SNAPSHOT. A Release Train generation is defined by the first two parts of the version, so 2020.0 (codename Ilford) is the Release Train generation, and 2020.0.0 is the first release. In other words, the first two parts of the version are not MAJOR.MINOR.
The previous scheme was based on London Tube Station names. These will be continued to be used for code names, but these names will no longer be used in versions published to Maven repositories.
Spring Cloud provides managed dependencies for some third-party libraries. These libraries are typically upgraded at the patch level for any given Spring Cloud release. Since we typically do not upgrade the minor or major versions of third-party libraries with our patch releases, you should check the EOL policies of projects that you depend on, since you may find that you use a supported version of Spring Cloud against an unsupported third-party library.
Commercial support for Spring Cloud is available from VMware. Please see https://tanzu.vmware.com/spring-runtime for details.