Software lifecycle calendars are scattered across vendor documentation pages, GitHub wikis, and community-maintained spreadsheets. This article consolidates the most critical end-of-life dates for the runtimes and frameworks that power the majority of production applications — current as of May 2026.

Use this as a quarterly reference. Bookmark it. Share it with your team. The dates below represent the last day each version receives security patches. After that date, disclosed vulnerabilities go unpatched indefinitely.

Python

Python follows an annual release cycle with roughly five years of support per version. The PSF is disciplined about EOL enforcement — when a version drops off, it drops off completely.

VersionEOL DateStatus
Python 3.8Oct 2024End of Life
Python 3.9Oct 2025End of Life
Python 3.10Oct 2026EOL in 5 months
Python 3.11Oct 2027Active
Python 3.12Oct 2028Active
Python 3.13Oct 2029Active — Latest

Action required: Any production application running Python 3.9 or earlier is on EOL code. Python 3.10 teams should begin migration planning now — five months is not much runway for a runtime upgrade.

Node.js

Node.js releases even-numbered versions as LTS (Long Term Support). Odd-numbered versions are Current releases with shorter support windows. Only run LTS in production.

VersionEOL DateStatus
Node.js 16Sep 2023End of Life
Node.js 18Apr 2025End of Life
Node.js 20Apr 2026End of Life
Node.js 22Apr 2027Active LTS
Node.js 24Apr 2028Active — Latest LTS

Action required: Node.js 20 reached EOL in April 2026. If your applications are running Node 20 or earlier, upgrade to Node 22 or 24 immediately.

PHP

PHP has a two-year active support window followed by one year of security-only fixes. The community tends to be slow at migrating major versions, which creates persistent EOL exposure across the ecosystem.

VersionEOL DateStatus
PHP 7.4Nov 2022End of Life
PHP 8.0Nov 2023End of Life
PHP 8.1Dec 2025End of Life
PHP 8.2Dec 2026EOL in 7 months
PHP 8.3Dec 2027Active
PHP 8.4Dec 2028Active — Latest

Action required: Any PHP 8.1 or earlier application is running on EOL code. PHP 8.2 teams should plan migration to 8.3 or 8.4 before year-end.

Java LTS Releases

Java LTS release support varies significantly by vendor. Oracle's free support for OpenJDK LTS builds is limited; vendors like Amazon Corretto, Eclipse Temurin, and Microsoft OpenJDK offer longer free support windows. The dates below reflect Oracle OpenJDK community support.

VersionOracle EOLStatus
Java 8Mar 2025 (free)Commercial support only
Java 11Sep 2023 (free)EOL (Oracle free)
Java 17Sep 2026EOL in 4 months
Java 21Sep 2028Active LTS
Java 25Sep 2030Active — Latest LTS

Action required: Java 17 reaches Oracle EOL in September 2026. Teams running Java 11 or earlier on Oracle OpenJDK should migrate to Java 21 or switch to a vendor distribution with longer free support.

Ruby

VersionEOL DateStatus
Ruby 3.0Mar 2024End of Life
Ruby 3.1Mar 2025End of Life
Ruby 3.2Mar 2026End of Life
Ruby 3.3Mar 2027Active
Ruby 3.4Mar 2028Active — Latest

Databases

ProductEOL DateStatus
MySQL 5.7Oct 2023End of Life
MySQL 8.0Apr 2026End of Life
MySQL 8.4Apr 2032Active LTS
PostgreSQL 14Nov 2026EOL in 6 months
PostgreSQL 15Nov 2027Active
PostgreSQL 16Nov 2028Active
Redis 6.xMar 2024End of Life
Redis 7.0Jul 2025End of Life
Redis 7.2Jul 2026EOL in 2 months
Note on Redis: Redis 7.4+ moved to a dual-license model (RSALv2/SSPLv1). For teams requiring open-source licensing, Valkey is the community fork maintaining Apache 2.0 licensing with active development.

How to Use This Calendar

Cross-reference this list against your production stack. For every version that is EOL or approaching EOL within six months, create a tracked ticket with an owner and a deadline. Don't leave it as a note in a document — it needs to be in your issue tracker, assigned to a team, with a date.

For versions approaching EOL, check your vendor's migration guide before the deadline. Major version upgrades — Python 3.9 to 3.13, Node 20 to 24, PHP 8.1 to 8.4 — occasionally include breaking changes that require code updates. Six months is enough runway if you start now. Two months is not.

This calendar is updated quarterly. For real-time EOL status on any of these products, use the EOL Checker — it pulls live data from endoflife.date and surfaces CVE blind spot warnings for products past their support window.