pigeonhole end of life dates — full support timeline
4 of 6 tracked pigeonhole releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 2.4 | 2025-01-24 | not announced | 2.4.4 | supported |
| 0.5 | 2017-12-24 | not announced | 0.5.21.1 | supported |
| 0.4 | 2013-05-09 | 2025-01-24 | 0.4.24.2 | ended |
| 0.3 | 2012-02-16 | 2017-12-24 | 0.3.6 | ended |
| 0.2 | 2010-09-10 | 2013-05-09 | 0.2.5 | ended |
| 0.1 | 2008-10-23 | 2012-02-16 | 0.1.4 | ended |
Who is affected
Anyone running an unsupported pigeonhole 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/pigeonhole, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next pigeonhole deadline
You are reading this because a pigeonhole 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 pigeonhole and related deadline as it is announced, with exact dates and primary sources.
Watch pigeonhole deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.