chore(workflow): upgrade npm CLI for trusted publishing OIDC support#154
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The 0.0.2 publish workflow run failed with 'error retrieving identity token' on @ngaf/licensing and @ngaf/partial-json, and a 404 on @ngaf/a2ui. Root cause: actions/setup-node@v6.3.0 with node-version: 22 ships npm 10.9.x, which has partial OIDC code paths but doesn't fully implement the trusted-publishing flow against npm registry's OIDC endpoint. Node 22 LTS will never ship npm 11+ (locked); Node 24 ships npm 11.6+ out of the box (verified via nodejs.org/dist/index.json). Bump only the publish workflow's Node version. The rest of CI (lint/test/build/e2e) stays on Node 22 — the publish workflow doesn't share artifacts with those, so the version drift is harmless. Sources: - https://philna.sh/blog/2026/01/28/trusted-publishing-npm/ - npm/cli#8730 - https://docs.npmjs.com/trusted-publishers/ Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
blove
force-pushed
the
chore/upgrade-npm-cli-for-trusted-publishing
branch
from
614cfd6 to
a109470
Compare
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.
Fixes the v0.0.2 publish workflow failure (run 25223696213).
Root cause
actions/setup-node@v6.3.0withnode-version: 22ships npm 10.9.2, which has partial OIDC code paths (enough to printerror retrieving identity token) but doesn't fully implement the trusted-publishing flow against npm registry's OIDC endpoint.npm 11.5.1+ is required for trusted publishing per npm docs.
Failure pattern observed
@ngaf/a2ui:404 Not Found - PUT https://registry.npmjs.org/@ngaf%2fa2ui@ngaf/licensing,@ngaf/partial-json:error retrieving identity tokenAll 7 packages have correct trusted-publisher configs on npmjs.com (verified manually); failure is npm CLI version, not config.
Fix
Adds
npm install -g npm@latestbetweennpm ciand the publish step.Next step after merge
Re-run the existing v0.0.2 publish workflow:
Sources
🤖 Generated with Claude Code