Every date has a source.
Where the calendar’s dates come from, which ones are checked against the vendor’s own data, how changes are kept, and how to tell us one is wrong.
Updated Dates last checked
Where dates come from
endoflife.date first, then the vendor.
Dates and version facts come from endoflife.date, a community-maintained dataset whose data is MIT licensed. The site reloads it every time it is built.
endoflife.date is a copy, and copies drift. Where a vendor publishes its own lifecycle data as a file, the build checks against it. When the two disagree, the vendor’s date is shown, the page names the vendor, and endoflife.date’s date is kept on record.
| Product | Checked against | Why it matters |
|---|---|---|
| Python | python.org release-cycle.json | Future dates are given as a month. We print the month, not a guessed day. |
| Ubuntu | distro-info-data | Ubuntu’s own release table, the one ubuntu-distro-info reads. Interim releases often differ from other trackers by days. |
| PostgreSQL | postgresql.org versions.json | Minor releases are dated by the day they ship, not the earlier day they were tagged. A new major version shows from release day. |
| PHP | php.net branches and releases | A new branch and a new security release show from the day php.net publishes them. End dates are not checked against it yet. |
More vendors get added as they are wired up. Node.js, Kubernetes, .NET, Debian, Alpine and Red Hat all publish machine-readable schedules too.
Cloud platforms use their own words. AWS Lambda “deprecates” a runtime on the day it stops patching it, then blocks creating and updating functions months later. Where a page covers a platform, it quotes the platform’s own table and its own terms rather than forcing them into one “end of life” date.
Changes
When a date moves, we keep both.
Since , a daily job stores every date endoflife.date publishes, for all of its products, and records each one that changes with the day it changed. Earlier changes are recovered from endoflife.date’s public edit history, back to 2021.
That history shows, for example, that endoflife.date listed Python 3.10’s end of life as 31 October 2026 from March 2024 until 2 October 2026. python.org ended it on 1 October, the day 3.10.22, its final release, shipped.
The writing
Consequences are written by a person.
The sentence under each release says what actually stops and what starts breaking. Each one is written by hand, and a release only gets a page of its own when someone has written one. No page here is generated from the data.
Some things are left out on purpose. There are no risk scores, because a number nobody can check is not information. There are no counts of “unpatched vulnerabilities”: vulnerability databases match version lines too loosely, and they often stop assessing a branch once it is out of support, so any such count would look precise and be wrong.
Written text is free to reuse under CC BY 4.0. endoflife.date’s data stays under its MIT licence.
Product logos come from Simple Icons, released under CC0, except the PHP logo, which is by Colin Viebrock under CC BY-SA 4.0. Each logo is a trademark of its owner and appears only to name the product. None of them implies an endorsement.
Independence
Nothing here is for sale.
Corrections