Repository navigation
Conversation
Starting with 27.x, every Node.js release line gets Alpha releases, versioned as `vN.0.0-alpha.X.Y.Z`, before its first Current release, and schedule.json has an `alpha` date for it. Releases now keep their pre-release identifiers. Coercing them turned every Alpha release into `vN.0.0`, so they would overwrite each other, and `vN.0.0` itself once it ships. Every release has an `alpha.isAlpha` flag, like `lts.isLts`, and `support.phases` has the `alpha` date, with `alpha` as the current phase until the release line becomes Current. Release lines on the previous schedule get the same data as before, besides `alpha.isAlpha` being `false` on their releases. This holds for all 872 releases in today's index.json. Refs: https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule Refs: nodejs/nodejs.org#9223 Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
ovflowd
marked this pull request as ready for review
October 19, 2026 12:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds support for the Alpha phase of the new Node.js release schedule. Starting with 27.x, every release line gets Alpha releases (
vN.0.0-alpha.X.Y.Z) before its first Current release, andschedule.jsonhas analphadate for it.v27.0.0, so they would overwrite each other, andv27.0.0itself once it ships.alpha.isAlphaflag, likelts.isLts; the website uses the newest release's flags to tell a release line's status.support.phases.dateshas thealphadate, andsupport.phases.currentisalphaduring the Alpha phase instead of{}.phases.dates, where the code puts them.Release lines on the previous schedule get the same data as before, besides
alpha.isAlphabeingfalse. I compared the output withmainfor all 872 releases in today'sindex.json, at dates from 2016 to 2030.The new tests pass made-up data through the
fetchoption, since the static test data is a snapshot of the realindex.json, which has no Alpha releases yet.With this, the website can drop its nodevu workaround; its tests pass against this branch without it.
Refs: nodejs/nodejs.org#9223