ci(release): add npm whoami verification before build#13
Merged
Conversation
Surfaces NPM_TOKEN problems early instead of waiting for the first real publish to fail. Three failure modes the new step catches: - NPM_TOKEN secret never set → explicit ::error:: with setup hint - Token expired / revoked → npm whoami returns 401/403 - Token wrong scope → npm whoami returns 403 No-op when everything's healthy (1 line of log). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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.
Adds a one-step `npm whoami` check right after install. Catches three NPM_TOKEN failure modes early:
On healthy auth it logs one line:
```
✓ npm authenticated as: seergb
```
After merging this PR, you can manually dispatch the workflow (Actions → Release → Run workflow) to verify your newly-added NPM_TOKEN is valid. With everything currently tagged, the publish step will skip all 6 packages — the only thing being tested is auth.
🤖 Generated with Claude Code