-
Notifications
You must be signed in to change notification settings - Fork 186
Supported Versions
Spring Vault 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 Vault releases are publicly available from Maven Central and https://repo.spring.io. We do not have a private repository reserved only for paying customers.
Spring Vault 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 Vault releases are usually marked end of life 27 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.
The list of all released and currently supported versions can be found here.
As much as possible, Spring Vault 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.
Commercial support for Spring Vault is available from VMware. Please see https://tanzu.vmware.com/spring-runtime for details.
-
Spring Vault 3.1.x: JDK 17-21
-
Spring Vault 3.0.x: JDK 17-19
-
Spring Vault 2.4.x: JDK 8-19
-
Spring Vault 2.3.x: JDK 8-19
-
Spring Vault 2.2.x: JDK 8-18
-
Spring Vault 2.1.x: JDK 8-12
-
Spring Vault 1.1.x: JDK 6-8
We fully test and support Spring on Long-Term Support (LTS) releases of the JDK, i.e. currently JDK 8 and 11 (both with a lifetime until 2023). Additionally, there is support for intermediate releases such as JDK 9/10/12/13 or the upcoming JDK 14 on a best-effort basis, meaning that we accept bug reports and will try to address them as far as technically possible but won’t provide any service level guarantees.