# Node.js 26 becomes Active LTS through April 2029 — check automatic runtime upgrades Node.js 26.13.0 entered Active LTS on October 28 with support through April 2029. The promotion adds no runtime features, but moving from Node 22 or 24 can affect native addons, Linux libatomic dependencies and unpinned CI/container builds. Node 26 is now production LTS. Teams using floating LTS selectors should test which major their CI, containers and native modules actually run. - Status: Active - Published: 2026-10-29T18:44:44+13:00 - Updated: 2026-10-29T18:44:44+13:00 - Categories: Web Development, JavaScript, Developer Tools - Tags: compatibility, JavaScript, migration, Node.js - Canonical HTML: https://beyondthe.news/dossiers/nodejs-26-lithium-lts-october-2026-libatomic-runtime-migration ## What changed On October 28, 2026, the Node.js project published v26.13.0 and moved its 26.x line into Active Long Term Support under the codename Lithium, with updates scheduled until April 30, 2029. The release explicitly says it contains no code changes beyond LTS metadata compared with the October 21 security-patched v26.12.1. Node.js 24 remains a supported LTS line through April 2028 and Node.js 22 through April 2027. Official Linux binaries since Node 25 are linked against libatomic, which may need installation on some distributions. The promotion matters for dependency support policies and environments configured to follow a moving LTS major rather than a pinned version. ## Why it matters For production JavaScript services, LTS status is often the decision boundary for runtime upgrades. A CI job or container based on an unpinned LTS selector can begin using a new major without an application commit; native modules, deployment images and integration tests may behave differently. The security fixes shipped October 21 are already documented separately in BTN dossier #522 and should not be confused with new security fixes in 26.13.0. Teams can stay on supported Node 24 or 22 while they validate 26. The operational change is a support and compatibility transition, not a new JavaScript capability introduced on October 28. ## The new LTS line is a support transition, not another feature release The upstream signed v26.13.0 release marks Node.js 26 as Active LTS and explicitly reports no further changes from v26.12.1 beyond metadata such as process.release. Its official lifecycle ends April 30, 2029. Treat the October 21 security release and October 28 LTS promotion as separate events. ## Unpinned LTS references can change your build runtime Check GitHub Actions setup-node settings such as node-version: lts/*, Docker images using node:lts and platform builders that resolve an LTS channel at build time. A moving alias can select a newer major even when your repository did not change. Pin a major or digest for repeatable builds, then advance it deliberately after tests. ## Linux and native-addon compatibility require a real rehearsal The Node maintainers specifically flag a libatomic dependency in official Linux binaries since Node 25. Verify it exists in minimal or custom images and on older Linux environments. Reinstall or rebuild native addons against the new runtime where necessary, and run tests for loaders, build tools and application dependencies; don't assume a successful JavaScript-only smoke test covers native code. ## Supported older LTS lines are still viable Node 24 remains supported until April 2028 and Node 22 until April 2027 according to the Release Working Group schedule. Upgrading immediately to 26 is not compulsory merely because it is now LTS. Prioritise the October 21 security-patched releases on the branch you actually operate, then choose a tested major upgrade window. ## The release policy is changing after Node 26 Node's official lifecycle documentation says that starting with version 27 the project moves to an annual release cycle in which every major eventually enters LTS after its Current phase. This is a forward-looking scheduling change, not a reason to assume Node 27 is already production LTS. Confirm timelines in the current Release Working Group schedule before planning upgrades. ## Key details - Node.js v26.13.0 Lithium entered Active LTS on October 28, 2026; scheduled end-of-life April 30, 2029. - Upstream says v26.13.0 has only LTS metadata changes compared with v26.12.1. - Official Linux binaries since Node 25 link against libatomic, potentially requiring an extra OS package. - Node 24 and Node 22 remain supported LTS lines; upgrading to 26 is a choice, not an immediate security requirement. - Floating CI/container LTS selectors can move a build to a different major without a source change. - The October 21 Brotli/TLS security fixes are covered separately by BTN dossier #522. ## Builder takeaways - Inventory runtime versions in production, containers, build jobs and CI; check what each LTS alias resolves to. - Pin a major or image digest when reproducibility matters, then test Node 26 in a separate matrix before promotion. - Check libatomic on minimal Linux images and rebuild native addons against Node 26 where required. - Keep the currently deployed 22/24 branch patched while preparing a controlled upgrade. - Do not describe 26.13.0 as a new security patch or as introducing the full Node 26 feature set. ## What to watch - Provider and base-image LTS alias changes, especially CI and PaaS defaults. - Node 26 compatibility declarations from frameworks, package managers and native dependencies. - Any corrected release policy or support date in the Node.js Release Working Group schedule. ## Uncertainties - The exact timing at which a third-party Docker tag, version manager or PaaS alias switches to Node 26 varies by provider. - libatomic availability and native addon rebuild requirements vary by Linux distribution and dependency set. - The Release Working Group schedule is subject to change; the upstream release is authoritative for 26.13.0's status. ## Sources - [Node.js v26.13.0 Lithium LTS signed release](https://github.com/nodejs/node/releases/tag/v26.13.0) — Node.js maintainers / GitHub · primary release · 2026-10-28T00:00:00+13:00. LTS transition, April 2029 lifecycle, metadata-only changes and Linux libatomic warning. - [Node.js Releases and support policy](https://nodejs.org/en/about/previous-releases) — Node.js · primary documentation · 2026-10-28T00:00:00+13:00. Current LTS support status, new annual release policy, production guidance. - [Node.js Release Working Group schedule](https://github.com/nodejs/Release) — Node.js Release Working Group · primary schedule · 2026-10-28T00:00:00+13:00. 22/24/26 support dates and planned 27.x phases; schedule may lag live release status. - [Node 26 LTS: node:lts moves without a commit](https://indragustiprasetya.com/blog/node-26-lts-on-oct-28-node-lts-moves-without-a-commit.html) — Indra Gusti Prasetya · independent technical analysis · 2026-10-07T00:00:00+13:00. Practical risk of floating LTS selectors and native addon ABI; written ahead of actual promotion.