88| [ 24.x] [ ] | ** Active LTS** | [ Krypton] [ ] | 2025-05-06 | 2025-10-28 | 2026-10-20 | 2028-04-30 |
99| [ 26.x] [ ] | ** Current** | | 2026-05-05 | 2026-10-28 | 2027-10-20 | 2029-04-30 |
1010
11+ | Release | Status | Codename | Alpha Start | Current Start | LTS Start | End-of-life |
12+ | :--: | :---: | :---: | :---: | :---: | :---: | :---: |
13+ | 27.x | ** Alpha** | | 2026-10-28 | 2027-04-22 | 2027-10-20 | 2030-04-30 |
14+
1115Dates are subject to change.
1216
1317<p ><img src =" schedule.svg " alt =" LTS Schedule " /></p >
@@ -16,23 +20,38 @@ The Release schedule is available also as a [JSON][] file.
1620
1721### Release Phases
1822
19- There are three phases that a Node.js release can be in: 'Current', 'Active
20- Long Term Support (LTS)', and 'Maintenance'. Odd-numbered release lines are not
21- promoted to LTS - they will not go through the 'Active LTS' or 'Maintenance'
23+ There are four phases that a Node.js release can be in: 'Alpha', 'Current',
24+ 'Active Long Term Support (LTS)', and 'Maintenance'. Starting with Node.js 27,
25+ every release line goes through the 'Alpha' phase before its first 'Current'
26+ release, and every release line is promoted to LTS. Those release lines stay in
27+ 'Active LTS' for the whole 30 months of Long Term Support and do not go through
28+ the 'Maintenance' phase. See the
29+ [ Evolving the Node.js Release Schedule] [ ] announcement for details.
30+
31+ Release lines up to and including Node.js 26 follow the previous schedule: they
32+ do not go through the 'Alpha' phase, and odd-numbered release lines were not
33+ promoted to LTS - they did not go through the 'Active LTS' or 'Maintenance'
2234phases.
2335
36+ * Alpha - Should incorporate most of the changes that land on ` nodejs/node `
37+ main branch, including * semver-major* (breaking) changes. Alpha releases (for
38+ example, ` 27.0.0-alpha.0.0.0 ` ) are signed, tagged, and tested through
39+ [ CITGM] [ ] , but their API and ABI may change between releases. They are intended
40+ for library authors and CI pipelines, not for production use.
2441 * Current - Should incorporate most of the non-major (non-breaking)
2542 changes that land on ` nodejs/node ` main branch.
2643 * Active LTS - New features, bug fixes, and updates that have been audited by
2744 the Release team and have been determined to be appropriate and stable for the
2845 release line.
29- * Maintenance - Critical bug fixes and security updates. New features may be
30- added at the discretion of the Release team - typically only in cases where
31- the new feature supports migration to later release lines.
46+ * Maintenance (release lines up to Node.js 26 only) - Critical bug fixes and
47+ security updates. New features may be added at the discretion of the Release
48+ team - typically only in cases where the new feature supports migration to
49+ later release lines.
3250
3351Changes required for critical security and bug fixes may lead to * semver-major*
34- changes landing within a release stream, such situations will be rare and will
35- land as * semver-minor* . Although, those changes should have a revert option included.
52+ changes landing within a Current or LTS release stream, such situations will be
53+ rare and will land as * semver-minor* . Although, those changes should have a
54+ revert option included.
3655
3756The term 'supported release lines' will be used to refer to all release lines
3857that are not End-of-Life.
@@ -76,7 +95,7 @@ Its responsibilities are:
7695* Define the content of releases.
7796* Generate and create releases.
7897* Test Releases.
79- * Manage the LTS and Current branches including backporting changes to
98+ * Manage the Alpha, Current, and LTS branches including backporting changes to
8099 these branches.
81100* Define the policy for what gets backported to release streams.
82101
@@ -104,21 +123,31 @@ Working Group.
104123
105124## Release Plan
106125
107- New * semver-major* releases of Node.js are branched from ` main ` every six
108- months. New even-numbered versions are released in April and odd-numbered
109- versions in October.
110-
126+ Starting with Node.js 27, a new release line is branched from ` main ` once a
127+ year, in October, and receives Alpha releases for six months. The first Alpha
128+ release of a new release line happens around the same time the previous release
129+ line transitions to Long Term Support. Each April, the release line in Alpha
130+ gets its first * semver-major* release (for example, ` 27.0.0 ` ) and enters the
131+ 'Current' phase.
132+
133+ Every release line stays 'Current' for six months, then transitions to Long
134+ Term Support in October. The transition to Long Term Support will happen in a
135+ * semver-minor* release. Every release line receives 30 months of Long Term
136+ Support, for a total of 36 months from its first Current release to
137+ End-of-Life.
138+
139+ Release lines up to and including Node.js 26 follow the previous schedule: new
140+ * semver-major* releases were branched from ` main ` every six months, with
141+ even-numbered versions released in April and odd-numbered versions in October.
111142In coordination with a new * odd-numbered* major release, the previous
112- * even-numbered* major version will transition to Long Term Support. The
113- transition to Long Term Support will happen in a * semver-minor* release and
114- should happen after the new major version is released.
143+ * even-numbered* major version transitioned to Long Term Support. Every even
144+ (LTS) major version is actively maintained for 12 months from the date it
145+ enters LTS coverage. Following those 12 months of active support, the major
146+ version transitions into "maintenance" mode for 18 months. Prior to Node.js 12,
147+ the active period was 18 months and the maintenance period 12 months.
115148
116- Every even (LTS) major version will be actively maintained for 12 months from
117- the date it enters LTS coverage. Following those 12 months of active support,
118- the major version will transition into "maintenance" mode for 18 months. Prior
119- to Node.js 12, the active period was 18 months and the maintenance period 12
120- months. See [ Releases Phases] ( #release-phases ) for details of which changes
121- are expected to land during each release phase.
149+ See [ Releases Phases] ( #release-phases ) for details of which changes are
150+ expected to land during each release phase.
122151
123152The exact date that a release will be moved to LTS, moved between LTS modes,
124153or deprecated will be chosen no later than the first day of the month it is to
@@ -144,9 +173,9 @@ commits are backported for a future Node.js v4 release, those must come in the
144173form of pull requests opened against the ` v4.x-staging ` branch. ** Commits are
145174only landed in the ` v4.x ` branch when a new ` v4.x ` release is being prepared.**
146175
147- Generally, changes are expected to live in a * Current* release for at least 2
148- weeks before being backported. It is possible for a commit to land earlier at
149- the discretion of the Release working group.
176+ Generally, changes are expected to live in an * Alpha * or * Current* release for
177+ at least 2 weeks before being backported. It is possible for a commit to land
178+ earlier at the discretion of the Release working group.
150179
151180[ Argon ] : https://nodejs.org/download/release/latest-argon/
152181[ Boron ] : https://nodejs.org/download/release/latest-boron/
@@ -160,6 +189,8 @@ the discretion of the Release working group.
160189[ Jod ] : https://nodejs.org/download/release/latest-jod/
161190[ Krypton ] : https://nodejs.org/download/release/latest-krypton/
162191[ JSON ] : schedule.json
192+ [ CITGM ] : https://github.com/nodejs/citgm
193+ [ Evolving the Node.js Release Schedule ] : https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule
163194[ nodejs16eol ] : https://nodejs.org/en/blog/announcements/nodejs16-eol/
164195[ 4.x ] : https://nodejs.org/download/release/latest-v4.x/
165196[ 5.x ] : https://nodejs.org/download/release/latest-v5.x/
0 commit comments