duckdb end of life dates — full support timeline
4 of 6 tracked duckdb 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.5 | 2026-03-09 | not announced | 1.5.5 | supported |
| 1.4 LTS | 2025-09-16 | 2026-09-16 | 1.4.5 | ends soon |
| 1.3 | 2025-05-21 | 2025-09-16 | 1.3.2 | ended |
| 1.2 | 2025-02-05 | 2025-05-21 | 1.2.2 | ended |
| 1.1 | 2024-09-09 | 2025-02-05 | 1.1.3 | ended |
| 1.0 | 2024-06-03 | 2024-09-09 | 1.0.0 | ended |
Who is affected
Anyone running an unsupported duckdb 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/duckdb, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next duckdb deadline
You are reading this because a duckdb 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 duckdb and related deadline as it is announced, with exact dates and primary sources.
Watch duckdb deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.