Add March 2025 CI incident blog post #7588
Merged
Conversation
This file contains 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
Signed-off-by: Matteo Collina <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Pull Request Overview
A new blog post is added to the Node.js website reporting a CI security incident.
- Introduces a markdown file containing the blog content
- Describes the incident with metadata including date, category, title, and author
Comments suppressed due to low confidence (1)
apps/site/pages/en/blog/vulnerability/march-2025-ci-incident.md:4
- [nitpick] The title includes the word 'Test' which might be unintentional; confirm whether this is a placeholder or should be updated to correctly reflect the incident.
title: Node.js Test CI Security Incident
apps/site/pages/en/blog/vulnerability/march-2025-ci-incident.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Copilot <[email protected]> Signed-off-by: Matteo Collina <[email protected]>
avivkeller
approved these changes
Mar 31, 2025
github-actions
bot
removed
the
github_actions:pull-request
|
Lighthouse Results
|
Unit Test Coverage Report
|
|
@mcollina does this require a banner? If not, merge at will. |
bjohansebas
approved these changes
Mar 31, 2025
bjohansebas
approved these changes
Mar 31, 2025
BridgeAR
approved these changes
Mar 31, 2025
MattIPv4
reviewed
Mar 31, 2025
|
|
||
| The reported issue did not impact the Node.js runtime and there is no risk to users of Node.js. No action by Node.js users is required. | ||
|
|
||
| The development infrastructure is expected to be available to the community by April 15 or sooner. |
There was a problem hiding this comment.
Suggested change
| The development infrastructure is expected to be available to the community by April 15 or sooner. | |
| The development infrastructure is expected to be available to the community by April 15th or sooner. |
MattIPv4
approved these changes
Mar 31, 2025
ljharb
approved these changes
Mar 31, 2025
anonrig
approved these changes
Mar 31, 2025
RafaelGSS
approved these changes
Mar 31, 2025
flakey5
approved these changes
Mar 31, 2025
UlisesGascon
approved these changes
Mar 31, 2025
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.
as discussed with the @nodejs/tsc in private.
See https://github.com/nodejs/moderation/issues/830 (🔏Private repository)