Open
Conversation
outslept
commented
Sep 17, 2025
|
|
||
| # Upgrade npm for trusted publishing | ||
| - name: Setup npm for publishing | ||
| run: npm install -g npm@latest |
Author
There was a problem hiding this comment.
A possible alternative to npm install -g npm@latest might be to use node-version: 24, which provides npm 11.6.0 and therefore support for trusted publishing. This approach should also help prevent breaking changes creeping in, e.g. it won't introduce npm 12
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR edits your workflow to switch to Trusted Publishing. It lets your CI mint short‑lived OIDC ID tokens (permissions: id-token: write) that npm exchanges for publish credentials at runtime, eliminating the need for long‑lived npm tokens in CI. npm CLI 11.5.1+ is required for OIDC support.
Context:
https://github.blog/changelog/2025-07-31-npm-trusted-publishing-with-oidc-is-generally-available
https://docs.npmjs.com/trusted-publishers
e18e/ecosystem-issues#201
Also. If it is already not set, please switch the package's Publishing Access radio button to "Require two-factor authentication and disallow tokens".