Will Node.js 26 enter Active LTS in October 2026 on schedule?
Published
Current View
Pending, with October 2026 still the documented plan. As of September 23, 2026, the official Node.js Release Working Group schedule lists October 28, 2026 as Node.js 26’s Active LTS start; both supplied official pages still classify it as Current. This supports an October target, not a confirmed on-time transition. The investigated material does not establish the original target, dated schedule revisions, or an announcement confirming entry into Active LTS, so whether it ultimately happens on schedule remains unresolved.
Reasons
- The current official Release Working Group schedule sets Node.js 26’s Active LTS start for October 28, 2026. This establishes the current target, but not whether that target has changed from an earlier plan.
- Both official pages list Node.js 26 as Current and record its initial release as May 5, 2026. The releases overview records its latest update as September 21, 2026; these status entries support a pending rather than completed Active LTS transition.
Counter-evidence
- Both supplied official pages classify Node.js 26 as Current, not Active LTS. This rules out treating these pages as confirmation of a completed transition, but does not indicate a delay before the target date.
- The schedule explicitly says dates are subject to change, and the release policy provides for date changes with at least 14 days’ notice. October 28 is therefore a plan, not a guarantee; the policy itself is not evidence that a change has occurred.
Limitations
- The official pages retrieved on September 22 are treated as the latest supplied status evidence for the September 23 assessment.
- Coverage is limited to the two supplied official pages. No dated schedule history or individual release announcement was investigated; missing evidence here does not establish that revisions or announcements do not exist.
- “On schedule” cannot be confirmed against an original baseline until that baseline and the actual transition date are established.
- What was Node.js 26’s originally documented Active LTS target? The two supplied current pages do not establish a dated earlier target or original schedule baseline.
- Were any Node.js 26 Active LTS schedule revisions documented before the asOf? Dated revision history and change announcements are not established by the two supplied pages.
- Does a separate official release announcement establish a transition or an effective transition date? No individual announcement was investigated because the allowed source boundary contains only the releases overview and Release Working Group repository page.
What to watch next
- Dated official schedule history establishing the original Node.js 26 Active LTS target and any subsequent revisions.
- An official revision or announcement changing the October 28, 2026 target.
- An official Node.js 26 release announcement confirming entry into Active LTS and its effective date.
- Reassessment at the target date and after October ends, without treating missing confirmation alone as proof of delay.