Repository navigation
Prepare for v27 #1187
Description
Pull requests needed to prepare the v27.x release line. The first Alpha, v27.0.0-alpha.0.0.0, is planned for 2026-10-28.
- nodejs/changelog-maker: fix: recognise alpha release commits (fix: recognise alpha release commits changelog-maker#279)
- nodejs/node-core-utils: feat(release): support alpha releases (feat(release): support alpha releases node-core-utils#1224)
- nodejs/nodejs-dist-indexer: feat: support alpha versions (feat: support alpha versions nodejs-dist-indexer#107)
- nodejs/node: build,doc,tools: support alpha releases (build,doc,tools: support alpha releases node#66796)
- nodejs/remark-preset-lint-node: feat: accept alpha versions in YAML comments (feat: accept alpha versions in YAML comments remark-preset-lint-node#729)
- nodejs/build: build: add expected assets for v27.x (build: add expected assets for v27.x build#4522)
- nodejs/nodejs.org: feat: support the Alpha release phase (feat: support the Alpha release phase nodejs.org#9223)
- nodejs/Release: doc: document the Alpha phase and v27 schedule (doc: document the Alpha phase and v27 schedule #1188)
These are all the changes I could map. If I missed something, please let me know in this issue.
cc @nodejs/releasers
Activity
fix: recognise alpha release commits
feat(release): support alpha releases
feat: support the Alpha release phase
feat: support the Alpha release phase
feat: accept alpha versions in YAML comments
doc: document the Alpha phase and v27 schedule
MikeMcC399 commentedon Oct 18, 2026
joyeecheung commentedon Oct 19, 2026
I am working on a V8 14.6 (on 26) -> 15.6 (on main currently) highlights for the release notes, it's still currently incomplete. https://hackmd.io/@openjs-nodejs/Bkrj9UAjMg
Note that V8 15.6 will have a stable release on Oct 20 (which would include bug fixes etc. they catch from Chrome). I'll refresh the V8 version on main then, and it shouldn't have much build issues. I think it would be great if 27 ship with that stable release. Planning to finalize the V8 hightlights after that update.
fix: recognise alpha release commits (#279)
doc: document the Alpha phase and v27 schedule (#1188)
build: add expected assets for v27.x (#4522)
feat: support the Alpha release phase (#9223)
MikeMcC399 commentedon Oct 26, 2026
doc: document the alpha release process
RafaelGSS commentedon Oct 27, 2026
Created
v27.xandv27.x-stagingfrommain(98dbf6070e8) and thev27.xlabels (v27.x,backport-blocked-v27.x,backport-open-v27.x,backport-requested-v27.x,backported-to-v27.x,dont-land-on-v27.x)feat: support alpha versions (#107)
feat(release): support alpha releases (#1224)
doc: note linear history rule on branch-off
MikeMcC399 commentedon Nov 1, 2026
Related issues:
latest-v27.xin https://nodejs.org/download/release #1196MikeMcC399 commentedon Nov 2, 2026
Please open a Release plan issue for Node.js 27, like for #1152 so that downstream consumers know what to expect. I'm assuming a 2 week cadence on Node.js 27 Alpha releases, but I don't know if that is the plan or not.
richardlau commentedon Nov 2, 2026
I think that might be waiting on #1193 to generate the schedule.
richardlau commentedon Nov 2, 2026
Not just that. Opened #1197.
MikeMcC399 commentedon Nov 2, 2026
https://nodejs.org/download/release/latest/ contains v26.13.0 which is the Active LTS release.
The following definition in Current and LTS releases seems to be incomplete:
At the moment the relevant release for
latestis the Active LTS release. There is no release line in status Current at the moment, so the definition should probably say something like:You could also just say that
latestmeans the latest non-alpha release. I can put this into a separate topic somewhere if that makes sense. I would prefer to leave the exact wording to the Release WG though.