Skip to content

Conversation

@RafaelGSS
Copy link
Member

cc: @nodejs/tsc

Co-Authored-By: Antoine du Hamel <[email protected]>
Co-Authored-By: Richard Lau <[email protected]>
Co-Authored-By: Matteo Collina <[email protected]>
@RafaelGSS RafaelGSS requested a review from a team as a code owner April 17, 2025 16:04
@vercel
Copy link

vercel bot commented Apr 17, 2025

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

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Apr 23, 2025 2:26pm

@avivkeller
Copy link
Member

FYI for Node.js Website Team (Unrelated to contents of this PR):
https://nodejs-org-git-security-incident-update-openjs.vercel.app/en/feed/vulnerability.xml shows #7648 in action

@github-actions
Copy link
Contributor

github-actions bot commented Apr 17, 2025

Lighthouse Results

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

@codecov-commenter
Copy link

codecov-commenter commented Apr 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@d9c0508). Learn more about missing BASE report.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7658   +/-   ##
=======================================
  Coverage        ?   74.61%           
=======================================
  Files           ?       96           
  Lines           ?     7689           
  Branches        ?      192           
=======================================
  Hits            ?     5737           
  Misses          ?     1950           
  Partials        ?        2           

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

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@RafaelGSS
Copy link
Member Author

FYI, I might not be available next week. Feel free to merge this PR on Monday.

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

I need to send some edit, will do asap.

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

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

LGTM

@mcollina
Copy link
Member

@nodejs/nodejs-website can someone help me sorting out the linting here? This is exactly like we want it.

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

lgtm

@avivkeller
Copy link
Member

@nodejs/nodejs-website can someone help me sorting out the linting here?

You need to run npm format.

This is exactly like we want it.

What does npm format do that isn't acceptable?

@mcollina
Copy link
Member

@node-core/website:lint: @node-core/website:lint:md: cache hit, replaying logs c9d8947053a45b98
@node-core/website:lint: @node-core/website:lint:md:
@node-core/website:lint: @node-core/website:lint:md:
@node-core/website:lint: @node-core/website:lint:md: > lint:md
@node-core/website:lint: @node-core/website:lint:md: > eslint "**/*.md?(x)" --cache --cache-strategy=content --cache-location=.eslintmdcache
@node-core/website:lint: @node-core/website:lint:md:
@node-core/website:lint:
@node-core/website:lint: @node-core/website:lint:md: /Users/matteo/repos/nodejs.org/apps/site/pages/en/blog/vulnerability/march-2025-ci-incident.md
@node-core/website:lint: @node-core/website:lint:md:   70:1  warning  {"reason":"Unexpected duplicate toplevel heading, exected a single heading with rank `1`","source"@node-core/website:lint: no-multiple-toplevel-headings","severity":1}  mdx/remark
@node-core/website:lint: @node-core/website:lint:md:
@node-core/website:lint: @node-core/website:lint:md: ✖ 1 problem (0 errors, 1 warning)
@node-core/website:lint: @node-core/website:lint:md:   0 errors and 1 warning potentially fixable with the `--fix` option.
@node-core/website:lint: @node-core/website:lint:md:

Note that the content is correct.

@avivkeller
Copy link
Member

avivkeller commented Apr 23, 2025

Can you run prettier on the content? The ESLint issue is just a warning, and wouldn't fail the quality checks

Signed-off-by: Matteo Collina <[email protected]>
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

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

lgtm

@avivkeller avivkeller added the github_actions:pull-request Trigger Pull Request Checks label Apr 23, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Apr 23, 2025
@aduh95 aduh95 added this pull request to the merge queue Apr 23, 2025
Merged via the queue into main with commit 0b24039 Apr 23, 2025
16 checks passed
@aduh95 aduh95 deleted the security-incident-update branch April 23, 2025 15:31
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.