fix(ci): force OIDC-only npm publish path#9
Merged
stevenobiajulu merged 1 commit intomainfrom Feb 25, 2026
Merged
Conversation
Release publish was falling back to token auth and failing with expired/revoked token errors despite trusted publishers being configured.\n\nMake trusted publishing the primary and only publish path by removing setup-node registry auth wiring and explicitly clearing NODE_AUTH_TOKEN/_authToken before npm publish. This prevents token fallback and keeps publish on OIDC + provenance.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
stevenobiajulu
added a commit
that referenced
this pull request
Feb 25, 2026
Trusted publishing with npm now requires a Node 22.14+ runtime. The release jobs were running on Node 20, so npm did not enter OIDC trusted-publishing mode and failed with ENEEDAUTH (interactive auth required).\n\nThis updates all release workflow jobs to Node 22 so the publish step can use OIDC provenance instead of manual npm login.\n\nRef: #9
stevenobiajulu
added a commit
that referenced
this pull request
Feb 25, 2026
) Trusted publishing with npm now requires a Node 22.14+ runtime. The release jobs were running on Node 20, so npm did not enter OIDC trusted-publishing mode and failed with ENEEDAUTH (interactive auth required).\n\nThis updates all release workflow jobs to Node 22 so the publish step can use OIDC provenance instead of manual npm login.\n\nRef: #9
stevenobiajulu
added a commit
that referenced
this pull request
Feb 25, 2026
Even with Node 22 and id-token permissions, npm publish was failing in release with ENEEDAUTH, meaning trusted publishing was not being engaged.\n\nsetup-node's registry-url configuration is part of npm's recommended trusted publishing setup. This restores registry-url in all release jobs while keeping token cleanup to avoid stale token fallback.\n\nRef: #9
stevenobiajulu
added a commit
that referenced
this pull request
Feb 25, 2026
Even with Node 22 and id-token permissions, npm publish was failing in release with ENEEDAUTH, meaning trusted publishing was not being engaged.\n\nsetup-node's registry-url configuration is part of npm's recommended trusted publishing setup. This restores registry-url in all release jobs while keeping token cleanup to avoid stale token fallback.\n\nRef: #9
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.
Summary
Why
Release publish was failing with token-style auth errors (expired/revoked token path), even though trusted publishing was configured. This change prevents fallback to token auth so npm uses OIDC consistently.
Validation