cachet end of life dates — full support timeline
7 of 8 tracked cachet 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 | 2023-10-27 | not announced | 2.4.1 | supported |
| 2.3 | 2016-06-27 | 2023-10-27 | 2.3.18 | ended |
| 2.2 | 2016-03-27 | 2016-06-27 | 2.2.4 | ended |
| 2.1 | 2016-02-06 | 2016-03-27 | 2.1.2 | ended |
| 2.0 | 2015-11-22 | 2016-02-06 | 2.0.4 | ended |
| 1.2 | 2015-08-18 | 2015-11-22 | 1.2.1 | ended |
| 1.1 | 2015-08-01 | 2015-08-19 | 1.1.1 | ended |
| 1.0 | 2015-06-19 | 2015-08-01 | 1.0.0 | ended |
Who is affected
Anyone running an unsupported cachet 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/cachet, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next cachet deadline
You are reading this because a cachet 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 cachet and related deadline as it is announced, with exact dates and primary sources.
Watch cachet deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.