Repository navigation
Conversation
Node.js 27 introduces Alpha releases versioned as vN.0.0-alpha.X.Y.Z (see nodejs/node#63135). - Keep Alpha versions in the release data instead of letting nodevu coerce them into vN.0.0, and give them the new Alpha status. - Add a /download/alpha page and warn that Alpha releases are not meant for production. - Fall back to the latest LTS on /download/current and /download/archive/current while there is no Current release. - Match pre-releases in the platform and installer checks. Refs: nodejs/Release#1187 Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4 of 8 tasks
|
Contributor
📦 Build Size ComparisonSummary
Changes🔄 Modified Routes (4)
|
| if (release?.status === 'LTS' && pathname.includes('current')) { | ||
| if ( | ||
| release?.status === 'LTS' && | ||
| (pathname.includes('current') || pathname.includes('alpha')) |
Member
There was a problem hiding this comment.
we don't need that right ? since this for redirecting "old" link
Member
Author
There was a problem hiding this comment.
It's not strictly needed, it only keeps the URL consistent with the selected release, like we do for /current. Happy to drop it if you prefer
MattIPv4
reviewed
Oct 18, 2026
1.1.0 supports the Alpha release phase: Alpha releases keep their pre-release identifiers instead of being coerced into `vN.0.0`, and every release has an `alpha.isAlpha` flag, like `lts.isLts`. Refs: cutenode/nodevu#86 Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
nodevu now keeps Alpha releases as they are, so the site no longer strips pre-releases before nodevu parses index.json and rebuilds them afterwards. The Alpha status comes from `alpha.isAlpha`, the same way LTS comes from `lts.isLts`. Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
This branch had an error being deployed
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
4 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.
feat: support the Alpha release phase
Note
I pushed two commits that bump
@nodevu/coreto 1.1.0, which supports Alpha releases (cutenode/nodevu#86), and drop the nodevu workaround. The Alpha status now comes fromalpha.isAlpha, like LTS does fromlts.isLts.CI will fail on
pnpm install(ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION) until 2026-10-22 00:09 UTC. 1.1.0 was published on 2026-10-21 at 00:09 UTC, and pnpm rejects packages younger than a day, even when they come from the lockfile. Re-running the failed checks after that should make them pass.