[MattIPv4]

Description

Handling for the EOL release status was missing, allowing a user to sit on the /download/current or /download/alpha routes while having an EOL version selected.

Validation

Changing from a Current version to an EOL version redirects from /download/current to /download.

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 22, 2026 3:07pm UTC

[MattIPv4]

Posing the same question here that I posed on Slack:

👀 When you change the version dropdown from LTS to Current, we do a full redirect currently. Do we need that? Could we manually push a history entry instead to avoid that re-render? Technically, the routes go to different pages, but I believe the content on them is identical?

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9232      +/-   ##
==========================================
- Coverage   86.13%   86.11%   -0.03%     
==========================================
  Files          86       87       +1     
  Lines        6082     6150      +68     
  Branches      362      369       +7     
==========================================
+ Hits         5239     5296      +57     
- Misses        839      850      +11     
  Partials        4        4              

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

[Copilot]

🟢 Approval recommended

The focused condition change covers both affected routes without changing other release-status behavior, and no blocking issues were identified.

No open issues 🎉

What changed in this PR

This PR extends the download page’s existing redirect logic to handle end-of-life (EOL) releases, keeping the route consistent with the selected version.

Changes:

• Redirects to /download when an EOL version is selected on /download/current or /download/alpha.
• Preserves the existing redirect behavior for LTS releases.

File	Description
apps/​site/​components/​Downloads/​Release/​VersionDropdown.tsx	Adds EOL status to the existing redirect condition.

_{Review effort: Balanced}

[github-actions]

📦 Build Size Comparison

Summary

Metric	Value
Old Total First Load JS	7.20 MB
New Total First Load JS	7.20 MB
Delta	84.00 B (0.00%)

Changes

🔄 Modified Routes (4)

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

[AugustinMauroy]

do we have unit/e2e test for this component ?

[MattIPv4]

do we have unit/e2e test for this component ?

No, there's currently no test coverage for the component as a whole. I can add it if desired.

[AugustinMauroy]

I think it's maybe a good idea since this component/part is quiet "critique" for the UX

[ovflowd]

do we have unit/e2e test for this component ?

No, there's currently no test coverage for the component as a whole. I can add it if desired.

I'd appreciate that yeah!

[MattIPv4]

Landing this as a hot-fix for broken behaviour 🙏