Skip to content

2026-10-28, Version 26.13.0 'Lithium' (LTS) - #66965

Open
richardlau wants to merge 1 commit into
v26.xfrom
v26.13.0-proposal
Open

richardlau wants to merge 1 commit into
v26.xfrom
v26.13.0-proposal

Conversation

@richardlau

@richardlau richardlau commented Oct 23, 2026 •

Copy link
Copy Markdown
Member

Notable changes:

This release marks the transition of Node.js 26.x into Long Term Support (LTS) with the codename 'Lithium'. It will continue to receive updates through to the end of April 2029.

Other than updating metadata, such as the process.release object, to reflect that the release is LTS, no further changes from Node.js 26.12.1 are included.

If you are updating from an earlier Long Term Support release (e.g. Node.js 24 or 22 or earlier) please note that since Node.js 25 the official binaries for Linux are linked against libatomic, which may need to be installed separately depending on your Linux distribution.


Per policy, this contains no new functional or bugfix commits since 26.12.1, as they will fail to meet the "two weeks in a current release" policy, and merely bumps metadata to identify the release as Long Term Support.

Notable changes:

This release marks the transition of Node.js 26.x into Long Term Support (LTS)
with the codename 'Lithium'. It will continue to receive updates through to
the end of April 2029.

Other than updating metadata, such as the `process.release` object, to reflect
that the release is LTS, no further changes from Node.js 26.12.1 are included.

PR-URL: #66965
Signed-off-by: Richard Lau <richard.lau@ibm.com>
@nodejs-github-bot nodejs-github-bot added meta Issues and PRs related to the general management of the project. needs-ci PRs that need a full CI run. v26.x Issues that can be reproduced on v26.x or PRs targeting the v26.x-staging branch. labels Oct 23, 2026
@bricss

bricss commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Would be great to pull 🧲 this bug 🐞 fix πŸͺ› in #66161

@richardlau

richardlau commented Oct 23, 2026 •

Copy link
Copy Markdown
Member Author

Would be great to pull 🧲 this bug 🐞 fix πŸͺ› in #66161

"Functional" here means affecting runtime behaviour (including untested bug fixes)

Per policy, this contains no new functional commits since 26.12.1 and merely bumps metadata to identify the release as Long Term Support.

I'll update the description to include that clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

meta Issues and PRs related to the general management of the project. needs-ci PRs that need a full CI run. v26.x Issues that can be reproduced on v26.x or PRs targeting the v26.x-staging branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants