Node.js 20 reaches end of life

Announced: 22 Oct 2024
Effective: passed 30 Apr 2026
Source: the vendor’s own page · last checked 7 Sept 2026

What breaks

The runtime stops receiving security patches on that date. Hosts and CI images drop the line in the months around it, so a deploy or a base image is usually what fails first, not the running process.

What to do

Move to Node.js 22 or 24. Both were active LTS lines as of 7 Sept 2026. Change the version where it is pinned: .nvmrc, the engines field, a Dockerfile base image, a CI workflow, the runtime setting on your host.

Advice confirmed 7 Sept 2026

What the vendor said

Node.js 20 (Iron) entered maintenance on 22 October 2024 and reaches end of life on 30 April 2026. After that date it receives no security patches, and hosting platforms drop the runtime.

You found this one the hard way. Suricate emails you about the next one — only when your own repository is affected, with the date it lands and what to do.

Watch my repository

One repository, free. We read your manifests and your configuration files. Never your code.

Watching more than one repository?

The team plan is not open yet.

No account, and no repository read. We store the address and the date, and nothing else — see privacy.