EOL.Wiki EOL.Wiki
← ← Back to all products

Halo

Active
CMS & Content Latest Version: v2.24.2 Latest Release: Apr 29, 2026

Halo is an open-source, modern blog and content management system (CMS) developed in China, built with Java/Spring Boot and featuring a powerful plugin and theme ecosystem.

Versions

10

Latest Version

v2.24.2

Active Support

3

EOL

7

Lifecycle Timeline

Today
2.24
2.24
2.23
2.23
2.22
2.22
2.21
2.21
2.20
2.20
2.19
2.19
2.17
2.17
2.11
2.11
2.0
2.0
1.5
1.5
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2.24Apr 16, 2026YesNov2.24.2No
Active
2.23Mar 13, 2026YesNov2.23.3No
Active
2.22Dec 24, 2025YesNov2.22.14No
Active
2.21Jun 15, 2025NoYesv2.21.10No
EOL
2.20Oct 14, 2024NoYesv2.20.21No
EOL
2.19Sep 2, 2024NoYesv2.19.3No
EOL
2.17Jul 2, 2024NoYesv2.17.2No
EOL
2.11Dec 1, 2023NoYesv2.11.3No
EOL
2.0Dec 1, 2022NoYesv2.0.3No
EOL
1.5Mar 22, 2022NoYesv1.5.6No
EOL

Frequently Asked Questions

Which versions of Halo have reached end of life?
The following Halo versions have reached end of life and no longer receive security updates: 2.21, 2.20, 2.19, 2.17, 2.11, 2.0, 1.5. It is recommended to upgrade to a supported version.
Is it safe to continue using Halo 2.21?
Halo 2.21 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 Halo?
The latest version of Halo is v2.24.2, released in the 2.24 release cycle.
How many versions of Halo are currently supported?
Halo currently has 3 actively supported version(s): 2.24, 2.23, 2.22.
When does Halo 2.24 reach end of life?
Halo 2.24 does not have a specific end-of-life date announced yet.
What should I do when Halo reaches end of life?
When a Halo 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.