fix: use pnpm publish instead of npm to prevent ENEEDAUTH#25
Merged
Conversation
pnpm was already handling all package operations (install, build, test). Switching the publish step from npm to pnpm ensures consistent registry and auth configuration throughout the workflow. npm's OIDC flow can fail when pnpm has written registry config that npm then misinterprets. Using pnpm publish avoids this auth state collision and leverages pnpm's native --provenance and OIDC support. Also add --no-git-checks to allow publishing after version commit. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
yltw27
requested review from
djslimbo,
horlaarsco and
matt-koevort
and removed request for
a team
djslimbo
approved these changes
Apr 14, 2026
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
The publish step was failing with ENEEDAUTH because npm and pnpm have conflicting auth configurations. pnpm handles all earlier workflow steps (install, build, test), but switching to
npm publishcauses npm to pick up stale or empty auth tokens written by pnpm, preventing OIDC from working.Changes
npm publishtopnpm publishin the CI workflow--no-git-checksflag to allow publishing after the version commitWhy this fixes it
pnpm's native OIDC support works without interference from npm's auth resolution. By staying in pnpm, we avoid the auth state collision where npm tries to use an empty/stale token instead of falling through to OIDC trusted publishing.
🤖 Generated with Claude Code