ShutdownRadar
Support lifecycle

kirby end of life dates — full support timeline

Next end of life: 2027-06-23·cycle 4·327 days away

19 of 21 tracked kirby releases have already reached end of life. The dates below are published support dates, not estimates.

Version support timeline

ReleaseReleasedEnd of lifeLatestStatus
52025-06-24not announced5.5.3supported
3.102023-12-192025-11-273.10.1.2ended
42023-11-282027-06-234.9.5supported
3.92023-01-172025-11-273.9.8.3ended
3.82022-10-062025-01-163.8.4.4ended
3.72022-06-272024-10-053.7.5.5ended
3.62021-11-162024-06-263.6.6.6ended
3.52020-12-152023-11-153.5.8.4ended
3.42020-07-072021-11-163.4.5ended
3.32019-11-052021-11-163.3.6ended
3.22019-06-252021-11-163.2.5ended
3.12019-03-192021-11-163.1.4ended
3.02019-01-152021-11-163.0.3ended
2.52017-06-202021-01-012.5.14ended
2.42016-11-032021-01-012.4.2ended
2.32016-05-172021-01-012.3.3ended
2.22015-11-172021-01-012.2.3ended
2.12015-05-192021-01-012.1.1ended
2.02014-10-072021-01-012.0.6ended
1.12012-06-192016-02-011.1.2ended
1.02012-01-092016-02-011.0.9ended

Who is affected

Anyone running an unsupported kirby release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.

Source

These dates are maintained by endoflife.date/kirby, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.

Get told before the next kirby deadline

You are reading this because a kirby release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every kirby and related deadline as it is announced, with exact dates and primary sources.

Watch kirby deadlines Team monitoring pilot →

Takes about twenty seconds. No account, no card, no tracking.

All upcoming deadlines · Full archive