Skip to content

Conversation

@RafaelGSS
Copy link
Member

cc: @nodejs/nodejs-website @nodejs/releasers @nodejs/security-release

I tried to create the CHANGELOGs for all release lines as we normally do, but it doesn't respect the version passed on

node --run scripts:release-post x.y.z

In my case, it was always fetching v25.3.0 only. My understanding is that it should be created automatically, but I'm not sure if that's working.

@RafaelGSS RafaelGSS requested a review from a team as a code owner January 13, 2026 13:59
Copilot AI review requested due to automatic review settings January 13, 2026 13:59
@RafaelGSS RafaelGSS requested a review from a team as a code owner January 13, 2026 13:59
@vercel
Copy link

vercel bot commented Jan 13, 2026

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

Project Deployment Review Updated (UTC)
nodejs-org Ready Ready Preview Jan 13, 2026 2:07pm

@github-actions
Copy link
Contributor

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/nodejs-website @nodejs/web-infra

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

@RafaelGSS
Copy link
Member Author

By the way, I have not renamed december-2025-security-releases to january-2026 because people will have broken links in case they are refreshing the page waiting for updates.

Copy link
Contributor

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 updates the Node.js website to announce the January 13, 2026 security release, replacing the previously announced postponement notices with the actual release details. The security release addresses 8 vulnerabilities across multiple severity levels affecting Node.js versions 20.x through 25.x.

Changes:

  • Updated website banner to announce security release availability instead of pre-release notification
  • Replaced postponement notices with full vulnerability disclosures including CVE details, descriptions, impacts, and acknowledgments
  • Added links to release downloads for affected Node.js versions (v20.19.7, v22.21.2, v24.12.1, v25.2.2)

Reviewed changes

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

File Description
apps/site/site.json Updated banner configuration to change dates and announcement text for the security release
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md Replaced postponement announcements with comprehensive security vulnerability disclosures and release information

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

RafaelGSS and others added 2 commits January 13, 2026 11:04
…eleases.md

Co-authored-by: Copilot <[email protected]>
Signed-off-by: Rafael Gonzaga <[email protected]>
…eleases.md

Co-authored-by: Copilot <[email protected]>
Signed-off-by: Rafael Gonzaga <[email protected]>
@RafaelGSS RafaelGSS added the github_actions:pull-request Trigger Pull Request Checks label Jan 13, 2026
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jan 13, 2026
@github-actions
Copy link
Contributor

📦 Build Size Comparison

Summary

Metric Value
Old Total Size 3.74 MB
New Total Size 3.74 MB
Delta -19.00 B (-0.00%)

Changes

➕ Added Assets (1)
Name Size
.next/static/chunks/d6c41d23b20f53e2.js 204.36 KB
➖ Removed Assets (1)
Name Size
.next/static/chunks/2dca7fe1a056db5e.js 204.38 KB

@avivkeller
Copy link
Member

avivkeller commented Jan 13, 2026

In my case, it was always fetching v25.3.0 only. My understanding is that it should be created automatically, but I'm not sure if that's working.

It did, see the automatic PRs created. It marked you as assignee

@github-actions
Copy link
Contributor

github-actions bot commented Jan 13, 2026

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 99 🟢 96 🟢 100 🟢 100 🔗
/en/about 🟢 99 🟢 97 🟢 100 🟠 88 🔗
/en/about/previous-releases 🟢 98 🟢 100 🟢 100 🟢 100 🔗
/en/download 🟢 98 🟢 100 🟢 96 🟢 100 🔗
/en/download/archive/current 🟢 99 🟢 100 🟢 96 🟢 100 🔗
/en/blog 🟢 99 🟢 100 🟢 96 🟢 100 🔗

@codecov
Copy link

codecov bot commented Jan 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.00%. Comparing base (3dff177) to head (d536004).
⚠️ Report is 4 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8538   +/-   ##
=======================================
  Coverage   75.00%   75.00%           
=======================================
  Files         103      103           
  Lines        9036     9036           
  Branches      311      311           
=======================================
  Hits         6777     6777           
  Misses       2257     2257           
  Partials        2        2           

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

@avivkeller avivkeller merged commit 632645e into main Jan 13, 2026
16 checks passed
@avivkeller avivkeller deleted the add-security-release-jan13 branch January 13, 2026 14:12
Comment on lines +150 to +153
- [Node.js v20.19.7](/blog/release/v20.19.7/)
- [Node.js v22.21.2](/blog/release/v22.21.2/)
- [Node.js v24.12.1](/blog/release/v24.12.1/)
- [Node.js v25.2.2](/blog/release/v25.2.2/)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- [Node.js v20.19.7](/blog/release/v20.19.7/)
- [Node.js v22.21.2](/blog/release/v22.21.2/)
- [Node.js v24.12.1](/blog/release/v24.12.1/)
- [Node.js v25.2.2](/blog/release/v25.2.2/)
- [Node.js 20.19.7](/blog/release/v20.19.7/)
- [Node.js 22.21.2](/blog/release/v22.21.2/)
- [Node.js 24.12.1](/blog/release/v24.12.1/)
- [Node.js 25.2.2](/blog/release/v25.2.2/)

Per #8520?

Copy link
Member

Choose a reason for hiding this comment

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

cc @aduh95 might need some more comms around following these guidelines everywhere? Or a lint rule to ban it?

@mex
Copy link

mex commented Jan 13, 2026

Are the versions included here wrong? It looks like they all link to 404 pages and the new releases today are minor bumps, not patch bumps.

Edit: Fixed in #8540

@MattIPv4
Copy link
Member

Yes, would appear so, workflow gremlins. Being addressed in #8540

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.

5 participants