You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Created v27.x and v27.x-staging from main (98dbf6070e8) and the v27.x labels (v27.x, backport-blocked-v27.x, backport-open-v27.x, backport-requested-v27.x, backported-to-v27.x, dont-land-on-v27.x)
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.
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.
I think that might be waiting on #1193 to generate the schedule.
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.
I think that might be waiting on [#1193](https://github.com/nodejs/Release/pull/1193) to generate the schedule.
I wonder if we could come up with a rule to include semver-major changes only in a few Alpha releases, so hopefully there's no longer a need to differentiate Alpha and Current releases. Maybe 2 months would be the right tradeoff (the more the 27 branch deviates from main, the higher the maintenance burden; hopefully 2 months is not enough time for the deviation to be painful).
So far we haven't included any semver-major changes in our Alpha versions (well except the very first one, obviously), and I haven't encountered any conflicts so far.
why would we not want them differentiated? the entire point of alphas is for people who want to try unstable, bleeding-edge code. If it's not something that should never be used in production, then "alpha" is the wrong name for it.
We want library authors to test with them. "alpha" might be the wrong name for it, what we're aiming for is for LTS to be for production, and Current and Alpha to be tested by library authors (to catch bugs/breakage before they reach LTS/production)
right - but alphas still should never go into production, and the vast majority of node users (who are not library authors) should actively be avoiding alphas.
Alpha are actual releases. The same care goes into preparing a Alpha release and a Current release, it's the same process, the same tests are run, etc. The difference is the semver guarentees.
right - but alphas still should never go into production, and the vast majority of node users (who are not library authors) should actively be avoiding alphas.
I don't think the vast majority of users are running on production, so I don't think they need to avoid Alpha more than Current
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)4 remaining items
MikeMcC399 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
MichaIng commentedon Nov 3, 2026
Is it intended that the alpha version appears in index.tab? I thought that was for (stable) releases only?
https://nodejs.org/download/release/index.tab
doc: note linear history rule on branch-off
doc: document the alpha release process
doc: note linear history rule on branch-off
aduh95 commentedon Nov 16, 2026
I wonder if we could come up with a rule to include semver-major changes only in a few Alpha releases, so hopefully there's no longer a need to differentiate Alpha and Current releases. Maybe 2 months would be the right tradeoff (the more the 27 branch deviates from
main, the higher the maintenance burden; hopefully 2 months is not enough time for the deviation to be painful).So far we haven't included any semver-major changes in our Alpha versions (well except the very first one, obviously), and I haven't encountered any conflicts so far.
ljharb commentedon Nov 16, 2026
why would we not want them differentiated? the entire point of alphas is for people who want to try unstable, bleeding-edge code. If it's not something that should never be used in production, then "alpha" is the wrong name for it.
aduh95 commentedon Nov 16, 2026
We want library authors to test with them. "alpha" might be the wrong name for it, what we're aiming for is for LTS to be for production, and Current and Alpha to be tested by library authors (to catch bugs/breakage before they reach LTS/production)
ljharb commentedon Nov 16, 2026
right - but alphas still should never go into production, and the vast majority of node users (who are not library authors) should actively be avoiding alphas.
MichaIng commentedon Nov 16, 2026
Basically setting "alpha" and "current" (latest stable release) equal seems weird, same like the fact that alpha versions are listed in https://nodejs.org/download/release/index.tab, where I would expect actual "releases", no alpha/beta/rc. https://github.com/nodejs/unofficial-builds/blob/main/www/install-node.sh also pulls the alpha versions now. Of course this can be all adjusted, but needs to be communicated.
aduh95 commentedon Nov 16, 2026
Alpha are actual releases. The same care goes into preparing a Alpha release and a Current release, it's the same process, the same tests are run, etc. The difference is the semver guarentees.
I don't think the vast majority of users are running on production, so I don't think they need to avoid Alpha more than Current
MichaIng commentedon Nov 16, 2026
Okay, then "alpha" is the entirely wrong name, indeed. But good to know.