Repository navigation
feat(ranges): add an alpha range and keep alpha releases out of the others - #90
Merged
Merged
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>
…thers Node.js 27 starts shipping vN.0.0-alpha.X.Y.Z releases before a line's first Current release. ranges now skips them everywhere except a new `alpha` range, which lists the alphas of a line in its Alpha phase, so `all.newest` stays the newest stable release. ranges also takes an optional second `options` argument that it passes to @nodevu/core, and depends on the 1.0.0 workspace versions of core and aliases.
…91) Co-authored-by: botandbang <337765928+botandbang@users.noreply.github.com>
… and versions in comments
Merged
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
2 participants
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.
Starting with Node.js 27, each line gets
vN.0.0-alpha.X.Y.Zreleases before its first Current release (core support landed in #86). Without this,all.newestturns into an alpha during the Alpha phase, and old alphas later show up incurrentandeol.Added: an
alpharange and alias that lists the alphas of lines in the Alpha phase, documented in both READMEs.ranges(filter, options)now passesfetchandnowthrough to core.ranges/test/alpha.test.jscovers every phase, using the 27.x schedule from nodejs/Release#1188.Changed: one check at the top of the release loop keeps alphas out of every range except
alpha. ranges now depends on@nodevu/core ^1.0.0and@nodevu/aliases ^1.0.0, which link to the workspace packages; before this it tested against the published core 0.3.0. ranges can't be published until core 1.x is on npm.Five existing ranges tests fail right now because they use live data and no line is in the
ltsphase until 26.x's first LTS release. The next PR in this stack fixes that.