Skip to content

chore: remove version support link #8002

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ovflowd
Copy link
Member

@ovflowd ovflowd commented Jul 20, 2025

With the work on #7906 and our EOL and ESP program links becoming prominent in multiple pages (downloads, about, home, security blog posts, etc) the need for a dedicated "version support" (which isn't clear IMO) isn't needed anymore.

@Copilot Copilot AI review requested due to automatic review settings July 20, 2025 15:26
@ovflowd ovflowd requested a review from a team as a code owner July 20, 2025 15:26
Copy link

vercel bot commented Jul 20, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Jul 20, 2025 3:26pm

@ovflowd ovflowd added the github_actions:pull-request Trigger Pull Request Checks label Jul 20, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes the "Version Support" link from the website footer as part of consolidating version-related information into more prominent locations across the site.

  • Removes the "versionSupport" translation key from the English locale file
  • Removes the "Version Support" navigation link from the footer configuration

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
packages/i18n/src/locales/en.json Removes the "versionSupport" translation key
apps/site/navigation.json Removes the version support link from footer navigation

Copy link
Contributor

github-actions bot commented Jul 20, 2025

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 90 🟢 100 🟢 100 🔴 66 🔗
/en/about 🟢 100 🟢 97 🟢 100 🔴 58 🔗
/en/about/previous-releases 🟢 99 🟢 93 🟢 100 🔴 61 🔗
/en/download 🟢 98 🟢 100 🟢 100 🔴 66 🔗
/en/blog 🟢 100 🟢 100 🟢 96 🔴 69 🔗

Copy link

codecov bot commented Jul 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.03%. Comparing base (ba6db41) to head (7b848fe).

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8002      +/-   ##
==========================================
- Coverage   73.03%   73.03%   -0.01%     
==========================================
  Files          95       95              
  Lines        8341     8337       -4     
  Branches      217      217              
==========================================
- Hits         6092     6089       -3     
+ Misses       2248     2247       -1     
  Partials        1        1              

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

@ljharb
Copy link
Member

ljharb commented Jul 20, 2025

I disagree; it's definitely still needed and should remain.

@avivkeller
Copy link
Member

avivkeller commented Jul 20, 2025

Could you elaborate on that? We aren't removing the page, just removing it from the footer. Users can still go to the "Downloads" page, and select "Releases", or select "About" and select "Releases"

@ovflowd
Copy link
Member Author

ovflowd commented Jul 20, 2025

Could you elaborate on that? We aren't removing the page, just removing it from the footer. Users can still go to the "Downloads" page, and select "Releases", or select "About" and select "Releases"

Note that the current link was just going to About > Previous Releases. Not the EOL/ESP page. The button is highlighted already on Home, About, Blog Posts, Download pages, pretty much all relevant pages of the website. Being in the footer doesn't really matter IMO, and removing this link allows us to accomodate the version pills in small screens. Otherwise we need to update the designs for better breakpoints.

@ljharb
Copy link
Member

ljharb commented Jul 20, 2025

I think it’s premature to remove this link until the new pages have been up long enough to figure out where traffic is coming from.

Copy link
Collaborator

@bmuenzenmeyer bmuenzenmeyer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree with jordan - let's slow down a bit and let #7990 land first
I also think there are merits to keeping some sort of EOL information in the header or footer...as nothing in our navigation currently links to it (even in 7990)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants