feat(meta): publish @node-core/* packages

[avivkeller]

The current vote on importing @node-core/* into api-docs-tooling stands at 8/0/0 in favor of publishing the @node-core/* packages. Given the lack of opposition in broader discussions, this outcome is unlikely to change.

As a result, this PR publishes the following packages to the npm registry:

• @node-core/ui-components
• @node-core/website-i18n
• @node-core/rehype-shiki
• Any future packages in the packages/ directory

These packages will be published on any commit that modifies their directories, provided the following conditions are met:

• The commit passes the "Linting and Tests" check on push to main, or the workflow is manually triggered.
• The commit was merged via the queue (i.e., not force-pushed to main).

Publishing requires a publish secrets.NPM_TOKEN for the @node-core scope, similar to the one used for Caritat.

[vercel]

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

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	May 26, 2025 1:47pm

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.34%. Comparing base (39e3ae1) to head (8572965).
Report is 2 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7776      +/-   ##
==========================================
+ Coverage   75.31%   75.34%   +0.02%     
==========================================
  Files          96       96              
  Lines        7856     7861       +5     
  Branches      192      192              
==========================================
+ Hits         5917     5923       +6     
+ Misses       1938     1937       -1     
  Partials        1        1              

☔ 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.

[Copilot]

Pull Request Overview

This PR adds a GitHub Actions workflow to automatically detect, verify, and publish any @node-core/* packages in the packages/ directory when changes are merged to main or manually triggered.

• Introduces .github/workflows/publish-packages.yml
• Detects which packages changed (or a specific package via input)
• Verifies commit authenticity and merge-queue origin before publishing via pnpm

Comments suppressed due to low confidence (1)

.github/workflows/publish-packages.yml:38

• [nitpick] Parsing ls output can break on directories with spaces or unexpected files. Consider using find packages -maxdepth 1 -type d -printf '%f\n' or verifying each folder contains a package.json.

PACKAGES=$(ls -d packages/* | xargs -n 1 basename | jq -R -s -c 'split("\n")[:-1]')

[AugustinMauroy]

we should add doc about

• how to release as collaborator
• why release package on npm registry

[avivkeller]

I've updated the PR with:

• More comments on the workflow
• A slack notification on manual publish
• Docs

[AugustinMauroy]

we need a npm token ?

[avivkeller]

Publishing requires a publish secrets.NPM_TOKEN for the @node-core scope, similar to the one used for Caritat.

[ovflowd]

LGTM

[ovflowd]

I've opened this issue: nodejs/admin#971

And thanks, @avivkeller for the work here <3

[github-actions]

Lighthouse Results

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