[DOCS] improve trusted publishing docs for easier github ci migration

[gitcommitshow]

Is there an existing issue for this?

• I have searched the existing issues

This is a CLI Docs Enhancement, not another kind of Docs Enhancement.

• This is a CLI Docs Enhancement.

Description of Problem

I wasted a lot of time on migrating my github action (for npm publish) to trusted publishing due to gaps in trusted publishing docs and the bug #8730

This was the exact issue and the solution - gitcommitshow/resilient-llm#39

Potential Solution

Following improvements can save time and frustration for others

• Add the node v24 as mandatory requirement in the github action. Could not discover this until I saw comments on [BUG] OIDC publish failing from GitHub actions #8730
• Highlight where to find the trusted publishing, include visual guide. I had hard time finding this.
• A clear destination to report issues. I could not find this info on the docs. I tried "contact npm" on the footer and waited for a day to get an answer. Then only I searched github for similar issue and could discover this page.

Docs URL

https://docs.npmjs.com/trusted-publishers#github-actions-configuration

[david-aldo-dalessandro]

Thanks for raising this. I ran into similar confusion reading through the trusted publishing docs.

I’d be happy to help with a small docs PR if this direction makes sense. Based on the discussion so far, I think the following clarifications could save time for others:

1. Explicitly note that Node v24 is required for trusted publishing with OIDC in GitHub Actions (the examples use v24, but it’s not called out as required).

2. Clarify where to find Trusted Publishing in the UI, e.g.
   npmjs.com → Packages → → Settings → Trusted publishing, possibly with a short visual or breadcrumb.

3. Add a short “Reporting issues” note pointing users to GitHub Issues for trusted publishing / OIDC problems, so users don’t default to “Contact npm” when they hit CI failures.

Before opening a PR, could you confirm:

Which repo these docs should be updated in (npm/cli vs another docs repo)?

Whether these changes belong in the existing trusted publishing docs, or if there’s a preferred location/structure?

Happy to take a first pass if that helps.