On this page
This software end-of-life tracker lists the dates that can break or expose a startup's stack. It covers runtimes, databases, operating systems, cloud runtimes, frameworks, AI model retirements, AI regulation and a few developer-platform changes. Every date comes from the vendor's own page, and every row shows when we last checked it. When a vendor gives only a month, we say so instead of guessing a day.
How to read this software end-of-life tracker
Each row has one of three statuses. Upcoming means the date is still ahead. In effect means the date has passed but a reduced state continues, such as a deprecated runtime that still runs, paid extended support, or a rule that now applies. Passed means support has ended and no more fixes ship. We re-check every entry at least every 90 days, and sooner when a vendor changes a date.
If a row below matches something you run, put the upgrade on your roadmap a quarter before the date. Most of these moves are routine when planned and painful when forced. The bigger changes get their own alerts and updates, linked in the sections below.
Runtimes and languages
Node.js end of life dates come from the project's release schedule; the other rows link each language's own policy page.
| Item | What happens | Date | Status | Source | Last verified |
|---|---|---|---|---|---|
| Node.js 20 | End of life | April 30, 2026 | Passed | Node.js release schedule | 2026-10-11 |
| Node.js 24 | Moves from Active LTS to Maintenance LTS (end of life April 30, 2028) | October 20, 2026 | Upcoming | Node.js release schedule | 2026-10-11 |
| Node.js 22 | End of life (in Maintenance LTS now) | April 30, 2027 | Upcoming | Node.js release schedule | 2026-10-11 |
| Python 3.9 | End of life | October 31, 2025 | Passed | Python Developer's Guide: versions | 2026-10-11 |
| Python 3.10 | End of life; 3.10.22 was the final security release | October 1, 2026 | Passed | PEP 619 | 2026-10-11 |
| .NET 8 (LTS) and .NET 9 (STS) | End of support for both | November 10, 2026 | Upcoming | .NET support policy | 2026-10-11 |
| PHP 8.1 | End of life (last release 8.1.34) | December 31, 2025 | Passed | PHP unsupported branches | 2026-10-11 |
| PHP 8.2 | End of security support | December 31, 2026 | Upcoming | PHP supported versions | 2026-10-11 |
| Ruby 3.2 | End of life | April 1, 2026 | Passed | Ruby maintenance branches | 2026-10-11 |
Databases
PostgreSQL 14 end of life comes first among the upcoming dates here: the final community release is due November 12, 2026.
| Item | What happens | Date | Status | Source | Last verified |
|---|---|---|---|---|---|
| PostgreSQL 13 | Final community release | November 13, 2025 | Passed | PostgreSQL versioning policy | 2026-10-11 |
| PostgreSQL 14 | Final community release | November 12, 2026 | Upcoming | PostgreSQL versioning policy | 2026-10-11 |
| MySQL 8.0 | End of life with version 8.0.46 | April 2026 (month only) | Passed | MySQL 8.0 release notes | 2026-10-11 |
| Amazon RDS for PostgreSQL 13 | End of standard support; RDS Extended Support year-1 pricing from March 1, 2026 | February 28, 2026 | In effect | RDS for PostgreSQL release calendar | 2026-10-11 |
| Amazon RDS for MySQL 8.0 | End of standard support; RDS Extended Support year-1 pricing from August 1, 2026 | July 31, 2026 | In effect | RDS for MySQL versions | 2026-10-11 |
| Amazon RDS for PostgreSQL 14 | End of standard support | February 28, 2027 | Upcoming | RDS for PostgreSQL release calendar | 2026-10-11 |
| MongoDB 6.0 | End of life | July 31, 2025 | Passed | MongoDB software lifecycle schedules | 2026-10-11 |
| MongoDB 7.0 | End of life | August 31, 2027 | Upcoming | MongoDB software lifecycle schedules | 2026-10-11 |
Operating systems
| Item | What happens | Date | Status | Source | Last verified |
|---|---|---|---|---|---|
| Ubuntu 20.04 LTS | End of standard support; covered only by Ubuntu Pro after | May 2025 (month only) | Passed | Ubuntu release cycle | 2026-10-11 |
| Amazon Linux 2 | End of support | June 30, 2026 | Passed | Amazon Linux 2 FAQs | 2026-10-11 |
| Debian 11 "bullseye" | End of Long Term Support | August 31, 2026 | Passed | Debian 11 release page | 2026-10-11 |
| Windows Server 2016 | End of extended support | January 12, 2027 | Upcoming | Microsoft lifecycle: Windows Server 2016 | 2026-10-11 |
| Ubuntu 22.04 LTS | End of standard security maintenance (Expanded Security Maintenance runs to May 2032) | May 2027 (month only) | Upcoming | Ubuntu release cycle | 2026-10-11 |
Cloud runtimes and Kubernetes
Each AWS Lambda runtime deprecation runs in three steps: security patches stop, then AWS blocks creating new functions, then it blocks updating existing ones.
| Item | What happens | Date | Status | Source | Last verified |
|---|---|---|---|---|---|
AWS Lambda python3.9 | Deprecated: no more security patches; create blocked July 29, 2027, update blocked August 31, 2027 | December 15, 2025 | In effect | Lambda runtimes | 2026-10-11 |
AWS Lambda nodejs20.x | Deprecated: no more security patches; create blocked July 29, 2027, update blocked August 31, 2027 | April 30, 2026 | In effect | Lambda runtimes | 2026-10-11 |
AWS Lambda python3.10 | Deprecation: security patches stop; create blocked July 29, 2027, update blocked August 31, 2027 | October 31, 2026 | Upcoming | Lambda runtimes | 2026-10-11 |
AWS Lambda dotnet8 | Deprecation: security patches stop; create blocked July 29, 2027, update blocked August 31, 2027 | November 10, 2026 | Upcoming | Lambda runtimes | 2026-10-11 |
AWS Lambda nodejs22.x | Deprecation: security patches stop; create blocked June 1, 2027, update blocked July 1, 2027 | April 30, 2027 | Upcoming | Lambda runtimes | 2026-10-11 |
Google Cloud Run functions python310 | Deprecation period started; decommission April 4, 2027 | October 4, 2026 | In effect | Cloud Run functions runtime support | 2026-10-11 |
Google Cloud Run functions nodejs20 | Decommission: no new or updated deployments; deprecated since April 30, 2026 | October 30, 2026 | Upcoming | Cloud Run functions runtime support | 2026-10-11 |
| Azure Functions .NET in-process model | End of support; move to the isolated worker model | November 10, 2026 | Upcoming | Azure Functions supported languages | 2026-10-11 |
| Kubernetes 1.33 | End of life | June 28, 2026 | Passed | Kubernetes releases | 2026-10-11 |
| Kubernetes 1.34 | End of life | October 27, 2026 | Upcoming | Kubernetes releases | 2026-10-11 |
| Kubernetes 1.35 | End of life | February 28, 2027 | Upcoming | Kubernetes releases | 2026-10-11 |
The Kubernetes rows are the upstream project's dates. If you use a managed Kubernetes service, also check your provider's own support calendar for the version you run.
Frameworks
| Item | What happens | Date | Status | Source | Last verified |
|---|---|---|---|---|---|
| Django 4.2 LTS | End of extended support | April 7, 2026 | Passed | Django supported versions | 2026-10-11 |
| Ruby on Rails 8.1 | End of bug fixes; security fixes continue to October 10, 2027 | October 10, 2026 | In effect | Rails maintenance policy | 2026-10-11 |
| Ruby on Rails 8.0 | End of security fixes | November 7, 2026 | Upcoming | Rails maintenance policy | 2026-10-11 |
| Angular v20 | End of long-term support | November 28, 2026 | Upcoming | Angular releases | 2026-10-11 |
| Django 5.2 LTS | End of extended support | April 2028 (month only) | Upcoming | Django supported versions | 2026-10-11 |
Next.js does not publish end dates per version. Its support policy lists 16.x as Active LTS, 15.x as Maintenance LTS, and 14.x and older as unsupported. If you are on Next.js 14 or older, you are already outside the support window.
AI model retirements
These AI model deprecation dates come from each provider's own deprecations page.
| Item | What happens | Date | Status | Source | Last verified |
|---|---|---|---|---|---|
Google gemini-2.0-flash and gemini-2.0-flash-lite | Shutdown | June 1, 2026 | Passed | Gemini API deprecations | 2026-10-11 |
Anthropic claude-sonnet-4-20250514 and claude-opus-4-20250514 | Retired | June 15, 2026 | Passed | Claude model deprecations | 2026-10-11 |
Anthropic claude-opus-4-1-20250805 | Retired | August 5, 2026 | Passed | Claude model deprecations | 2026-10-11 |
OpenAI legacy GPT snapshots: gpt-3.5-turbo, gpt-4, gpt-4-turbo, gpt-4.1-nano, gpt-4o-2024-05-13, o1, o3-mini, o4-mini, gpt-image-1 | Shutdown | October 23, 2026 | Upcoming | OpenAI deprecations | 2026-10-11 |
Google gemini-2.5-flash-preview-tts and gemini-2.5-pro-preview-tts | Earliest possible shutdown | November 17, 2026 | Upcoming | Gemini API deprecations | 2026-10-11 |
OpenAI v1/prompts, reusable prompts, Agent Builder and Evals | Shutdown | November 30, 2026 | Upcoming | OpenAI deprecations | 2026-10-11 |
Anthropic claude-sonnet-4-5-20250929 | Retirement; replacement claude-sonnet-5-5 | November 30, 2026 | Upcoming | Claude model deprecations | 2026-10-11 |
OpenAI gpt-image-1-mini, gpt-image-1.5, chatgpt-image-latest | Shutdown | December 1, 2026 | Upcoming | OpenAI deprecations | 2026-10-11 |
| OpenAI first GPT-5, GPT-5 mini, GPT-5 nano, GPT-5 pro, o3 and o3-pro snapshots | Shutdown | December 11, 2026 | Upcoming | OpenAI deprecations | 2026-10-11 |
OpenAI tts-1, tts-1-hd, gpt-4o-mini-tts snapshots | Shutdown | January 6, 2027 | Upcoming | OpenAI deprecations | 2026-10-11 |
| OpenAI legacy audio, realtime and transcription models | Shutdown | January 20, 2027 | Upcoming | OpenAI deprecations | 2026-10-11 |
OpenAI whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe, gpt-4o-transcribe-diarize | Shutdown | February 26, 2027 | Upcoming | OpenAI deprecations | 2026-10-11 |
Google lists the earliest possible shutdown dates and confirms the exact date with notice. Anthropic's dates apply to its own platforms; Amazon Bedrock and Google Cloud set their own schedules. For the OpenAI dates and what to do about them, read our OpenAI API deprecations alert.
AI regulation
| Item | What happens | Date | Status | Source | Last verified |
|---|---|---|---|---|---|
| EU AI Act, general application | Act applies; AI Office and national enforcement start; Article 50 transparency duties apply | August 2, 2026 | In effect | Commission: AI Act enforcement | 2026-10-11 |
| EU AI Act, Article 50(2) for older systems; new bans | Machine-readable marking deadline for generative systems on the market before August 2, 2026; ban on non-consensual intimate imagery and child sexual abuse material generation applies | December 2, 2026 | Upcoming | AI Act Service Desk: Article 113 | 2026-10-11 |
| EU AI Act, Annex III high-risk uses | High-risk obligations apply (moved by the AI Omnibus) | December 2, 2027 | Upcoming | Commission: AI Omnibus | 2026-10-11 |
| EU AI Act, Annex I products | High-risk obligations apply for AI in regulated products | August 2, 2028 | Upcoming | Commission: AI Omnibus | 2026-10-11 |
What these dates mean for a startup that builds on model APIs is in our EU AI Act enforcement update.
Developer platform changes
| Item | What happens | Date | Status | Source | Last verified |
|---|---|---|---|---|---|
| npm classic tokens | All classic tokens revoked; npm login issues two-hour session tokens | December 9, 2025 | Passed | GitHub changelog | 2026-10-11 |
| npm v12 | Dependency install scripts, git and remote URL dependencies off by default | July 8, 2026 | In effect | GitHub changelog | 2026-10-11 |
Supabase legacy anon and service_role keys | Deprecated in favour of publishable and secret keys | By the end of 2026 (no exact day) | Upcoming | Supabase API keys | 2026-10-11 |
| npm granular tokens that bypass 2FA | Direct publishing removed; publish through trusted or staged publishing | January 2027 (target) | Upcoming | GitHub changelog | 2026-10-11 |
The npm changes followed a year of supply chain attacks; our npm supply chain attacks update covers what happened and what to change.
How we help with software end-of-life upgrades
Through our DevOps consulting services, we plan and run these upgrades with startup teams. When an end date forces a bigger move, such as a new runtime or another cloud provider, our cloud migration consulting services cover the plan and the work. If an investor review is coming, our technical due diligence services look at the versions you run as part of the review. Keeping versions current is part of technical debt management, which our guide covers in more depth.
Frequently asked questions
What is the difference between end of life, end of support and deprecation?
End of life or end of support means the vendor stops shipping fixes, including security fixes. Deprecation usually comes first: the item still works, but has an end date and should not go into new work. For cloud runtimes, deprecation can also mean patches stop while existing functions keep running. Wording varies by vendor, so check the source row.
What happens if we keep running software past its end-of-life date?
Usually nothing breaks on the day. The risk grows after it: new vulnerabilities stay unpatched, libraries drop support, and security reviews, enterprise customers and investors start to flag it. AI model retirements are different. After a shutdown date, API calls to that model fail.
Do AWS Lambda functions stop working on the deprecation date?
No. AWS says you can keep invoking functions on a deprecated runtime, but it no longer applies security patches and those functions lose technical support. Later, AWS blocks creating new functions and then blocks updating existing ones. Each Lambda row above lists those dates, and AWS says they are forecasts that can change.
Are AI model retirement dates the same on Amazon Bedrock, Google Cloud or Azure?
Not always. Anthropic says its dates apply to the Claude API, Claude Platform on AWS and Microsoft Foundry, while Amazon Bedrock and Google Cloud set their own retirement schedules. Check the deprecation page of the platform you actually call, not only the model maker's page.
How often is this tracker updated?
We re-check every entry at least every 90 days, and update a row when a vendor changes a date. Each row shows its last verified date, and a dated change note records every edit. When a date passes, the status changes, and the row stays for a while so you can see what recently ended.
Why do some rows show only a month?
Because the vendor publishes only a month. Ubuntu does this for standard security maintenance, and Oracle did it for MySQL 8.0. We show what the vendor publishes and do not invent a day. Plan as if support ends on the first day of that month, so the real date cannot surprise you.
How should a startup plan these upgrades?
Keep a one-page inventory of runtimes, database versions, base images, cloud runtimes and AI models per service. Compare it with this tracker once a quarter, and schedule each upgrade at least a quarter before its date, with a test pass and a rollback plan.
Sources and update history
- Node.js release schedule
- Python Developer's Guide: versions
- PEP 619
- .NET support policy
- PHP unsupported branches
- PHP supported versions
- Ruby maintenance branches
- PostgreSQL versioning policy
- MySQL 8.0 release notes
- RDS for PostgreSQL release calendar
- RDS for MySQL versions
- MongoDB software lifecycle schedules
- Ubuntu release cycle
- Amazon Linux 2 FAQs
- Debian 11 release page
- Microsoft lifecycle: Windows Server 2016
- Lambda runtimes
- Cloud Run functions runtime support
- Azure Functions supported languages
- Kubernetes releases
- Django supported versions
- Rails maintenance policy
- Angular releases
- Gemini API deprecations
- Claude model deprecations
- OpenAI deprecations
- Commission: AI Act enforcement
- AI Act Service Desk: Article 113
- Commission: AI Omnibus
- GitHub changelog
- GitHub changelog
- Supabase API keys
- GitHub changelog
- Next.js support policy
Update history
- First published with 58 entries in 8 sections, all checked on vendor pages.
