ci(release): fix oidc authentication for npm trusted publishing #26
Conversation
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
- remove manual npmrc token configuration (rely on setup-node oidc) - update node.js to version 20 for better npm oidc support - add npm update step to ensure oidc and provenance support - add NPM_CONFIG_ACCESS env var to force public access on first publish - add workflow_dispatch for manual testing - update comments to clarify oidc authentication flow this fixes the 404 error by properly using oidc tokens minted automatically by setup-node instead of manual token configuration.
itsjdubois
approved these changes
Nov 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes the 404 error by properly using oidc tokens minted automatically by setup-node instead of manual token configuration.