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.