EOL.WikiEOL.Wiki
← ← Back to all products

Spring Cloud

Active
OtherLatest Version: 2025.1.2Latest Release: Jun 11, 2026

Support summary

Spring Cloud 2025.0 reaches EOL in 6 days. Start upgrade planning and compatibility testing now.

What do EOL and support statuses mean?

Next EOL

Jun 30, 2026

Spring Cloud 2025.0 · 6 days left

Supported cycles

2

0 lts

Versions

7

Latest Version

2025.1.2

Active Support

2

EOL

5

Lifecycle Timeline

Today
2025.1
2025.1
2025.0
2025.0
2024.0
2024.0
2023.0
2023.0
2022.0
2022.0
2021.0
2021.0
2020.0
2020.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2025.1Nov 24, 2025YesDec 31, 20262025.1.2No
Active
2025.0May 29, 2025YesJun 30, 20262025.0.3No
Active
2024.0Dec 3, 2024NoDec 31, 20252024.0.3No
EOL
2023.0Dec 6, 2023NoJun 30, 20252023.0.6No
EOL
2022.0Dec 16, 2022NoJun 30, 20242022.0.5No
EOL
2021.0Dec 1, 2021NoJun 30, 20232021.0.9No
EOL
2020.0Dec 22, 2020NoMay 31, 20222020.0.6No
EOL

Data sources

Frequently Asked Questions

Which versions of Spring Cloud have reached end of life?
The following Spring Cloud versions have reached end of life and no longer receive security updates: 2024.0, 2023.0, 2022.0, 2021.0, 2020.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Spring Cloud 2024.0?
Spring Cloud 2024.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Spring Cloud?
The latest version of Spring Cloud is 2025.1.2, released in the 2025.1 release cycle.
How many versions of Spring Cloud are currently supported?
Spring Cloud currently has 2 actively supported version(s): 2025.1, 2025.0.
When does Spring Cloud 2025.1 reach end of life?
Spring Cloud 2025.1 is scheduled to reach end of life on Dec 31, 2026.
What should I do when Spring Cloud reaches end of life?
When a Spring Cloud version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.