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.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9223 +/- ##
==========================================
+ Coverage 86.13% 86.28% +0.14%
==========================================
Files 86 86
Lines 6075 6139 +64
Branches 360 370 +10
==========================================
+ Hits 5233 5297 +64
Misses 838 838
Partials 4 4 ☔ View full report in Codecov by Harness. |
📦 Build Size ComparisonSummary
Changes🔄 Modified Routes (4)
|
| if (release?.status === 'LTS' && pathname.includes('current')) { | ||
| if ( | ||
| release?.status === 'LTS' && | ||
| (pathname.includes('current') || pathname.includes('alpha')) |
There was a problem hiding this comment.
we don't need that right ? since this for redirecting "old" link
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
There was a problem hiding this comment.
Can we fix this upstream rather than writing custom logic around nodevu?
There was a problem hiding this comment.
+1 @bnb would you mind updating nodevu to support this? I can also bake a PR to nodevu
There was a problem hiding this comment.
feat: support the Alpha release phase