Node.js 22 reaches end of life
- Announced
- 24 Apr 2024
- Effective
- 30 Apr 2027 · in 218 days
- Source
- the vendor’s own page · last checked 18 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 24, the active LTS line, or Node.js 26 once it enters LTS on 28 October 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.
What the vendor said
Node.js 22 (Jod) shipped on 2024-04-24 with its support schedule published alongside it: maintenance from 2025-10-21, end of life on 2027-04-30. After that date the line receives no security patches, and hosting platforms drop the runtime.
Suricate tells you this before it lands, by email, only when your own repository is affected.
Watch my repositoryOne 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.