Node.js 25 and 26 LTS Timeline for NodeBB Forum Admins
Operating a self-hosted community with NodeBB requires keeping server environments aligned with upstream runtime schedules. In late October 2026, community owners and administrators face key maintenance decisions across modern Node.js release cycles. Tracking these milestones helps forum hobbyists protect user sessions, maintain reliable database connections, and avoid running unmaintained server software. Official cycle information tracked by the endoflife.date Node.js Release Cycle Data clarifies how odd-numbered intermediate releases transition into stable, even-numbered Long Term Support branches.
October 2025: The Introduction of Intermediate Release Cycle 25
The release lifecycle for cycle 25 commenced on 2025-10-15. As an odd-numbered release cycle, cycle 25 was designed for short-term evaluation rather than extended production hosting. Its status designated that LTS was false, and extendedSupport was false as well. Maintenance for cycle 25 concluded when its active support window reached its limit on 2026-04-01. On that same day, 2026-04-01, maintainers published version 25.9.0 as the latest build for cycle 25. For forum administrators hosting NodeBB, running an odd-numbered branch required planning for a rapid migration path before routine maintenance updates ceased entirely.
May 2026: Cycle 26 Launches in the Current Phase
Cycle 26 entered the official release timeline on 2026-05-05. During this initial phase, cycle 26 served as the Current release line. This stage provided forum administrators with an opportunity to test modern runtime features, verify NodeBB core functionality on test environments, and validate plugin compatibility without risking production stability. Throughout this period, production forums remained recommended on existing Long Term Support cycles while developers and server operators monitored cycle 26 builds leading into autumn.
June 2026: End of Life Arrives for Release Cycle 25
The final milestone for cycle 25 arrived on 2026-06-01, marking its formal end of life (eol). After 2026-06-01, cycle 25 stopped receiving any security patches, bug resolutions, or maintenance updates. Administrators managing active community forums who had not migrated off cycle 25 faced potential operational vulnerabilities. Earlier in the spring, cycle 20 had also completed its lifecycle, reaching end of life on 2026-04-30 with version 20.20.2 released on 2026-03-24. These scheduled retirements reinforced why forum operators must systematically eliminate unsupported runtimes from production servers.
October 2026: Cycle 26 Enters Long Term Support
In October 2026, cycle 26 achieves its Long Term Support milestone, providing forum administrators with a dependable, production-ready foundation for hosting NodeBB. The latest build recorded for cycle 26 is version 26.12.1, published on 2026-10-21. For administrators assessing other branches during this transition, the endoflife.date Node.js Release Cycle Data documents that cycle 24 reached version 24.22.1 on 2026-10-21, following the conclusion of its active support window on 2026-10-20. Meanwhile, cycle 22 reached version 22.23.4 on 2026-10-21, operating with extendedSupport marked as true after its active support phase ended on 2025-10-21. Cycle 26 now stands ready to carry production forum workloads forward with multi-year stability.
Looking Ahead: Support and End of Life Milestones Through 2029
The timeline for cycle 26 extends several years into the future, giving forum teams a predictable maintenance runway:
- Active support for cycle 26 continues until 2027-10-27.
- Final end of life for cycle 26 is scheduled for 2029-04-30.
- Extended support for cycle 26 is marked as false.
- By comparison, cycle 22 reaches its scheduled end of life on 2027-04-30.
- Cycle 24 maintains an end of life target date of 2028-04-30.
Having visibility through 2029-04-30 allows community managers to schedule platform upgrades well before upstream support windows close.
Server Preparation Checklist for NodeBB Admins
Transitioning a live community forum between Node.js runtimes requires methodical execution to prevent downtime or lost data. Administrators managing NodeBB installations should adopt a structured procedure during upgrade cycles:
- Create full snapshots of forum files and database records prior to runtime upgrades, following the steps outlined in How to Back Up Your Forum (and Actually Restore It).
- Review third-party NodeBB plugins on a non-production clone to verify that all extensions execute cleanly on the targeted release cycle.
- Verify server-level access permissions and firewall configurations to safeguard the host, consulting Forum Admin Security: 10 Steps to Protect Your Forum From Takeovers.
- Verify process manager configurations to ensure NodeBB services restart reliably across host reboots under the new runtime version.
Sources
endoflife.date Node.js Release Cycle Data
Published October 28, 2026. No affiliate links on this page. Facts come from the sources linked above; check them for updates.