EOL.WikiEOL.Wiki
← ← Back to all products

HaloEnd of Life (EOL) Dates & Support Status

Active
CMS & ContentLatest Version: v2.26.0Latest Release: Aug 14, 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.

Support summary

Halo currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

4

0 lts

Versions

11

Latest Version

v2.26.0

Active Support

4

EOL

7

Lifecycle Timeline

Dec 1, 2022As of Sep 27, 2026
2.26Active · Date not announced
2.24Active · Date not announced
2.23Active · Date not announced
2.22Active · Date not announced
2.21EOL · Ended; date not announced
2.20EOL · Ended; date not announced
2.19EOL · Ended; date not announced
2.17EOL · Ended; date not announced
2.11EOL · Ended; date not announced
2.0EOL · Ended; date not announced
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2.26Aug 14, 2026MaintainedDate not announcedv2.26.0No
Active
2.24Apr 16, 2026MaintainedDate not announcedv2.24.2No
Active
2.23Mar 13, 2026MaintainedDate not announcedv2.23.3No
Active
2.22Dec 24, 2025MaintainedDate not announcedv2.22.14No
Active
2.21Jun 15, 2025EndedEnded; date not announcedv2.21.10No
EOL
2.20Oct 14, 2024EndedEnded; date not announcedv2.20.21No
EOL
2.19Sep 2, 2024EndedEnded; date not announcedv2.19.3No
EOL
2.17Jul 2, 2024EndedEnded; date not announcedv2.17.2No
EOL
2.11Dec 1, 2023EndedEnded; date not announcedv2.11.3No
EOL
2.0Dec 1, 2022EndedEnded; date not announcedv2.0.3No
EOL
1.5Mar 22, 2022EndedEnded; date not announcedv1.5.6No
EOL

Data sources

Last verified

Aug 21, 2026

Community-maintained lifecycle data. Verify against official release notes before production migration.

Embed this badge

Halo end-of-life support status badge

Show Halo's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![Halo end-of-life status](https://eol.wiki/badge/halo.svg)](https://eol.wiki/halo/)

HTML

<a href="https://eol.wiki/halo/"><img src="https://eol.wiki/badge/halo.svg" alt="Halo end-of-life status" height="20"></a>
All badges & lifecycle API →

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.26.0, released in the 2.26 release cycle.
How many versions of Halo are currently supported?
Halo currently has 4 actively supported version(s): 2.26, 2.24, 2.23, 2.22.
When does Halo 2.26 reach end of life?
Halo 2.26 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.