[MattIPv4]

Description

The alert box shown when an LTS release is selected offers the user the option to use the latest release instead. However, that link to /download/current currently shows the LTS release, as there is no Current release. Instead, we should fall back to /download/alpha if there is no Current release, but there is an Alpha release.

Validation

/download shows a CTA linking to /download/alpha for the latest version.

Related Issues

cc #9223

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run pnpm format to ensure the code follows the style guide.
• I have run pnpm test to check if all tests are passing.
• I have run pnpm build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
nodejs-org	Ready	Preview	Oct 29, 2026 8:40pm UTC

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.11%. Comparing base (b86c448) to head (585e30d).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9244      +/-   ##
==========================================
- Coverage   86.14%   86.11%   -0.04%     
==========================================
  Files          87       87              
  Lines        6149     6149              
  Branches      369      369              
==========================================
- Hits         5297     5295       -2     
- Misses        848      850       +2     
  Partials        4        4              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

[Copilot]

🟡 Changes recommended

A Server Component consumes client-only release context, breaking archive-page rendering, while missing providers suppress LTS notices on previous-release and archive pages.

2 open issues

• Consume ReleasesContext from a client component · New
• Provide release availability to archive release modals · New

What changed in this PR

This PR updates the shared LTS release alert to link to Alpha downloads when no Current release exists, building on the Alpha release support introduced in #9223.

Changes:

• Reads release availability from ReleasesContext.
• Prefers /download/current, falling back to /download/alpha.
• Hides the LTS notice when neither release status is available.

File	Description
apps/​site/​components/​withReleaseAlertBox.tsx	Selects the LTS alert’s download link based on Current and Alpha availability.

_{Review effort: Balanced}

[ovflowd]

I agree with you, but this approach is not ideal, as it transforms this component in client-side one; We shouldn't use ReleasesContext

[MattIPv4]

We shouldn't use ReleasesContext

What's the alternative? How else does this component get the data to know what the current releases are? Prop-drilling?

[ovflowd]

We shouldn't use ReleasesContext

What's the alternative? How else does this component get the data to know what the current releases are? Prop-drilling?

Yes! Check the callers of this Component. I think it is called within MDX and surrounded on the Release Provider already. So you can simply pass what you need.

[ovflowd]

Here:

nodejs.org/apps/site/pages/id/download/archive/index.mdx

Line 22 in b86c448

<WithReleaseAlertBox status={release.status} />

[ovflowd]

Also small nit, could you rename this component from withReleaseAlertBox just to ReleaseAlertBox lol

[MattIPv4]

Yes! Check the callers of this Component. I think it is called within MDX and surrounded on the Release Provider already. So you can simply pass what you need.

👍 I figured as we have a context we should use the context, as that's what they're for, but will switch to prop-drilling instead. I assume I'll need to update the translations here as to not braek them?

Also small nit, could you rename this component from withReleaseAlertBox just to ReleaseAlertBox lol

Yeh, can do, no idea why all these things are called With....

[github-actions]

📦 Build Size Comparison

Summary

Metric	Value
Old Total First Load JS	7.21 MB
New Total First Load JS	7.21 MB
Delta	1.11 KB (+0.02%)

Changes

🔄 Modified Routes (4)

Route	Old First Load JS	New First Load JS	Delta
/[locale]	1.69 MB	1.69 MB	📈 285.00 B (+0.02%)
/[locale]/[...path]	1.69 MB	1.69 MB	📈 285.00 B (+0.02%)
/[locale]/blog/[...path]	1.69 MB	1.69 MB	📈 285.00 B (+0.02%)
/[locale]/download/archive/[version]	1.69 MB	1.69 MB	📈 285.00 B (+0.02%)

[MattIPv4]

Also small nit, could you rename this component from withReleaseAlertBox just to ReleaseAlertBox lol

Yeh, can do, no idea why all these things are called With....

Actually I think this should probably happen as a separate PR, and perhaps all of them at once, to keep this diff isolated.

[github-actions]

Note

Your Pull Request seems to be updating Translations of the Node.js Website.

Whilst we appreciate your intent; Any Translation update should be done through our Crowdin Project.
We recommend giving a read on our Translation Guidelines.

Thank you!

[MattIPv4]

Folks happy for this to land fast-tracked as a bug fix?

[ovflowd]

👍 I figured as we have a context we should use the context, as that's what they're for, but will switch to prop-drilling instead. I assume I'll need to update the translations here as to not braek them?

In this context is due to SSR/CSR context drilling. Using a Provider here would require this context to go to Client-Side.