feat(actions): publish @node-core/ui-components

[avivkeller]

It's hard to properly test this, as it makes use of GitHub tokens, but based on my testing of each step independently, this'll publish the @node-core/ui-components package.

This PR publishes `@node-core/ui-components to the GitHub registry. Before merging, we need to verify that we have access to this scope.

For security reasons, several checks are in place to prevent malicious execution:

• The commit must've passed all checks on main's Linting and Tests workflow, and that check must've been triggered by a push event to main, or the workflow was manually dispatched
• The commit must be verified.
• Unless explicitly specified in the workflow_dispatch event, the commit must come from the merge queue.
  • i.e. a push directly to main will not be published automatically

Additionally, the commit must've modified something in packages/ui-components.

---

Ref: #7401
Closes nodejs/api-docs-tooling#236

[vercel]

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

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Mar 24, 2025 11:08pm

[Copilot]

Pull Request Overview

This pull request adds a new GitHub Actions workflow to publish the @node-core/ui-components package after successful tests and additional security validations. Key changes include:

• Triggering the workflow via a completed Linting and Tests workflow or by workflow_dispatch.
• Introducing commit authenticity checks to enforce verified commit and authorized committer requirements.
• Setting up Node.js, generating versions using the commit SHA, and publishing the package if changes occur in the packages/ui-components directory.

[github-actions]

Lighthouse Results

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

[github-actions]

Unit Test Coverage Report

Title	Lines	Statements	Branches	Functions
@node-core/ui-components		95.83% (161/168)	77.86% (102/131)	88.57% (31/35)
@nodejs/website		84.74% (500/590)	76.03% (165/217)	87.09% (108/124)

Title	Tests	Skipped	Failures	Errors	Time
@node-core/ui-components	24	0 💤	0 ❌	0 🔥	4.895s ⏱️
@nodejs/website	157	0 💤	0 ❌	0 🔥	6.527s ⏱️

[AugustinMauroy]

I didn't get if you are trying to publish it npm registry or GitHub packages

[avivkeller]

I didn't get if you are trying to publish it npm registry or GitHub packages

We are publishing to GitHub Packages.

[avivkeller]

We don't control the @node-core scope on Github Packages, see nodejs/api-docs-tooling#236 (comment)

[avivkeller]

Per discussion in other thread