chore: updated docs for releases

[ovflowd]

This PR updates the docs for Releases, further tapping into Community and Official requirements.

[Copilot]

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• apps/site/pages/en/about/previous-releases.mdx: Language not supported

[vercel]

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

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Apr 3, 2025 3:30pm

[ovflowd]

cc @nodejs/nodejs-website

[github-actions]

Lighthouse Results

URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟢 99	🟢 100	🟢 100	🟢 91	🔗
/en/about	🟢 100	🟢 100	🟢 100	🟢 91	🔗
/en/about/previous-releases	🟢 100	🟢 100	🟢 100	🟢 92	🔗
/en/download	🟢 98	🟢 100	🟢 100	🟢 91	🔗
/en/blog	🟢 100	🟢 100	🟢 96	🟢 92	🔗

[github-actions]

Unit Test Coverage Report

Title	Lines	Statements	Branches	Functions
@node-core/ui-components		95.83% (161/168)	77.86% (102/131)	88.57% (31/35)
@nodejs/website		84.73% (494/583)	76.03% (165/217)	86.99% (107/123)

Title	Tests	Skipped	Failures	Errors	Time
@node-core/ui-components	24	0 💤	0 ❌	0 🔥	4.96s ⏱️
@nodejs/website	156	0 💤	0 ❌	0 🔥	6.445s ⏱️

[bmuenzenmeyer]

This looks good to me but for our own sake of future documentation, can we link to the discussions (in the PR, not the code) that led to these criteria? I am pretty sure many conversations happened. I dont want the website team to have to defend itself months from now.

[avivkeller]

Discussions (that I am aware of):

• https://openjs-foundation.slack.com/archives/C044DNU6TEH/p1739802238093859
• Define criteria for inclusion in the Downloads page #7536

[avivkeller]

Merging, as:

• Over a month has passed since the original suggestion with no objections and multiple👍s from the package maintenance team
• 72 hours have passed since the PR was opened, with no objections, and approvals from package maintenance team members

[GeoffreyBooth]

I just learned of this because it closed the original issue. Next time please comment on the issue when you open a PR to address it, and tagging the package maintenance team would help too.

[avivkeller]

😅 that's on me! I didn't realize that the teams weren't aware of this PR, I thought you all knew.

I'll keep that in account for the future.

[ovflowd]

I just learned of this because it closed the original issue. Next time please comment on the issue when you open a PR to address it, and tagging the package maintenance team would help too.

Hmm, was the issue connected somewhere? I don't see any issue linked here?

[ovflowd]

Oh, Aviv linked it. Apologies, @GeoffreyBooth, I also forgot to tag package maintenance here. Would you feel comfortable reviewing the contents of this PR? I can address any feedback in a follow-up PR!

[styfle]

I don't believe Docker releases are available simultaneously with the official release even though its listed as Official here:

[ovflowd]

Yup, that is correct. But it is a 1st party installation method (provided by the Node project) hence it is official, although it does not fulfils that specific criteria.