Kirby End of Life Dates
Release, end of support and end of life dates for every tracked Kirby version, with current status.
All products · Vendor lifecycle page · Source entry
Status as of 2026-09-23 (UTC): 21 versions tracked; 1 supported, 0 security fixes only, 1 ending within 90 days, 19 end of life.
| Version | Status | Released | Support ends | Latest |
|---|---|---|---|---|
| 5 | Supported | 2025-06-24 | Not announced | 5.6.0 |
| 3.10 | End of life | 2023-12-19 | 2025-11-27 | 3.10.1.2 |
| 4 (A new era) | Ends within 90 days (66 days left) | 2023-11-28 | 2026-11-28 | 4.9.6 |
| 3.9 (Brookesia) | End of life | 2023-01-17 | 2025-11-27 | 3.9.8.3 |
| 3.8 (Rhampholeon) | End of life | 2022-10-06 | 2025-01-16 | 3.8.4.4 |
| 3.7 (Kinyongia) | End of life | 2022-06-27 | 2024-10-05 | 3.7.5.5 |
| 3.6 (Jungle Calumma) | End of life | 2021-11-16 | 2024-06-26 | 3.6.6.6 |
| 3.5 (Calumma) | End of life | 2020-12-15 | 2023-11-15 | 3.5.8.4 |
| 3.4 (Furcifer) | End of life | 2020-07-07 | 2021-11-16 | 3.4.5 |
| 3.3 (Trioceros) | End of life | 2019-11-05 | 2021-11-16 | 3.3.6 |
| 3.2 (Archaius) | End of life | 2019-06-25 | 2021-11-16 | 3.2.5 |
| 3.1 (Chamaeleo) | End of life | 2019-03-19 | 2021-11-16 | 3.1.4 |
| 3.0 | End of life | 2019-01-15 | 2021-11-16 | 3.0.3 |
| 2.5 | End of life | 2017-06-20 | 2021-01-01 | 2.5.14 |
| 2.4 | End of life | 2016-11-03 | 2021-01-01 | 2.4.2 |
| 2.3 | End of life | 2016-05-17 | 2021-01-01 | 2.3.3 |
| 2.2 | End of life | 2015-11-17 | 2021-01-01 | 2.2.3 |
| 2.1 | End of life | 2015-05-19 | 2021-01-01 | 2.1.1 |
| 2.0 | End of life | 2014-10-07 | 2021-01-01 | 2.0.6 |
| 1.1 | End of life | 2012-06-19 | 2016-02-01 | 1.1.2 |
| 1.0 | End of life | 2012-01-09 | 2016-02-01 | 1.0.9 |
Note: "Not announced" means the vendor has not published a date. "Ended (no date published)" means the source marks it ended without a date. Dates are compared as calendar days in UTC, so a date can flip up to a day earlier or later than your local calendar.
Data: endoflife.date (MIT license), snapshot 2026-09-23. Dates come from each vendor's published lifecycle. Always confirm with the vendor link before a purchase or migration decision.