Node.js 26.x enters LTS as 'Lithium' with support through April 2029

The Node.js project has promoted its 26.x release line to Long Term Support status with the release of Node.js 26.13.0, codenamed 'Lithium'. This LTS designation commits the branch to maintenance updates through the end of April 2029, giving enterprises and downstream distributions a stable target for production deployments. Beyond updating the process.release object and other metadata to reflect LTS status, this release contains no changes from the preceding 26.12.1 current release.

Administrators migrating from earlier LTS lines such as Node.js 24 or 22 should note a platform-level change introduced in Node.js 25: official Linux binaries now link against libatomic, which may require separate installation on certain distributions. This dependency shift affects automated deployment pipelines and container images that previously relied on self-contained Node.js binaries.

LTS transition and Linux binary changes

• LTS metadata update: The process.release object now reports the 'Lithium' codename and LTS status, enabling runtime detection of support tier by applications and deployment tools.
• No functional delta: Version 26.13.0 is identical to 26.12.1 in all respects except metadata, representing a pure promotion rather than a feature or fix release.
• libatomic dependency: Since Node.js 25, official Linux binaries dynamically link libatomic, which may not be present in minimal container images or stripped-down server installations and must be installed separately.
• Support lifecycle: The LTS commitment runs through April 2029, establishing a predictable security and maintenance window for the 26.x line.

Why it matters

For Linux distribution maintainers and DevOps engineers, the libatomic linkage requirement demands attention when upgrading from Node.js 22 or 24 LTS, as existing deployment scripts and container base images may need dependency updates to avoid runtime failures. The 26.x LTS line provides a stable foundation for cloud-native and server-side JavaScript applications through 2029, aligning with enterprise upgrade cycles and reducing friction for organizations that deferred adoption during the current release phase.