Why are Node.js 20 and Node.js 25 missing?
Today is June 12, 2026, and both dates have already passed: Node.js 20 ended on April 30, 2026, and Node.js 25 ended on June 1, 2026. This page only keeps future timers.
End-of-life dates tend to sit in release notes until they suddenly become a production upgrade. This calendar is for the supported runtime lines that still have future deadlines after June 2026.
The dates here are fixed vendor support dates, not recurring rules. Node.js 20 and Node.js 25 are left out because their EOL dates have already passed. Each remaining item counts down to the end of the listed support day in UTC.
Use this as a planning calendar for dependency owners, platform teams, and maintainers who need enough lead time for test upgrades, container rebuilds, and rollout windows. Vendor schedules can still change, so evergreen refreshes should re-check the official tables.

Next up
.NET 8 is listed by Microsoft as an LTS release with end of support on November 10, 2026.
.NET 9 is listed by Microsoft as an STS release with end of support on November 10, 2026.
PHP 8.2 is in security-fixes-only support until December 31, 2026.
The Node.js release schedule lists Node.js 22, codename Jod, with end of life on April 30, 2027.
PHP 8.3 is in security support until December 31, 2027.
The Node.js release schedule lists Node.js 24, codename Krypton, with end of life on April 30, 2028.
.NET 10 is listed by Microsoft as an LTS release with end of support on November 14, 2028.
PHP 8.4 is in active support until the end of 2026 and security support until December 31, 2028.
The Node.js release schedule lists Node.js 26 with end of life on April 30, 2029.
PHP 8.5 is in security support until December 31, 2029.
Today is June 12, 2026, and both dates have already passed: Node.js 20 ended on April 30, 2026, and Node.js 25 ended on June 1, 2026. This page only keeps future timers.
No. Each timer is a concrete vendor support date. The page should be refreshed when the official support tables change, not generated from a recurrence rule.
After end of support, vendors stop publishing normal fixes for that release line. Teams usually plan upgrades earlier so test, deployment, and rollback windows are not squeezed into the final week.
These support tables are global release schedules rather than local civil deadlines. The timers count down to the end of the listed calendar day in UTC.