EOL deadline radar
Paste a manifest or list your runtimes to get a dated end-of-life report, a share link and an upgrade memo. Dates from official release calendars, checked November 21, 2026.
Parsing happens in your browser. Nothing you paste is sent anywhere.
| Component | Version | Date | Status | Smallest supported jump | Found in |
|---|
How to use it
- Paste a manifest (package.json, requirements.txt, pyproject.toml, Gemfile, Dockerfile, .csproj) or type runtimes one per line, like node 20 or postgres 14. Or click the quick-add buttons.
- Read the report: every component found, the date its support ends, its status today and a supported upgrade target.
- Share the link, download the Markdown upgrade memo for your board or security review, or print it to PDF.
2025 to 2028 end-of-life calendar
Every date below comes from the project’s official release calendar or support policy, checked November 21, 2026. Month-only dates are shown as the project publishes them.
| Product | Version | Date | What ends | Status on November 21, 2026 |
|---|---|---|---|---|
| Ruby | 3.1 | Mar 26, 2025 | End of life | Past end of life |
| Ruby on Rails | 7.0 | Apr 1, 2025 | Security support ends | Past end of life |
| Django | 5.0 | Apr 2, 2025 | End of life | Past end of life |
| Node.js | 18 | Apr 30, 2025 | End of life | Past end of life |
| Angular | 17 | May 15, 2025 | End of life | Past end of life |
| Ruby on Rails | 7.1 | Oct 1, 2025 | Security support ends | Past end of life |
| Python | 3.9 | Oct 31, 2025 | End of life | Past end of life |
| Kubernetes | 1.31 | Nov 11, 2025 | End of life | Past end of life |
| PostgreSQL | 13 | Nov 13, 2025 | End of life | Past end of life |
| Angular | 18 | Nov 21, 2025 | End of life | Past end of life |
| Django | 5.1 | Dec 3, 2025 | End of life | Past end of life |
| PHP | 8.1 | Dec 31, 2025 | Security support ends | Past end of life |
| Kubernetes | 1.32 | Feb 28, 2026 | End of life | Past end of life |
| Ruby | 3.2 | Apr 1, 2026 | End of life | Past end of life |
| MySQL | 8.0 | April 2026 | End of support | Past end of life |
| Django | 4.2 | Apr 7, 2026 | End of life | Past end of life |
| Node.js | 20 | Apr 30, 2026 | End of life | Past end of life |
| Angular | 19 | May 19, 2026 | End of life | Past end of life |
| Node.js | 25 | Jun 1, 2026 | End of life | Past end of life |
| Kubernetes | 1.33 | Jun 28, 2026 | End of life | Past end of life |
| Ruby on Rails | 7.2 | Aug 9, 2026 | Security support ends | Past end of life |
| Oracle Java SE (Premier Support) | 17 | September 2026 | Oracle Premier Support ends | Past end of life |
| Oracle Java SE (Premier Support) | 26 | September 2026 | Oracle Premier Support ends | Past end of life |
| Eclipse Temurin | 26 | September 2026 | End of life | Past end of life |
| Python | 3.10 | Oct 1, 2026 | End of life | Past end of life |
| Kubernetes | 1.34 | Oct 27, 2026 | End of life | Past end of life |
| Ruby on Rails | 8.0 | Nov 7, 2026 | Security support ends | Past end of life |
| .NET | 8 | Nov 10, 2026 | End of support | Past end of life |
| .NET | 9 | Nov 10, 2026 | End of support | Past end of life |
| PostgreSQL | 14 | Nov 12, 2026 | End of life | Past end of life |
| Angular | 20 | Nov 28, 2026 | End of life | Within 6 months |
| PHP | 8.2 | Dec 31, 2026 | Security support ends | Within 6 months |
| Kubernetes | 1.35 | Feb 28, 2027 | End of life | Within 6 months |
| Oracle Java SE (Premier Support) | 27 | March 2027 | Oracle Premier Support ends | Within 6 months |
| Eclipse Temurin | 27 | March 2027 | End of support | Within 6 months |
| Ruby | 3.3 | Mar 31, 2027 | End of life | Within 6 months |
| Django | 6.0 | April 2027 | End of life | Within 6 months |
| Node.js | 22 | Apr 30, 2027 | End of life | Within 6 months |
| Angular | 21 | June 2027 | End of life | Within 12 months |
| Kubernetes | 1.36 | Jun 28, 2027 | End of life | Within 12 months |
| Python | 3.11 | October 2027 | End of life | Within 12 months |
| Eclipse Temurin | 11 | October 2027 | End of support | Within 12 months |
| Eclipse Temurin | 17 | October 2027 | End of support | Within 12 months |
| Ruby on Rails | 8.1 | Oct 10, 2027 | Security support ends | Within 12 months |
| Kubernetes | 1.37 | Oct 28, 2027 | End of life | Within 12 months |
| PostgreSQL | 15 | Nov 11, 2027 | End of life | Within 12 months |
| Django | 6.1 | December 2027 | End of life | Supported |
| PHP | 8.3 | Dec 31, 2027 | Security support ends | Supported |
| Django | 5.2 | April 2028 | End of life | Supported |
| Node.js | 24 | Apr 30, 2028 | End of life | Supported |
| Angular | 22 | June 2028 | End of life | Supported |
| Oracle Java SE (Premier Support) | 21 | September 2028 | Oracle Premier Support ends | Supported |
| Python | 3.12 | October 2028 | End of life | Supported |
| PostgreSQL | 16 | Nov 9, 2028 | End of life | Supported |
| .NET | 10 | Nov 14, 2028 | End of support | Supported |
| .NET | 11 | Nov 14, 2028 | End of support | Supported |
| PHP | 8.4 | Dec 31, 2028 | Security support ends | Supported |
Deadline guides
Step-by-step upgrade plans for the deadlines teams ask about most:
- Node.js 20 end of life
- Node.js 22 end of life
- Python 3.10 end of life
- Python 3.11 end of life
- .NET 8 and 9 end of support
- PostgreSQL 14 end of life
- PostgreSQL 15 end of life
- Rails 7.2 end of life
Why end-of-life dates matter
After a runtime or database reaches end of life, the project stops shipping security fixes for it. Vulnerability scanners keep finding issues that will never be patched upstream, customer security questionnaires ask about it, and SOC 2’s CC7.1 criterion asks companies to detect and manage vulnerabilities. Our SOC 2 guide for AI-assisted codebases covers that side. The migration runbooks cover bigger platform moves.
Who does the upgrades
Upgrades are engineering work: inventory, compatibility testing, canary rollouts and a rollback plan for every component. Ryz engineers do this on your team, reporting to your leads. Ryz engineers on your team start from $7,000 per month. Scope your team.
FAQ
Does the EOL deadline radar upload my manifest?
No. The parser runs entirely in your browser. Nothing you paste is sent to Ryz Labs or anyone else, and the share link only contains the component names and versions it found.
Where do the end-of-life dates come from?
From each project’s official release calendar or support policy: nodejs.org’s release schedule, devguide.python.org, Microsoft’s .NET support policy, postgresql.org’s versioning page, rubyonrails.org, djangoproject.com, php.net, angular.dev, vuejs.org, Oracle, Adoptium and kubernetes.io. Every date was checked on November 21, 2026.
What is the difference between end of life and end of support?
Projects use different words. Some stop all releases on the end-of-life date, others stop bug fixes first and security fixes later, and commercial vendors may sell longer support. The table shows exactly what ends on each date, as the project describes it.
Which files can I paste?
package.json (engines and major framework dependencies), requirements.txt, pyproject.toml, runtime.txt, a Gemfile, Dockerfile FROM lines, .csproj target frameworks, .nvmrc, or plain lines such as node 20, postgres 14 or .net 8.
Can I share the report with my CTO or auditor?
Yes. Copy the share link, download the Markdown memo, or print to PDF. The memo lists every component, its date, its status and an upgrade target, with links to the official sources. It is a planning document, not an audit opinion.
Want engineers to run the upgrades?
Ryz Labs engineers plan and ship runtime and database upgrades on your team, reporting to your leads, with canary rollouts and a rollback path for each one.
Start a conversation →