deno end of life dates — full support timeline
10 of 11 tracked deno 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.9 | 2026-06-25 | not announced | 2.9.4 | supported |
| 2.8 | 2026-05-22 | 2026-06-25 | 2.8.3 | ended |
| 2.7 | 2026-02-25 | 2026-05-22 | 2.7.14 | ended |
| 2.6 | 2025-12-10 | 2026-02-25 | 2.6.10 | ended |
| 2.5 LTS | 2025-09-10 | 2026-04-30 | 2.5.7 | ended |
| 2.4 | 2025-07-01 | 2025-09-10 | 2.4.5 | ended |
| 2.3 | 2025-04-30 | 2025-07-01 | 2.3.7 | ended |
| 2.2 LTS | 2025-02-18 | 2025-10-31 | 2.2.15 | ended |
| 2.1 LTS | 2024-11-21 | 2025-04-30 | 2.1.14 | ended |
| 2.0 | 2024-10-08 | 2024-11-21 | 2.0.6 | ended |
| 1 | 2020-04-13 | 2024-10-09 | 1.46.3 | ended |
Who is affected
Anyone running an unsupported deno 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/deno, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next deno deadline
You are reading this because a deno 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 deno and related deadline as it is announced, with exact dates and primary sources.
Watch deno deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.