Check a site
Check a website Service status Outages Blog
Theme
All tools
Check a websiteBrowse all tools
A terminal window running node -v and showing v26.13.0, with an LTS badge labelled Lithium and a small release timeline

News

Node.js 26 is now LTS: what “Lithium” changes, and when Node.js 22 and 24 run out

Posted Jimel S.4 min read

Node.js 26 became the Active LTS line, codename Lithium, on 28 October 2026, with updates until the end of April 2029. Node.js 24 is now in maintenance, Node.js 22 reaches end of life on 30 April 2027, and Docker’s lts tag has already moved.

Illustration: UtiBox

On 28 October 2026 Node.js 26 was promoted to Long Term Support (LTS) under the codename Lithium. Version 26.13.0 marks the switch, and the release notes say the line “will continue to receive updates through to the end of April 2029.”

Most teams run only LTS versions in production. If you’re one of them, Node.js 26 is now the version to plan for.

Where each release line stands

From the Node.js Release Working Group’s schedule:

LineCodenameStatusEnd of life
26.xLithiumActive LTS since 28 Oct 2026, maintenance from 20 Oct 202730 Apr 2029
24.xKryptonMaintenance LTS since 20 Oct 202630 Apr 2028
22.xJodMaintenance LTS30 Apr 2027
27.xnone yetAlpha30 Apr 2030

In maintenance, a line gets critical bug fixes and security updates only. Node.js 20 reached end of life on 30 April 2026. If anything still runs it, move that first.

What’s in Node.js 26

Node.js 26.0.0 arrived on 5 May 2026 and spent six months as the “Current” release. The main changes:

  • Temporal is on by default. Temporal, a modern and more capable alternative to the old Date object, works without a flag.
  • V8 14.6, the JavaScript engine from Chromium 146. It adds Map.prototype.getOrInsert(), getOrInsertComputed() and Iterator.concat().
  • Undici 8.0, an update to the library behind Node’s built-in HTTP client.

Things that can break when you move from 22 or 24:

  • The old writeHeader() alias has been removed from the HTTP module. Use writeHead().
  • The legacy _stream_readable, _stream_writable, _stream_duplex, _stream_transform, _stream_passthrough and _stream_wrap modules have been removed. Old dependencies sometimes import these directly.
  • module.register() now prints a runtime deprecation warning, and the --experimental-transform-types flag has gone.
  • On Linux, the official binaries have been linked against libatomic since Node.js 25. The LTS release notes warn that you may need to install it separately, depending on your distribution. Minimal servers and slim container images are where this tends to show up.

Docker’s floating tags now mean Node.js 26

In the Docker official images, node:lts, node:latest and node:current, plus their -slim, -alpine and Debian variants, now point to Node.js 26.13.0. If a Dockerfile uses one of those tags, the next rebuild quietly moves you to a new major version.

Pin the major version and upgrade when you choose to:

FROM node:24-slim    # stay on 24 until your tests pass on 26
FROM node:26-slim    # then switch deliberately

A new yearly rhythm from Node.js 27

Node.js 26 is the last line released under the old model, with two major versions a year and only the even-numbered ones becoming LTS. From Node.js 27 there is one major version a year, and every line becomes LTS:

  • Alpha builds start in October. The first Node.js 27 alpha was published on 29 October 2026. Alphas can contain breaking changes and are meant for library authors and CI pipelines, not production.
  • Node.js 27.0.0 is due in April 2027, should enter LTS in October 2027 and reaches end of life on 30 April 2030.
  • Version numbers now follow the calendar year of the first Current release: 27 in 2027, 28 in 2028.

If you maintain a library, the project recommends adding the alpha releases to your CI as early as you can.

What to do

  1. Take stock. Run node -v on every server, and check your CI images and the runtime settings of any serverless functions.
  2. Patch first. Install the 11 November security release for your current line before planning anything bigger.
  3. On Node.js 22, plan the move now. It reaches end of life on 30 April 2027, less than six months away. Going straight to 26 gives you the longest runway.
  4. Upgrade on a branch. With nvm, for example, run nvm install 26, then your full test suite. Run your app with node --trace-deprecation to find out where warnings come from.
  5. Pin Docker tags to a major version, as shown above.
  6. Check after you deploy. Make sure the site answers normally with our HTTP Status Checker, and compare server response times before and after with the Response Time Test.

Check your site after the upgrade

Sources

Related

More from News

Most read

Latest

Most read

  1. 01November Patch Tuesday lands on the 10th: what October’s record release tells us19
  2. 02Introducing UtiBox: the Web’s Utility Box2
  3. 03Ivanti Connect Secure zero-days gave attackers root on VPN gateways1
  4. 04“Black October”: attackers raid secrets at cloud and AI developer platforms1

Embed this post

Paste this code into your page. It shows the post as a card that links back here. In WordPress you can also paste the post’s address on a line of its own.

Cookies on UtiBox

UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.