contour end of life dates — full support timeline
7 of 10 tracked contour 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 |
|---|---|---|---|---|
| 1.33 | 2025-09-08 | not announced | 1.33.5 | supported |
| 1.32 | 2025-05-15 | not announced | 1.32.5 | supported |
| 1.31 | 2025-05-06 | not announced | 1.31.6 | supported |
| 1.30 | 2024-07-31 | 2025-09-08 | 1.30.5 | ended |
| 1.29 | 2024-05-07 | 2025-05-15 | 1.29.5 | ended |
| 1.28 | 2024-02-12 | 2025-05-06 | 1.28.8 | ended |
| 1.27 | 2023-10-30 | 2024-07-31 | 1.27.4 | ended |
| 1.26 | 2023-08-29 | 2024-05-07 | 1.26.3 | ended |
| 1.25 | 2023-05-09 | 2024-02-12 | 1.25.3 | ended |
| 1.24 | 2023-01-31 | 2023-10-30 | 1.24.6 | ended |
Who is affected
Anyone running an unsupported contour 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/contour, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next contour deadline
You are reading this because a contour 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 contour and related deadline as it is announced, with exact dates and primary sources.
Watch contour deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.