fix: remove conflicting NPM_TOKEN from Trusted Publishing workflow #25
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
id-token: writefor Trusted Publishing (OIDC), which conflicts with legacy token authenticationRoot Cause
When both Trusted Publishing (
id-token: write) and legacy token authentication (NPM_TOKEN) are configured, npm authentication fails with "ENEEDAUTH" error.Solution
Remove the
NPM_TOKENenvironment variable to use only Trusted Publishing for secure, token-free npm publishing.Test Plan
Related Issues
Fixes the npm publishing failure that started after PR #21 was merged.