fix: switch npm publish to OIDC trusted publishing#638
Merged
kovtcharov merged 2 commits intomainfrom Mar 27, 2026
Merged
Conversation
…1-rc.1 - Remove NPM_TOKEN secret, use OIDC provenance instead - Bump Node to 22 for npm 11.5.1+ (required for trusted publishing) - Bump version to 0.17.1-rc.1 to test trusted publishing pipeline
Without --refresh, uv uses a cached package index which may not include recently published versions, causing install failures for new users running gaia-ui right after a release.
kovtcharov-amd
approved these changes
Mar 27, 2026
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Mar 27, 2026
## Summary - Remove `registry-url` from `setup-node` in the publish workflow - `setup-node` with `registry-url` creates an `.npmrc` that sets `NODE_AUTH_TOKEN`, which overrides OIDC authentication and causes E404 on trusted publishing ## Context Follow-up to #638. Trusted publishing was configured but npm publish kept failing with E404 because the `.npmrc` token was taking precedence over OIDC.
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
2 participants
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.
Summary
NPM_TOKENsecret, use OIDC trusted publishing instead0.17.1-rc.1to test trusted publishing pipelineContext
The npm publish workflow was failing with E403 because it required 2FA/OTP. Trusted publishing via OIDC eliminates the need for stored tokens entirely — GitHub Actions authenticates directly with npm using short-lived OIDC credentials.
Trusted publisher has been configured on npmjs.com for this workflow + environment.
Test plan
v0.17.1-rc.1and push to trigger the publish workflow@amd-gaia/agent-ui@0.17.1-rc.1appears on npm