-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
Blog: add January 13 security release #8538
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
👋 Codeowner Review RequestThe 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! 🙏 |
|
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. |
There was a problem hiding this 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.
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
Show resolved
Hide resolved
…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]>
📦 Build Size ComparisonSummary
Changes➕ Added Assets (1)
➖ Removed Assets (1)
|
It did, see the automatic PRs created. It marked you as assignee |
|
Lighthouse Results
|
Codecov Report✅ All modified and coverable lines are covered by tests. 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. |
| - [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/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - [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?
There was a problem hiding this comment.
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?
|
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 |
|
Yes, would appear so, workflow gremlins. Being addressed in #8540 |
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
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.