Skip to content

Conversation

@naveenkarmegam
Copy link

@naveenkarmegam naveenkarmegam commented Dec 25, 2025

Description

Fixes a broken markdown link on the Previous Releases documentation page where /download was rendered as plain text instead of a clickable link. This change updates the sentence to use proper markdown link syntax for improved usability and consistency across the site.

Validation

  • Navigated to /en/about/previous-releases
  • Verified that the Download page link is now clickable and correctly routes to /download
  • Screenshot attached
image

Related Issues

Fixes #8451

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.

@naveenkarmegam naveenkarmegam requested a review from a team as a code owner December 25, 2025 15:12
@vercel
Copy link

vercel bot commented Dec 25, 2025

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

Project Deployment Review Updated (UTC)
nodejs-org Ready Ready Preview Dec 25, 2025 3:13pm

@github-actions
Copy link
Contributor

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/nodejs-website

Please review the changes when you have a chance. Thank you! 🙏

### Community Installation Methods

Community installation methods included on the self-service download page (/download) must also adhere to a minimum set of criteria:
Community installation methods included on the self-service [download page](/download) must also adhere to a minimum set of criteria:
Copy link
Member

Choose a reason for hiding this comment

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

This wasn't meant to be a link but to reference "what the self-service download page" is about (so /download) serves as a hint. So I'm unhappy with the proposed changes.

Copy link
Author

@naveenkarmegam naveenkarmegam Dec 25, 2025

Choose a reason for hiding this comment

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

Thanks for the clarification!
That makes sense - I misunderstood the intention behind the ( /download ) reference.
Would it be acceptable to adjust the wording slightly to make that intent clearer for readers?

For example, something like:
Community installation methods included on the self-service download page (located at /download) must also adhere to a minimum set of criteria:

This would keep it non-linking while making the meaning clearer.

Copy link
Member

Choose a reason for hiding this comment

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

That would make more sense yes :)

@codecov
Copy link

codecov bot commented Dec 25, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.77%. Comparing base (8ab0fd7) to head (c68b9b5).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8452      +/-   ##
==========================================
- Coverage   73.81%   73.77%   -0.05%     
==========================================
  Files         109      109              
  Lines        9255     9255              
  Branches      313      314       +1     
==========================================
- Hits         6832     6828       -4     
- Misses       2421     2425       +4     
  Partials        2        2              

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

@ovflowd
Copy link
Member

ovflowd commented Dec 25, 2025

Screenshot attached

No screenshot attached?

@avivkeller avivkeller changed the title docs: fix broken /download link on Nodejs Releases page (#8451) feat(previous-releases): convert plaintext link to markdown Dec 25, 2025
@naveenkarmegam
Copy link
Author

Apologies for the oversight. I forgot to include the screenshot in the description.
I’ve attached it now — thank you for letting me know.

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.

Broken markdown link on “Previous Releases” page – /download link not clickable

5 participants