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.

@codecov

codecov Bot commented Oct 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.77%. Comparing base (26e72d8) to head (18b32a3).
⚠️ Report is 21 commits behind head on v26.x.

Additional details and impacted files
@@            Coverage Diff             @@
##            v26.x   #66965      +/-   ##
==========================================
- Coverage   90.80%   90.77%   -0.04%     
==========================================
  Files         775      775              
  Lines      273312   273467     +155     
  Branches    52454    52512      +58     
==========================================
+ Hits       248183   248228      +45     
- Misses      16025    16103      +78     
- Partials     9104     9136      +32     

see 57 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@richardlau richardlau added the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Oct 23, 2026
@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Oct 23, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

This comment was marked as duplicate.

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.

6 participants