feat: update node.js unsafe versions for january 13 2026 security releases #284
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. Comment |
- Update Node.js 20.x to 20.20.0 (from 20.19.4) - Update Node.js 22.x to 22.22.0 (from 22.17.1) - Update Node.js 24.x to 24.13.0 (from 24.4.1) - Add Node.js 25.x at 25.3.0 - Remove Node.js v18.x (EOL on 2025-04-30) - Remove Node.js v23.x (not included in December 2025 security release) All changes reference: https://nodejs.org/en/blog/vulnerability/december-2025-security-releases Co-authored-by: fengmk2 <156269+fengmk2@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update Node.js to address December 2025 security releases
Update Node.js unsafe versions for December 2025 security releases
Jan 14, 2026
fengmk2
reviewed
Jan 14, 2026
Keep v18 and v23 entries as requested. - Update Node.js 20.x to 20.20.0 (from 20.19.4) - Update Node.js 22.x to 22.22.0 (from 22.17.1) - Update Node.js 24.x to 24.13.0 (from 24.4.1) - Add Node.js 25.x at 25.3.0 - Keep Node.js v18.x at 18.20.6 (January 2025 release) - Keep Node.js v23.x at 23.11.1 (May 2025 release) Reference: https://nodejs.org/en/blog/vulnerability/december-2025-security-releases Co-authored-by: fengmk2 <156269+fengmk2@users.noreply.github.com>
fengmk2
approved these changes
Jan 14, 2026
fengmk2
changed the title
fengmk2
changed the title
fengmk2
changed the title
|
🎉 This PR is included in version 1.119.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Node.js published security releases on December 15, 2025 for active release lines (20.x, 22.x, 24.x, 25.x).
Updated to secure versions:
20.19.4→20.20.022.17.1→22.22.024.4.1→24.13.025.3.0Preserved existing entries:
18.20.6(January 2025 release)23.11.1(May 2025 release)All updated entries reference: https://nodejs.org/en/blog/vulnerability/december-2025-security-releases
The repository maintains entries for all Node.js versions, including EOL versions, to ensure users are warned about unsafe versions regardless of which Node.js version they're using.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.