Node.js End-of-Life Tracker

Even versions only — the odd ones never get LTS

Node.js only promotes even-numbered releases (18, 20, 22, 24...) to Long-Term Support; odd-numbered releases (19, 21, 23...) stay in the short-lived "Current" phase for about six months and go straight to end-of-life without ever becoming LTS — they were never intended for production use. This table only tracks the LTS lines.

Why teams get caught out by this schedule

An LTS line gets roughly 30 months of total support from initial release, split between an active-development phase and a security-only maintenance phase — but because that clock starts at the original release date, not whenever a given team happens to adopt it, a version can feel "recent" to a team while already being much closer to its EOL date than they realize.