Skip to content

ci(release): add npm whoami verification before build#13

Merged
leefanv merged 1 commit into
mainfrom
ci/release-whoami
May 11, 2026
Merged

ci(release): add npm whoami verification before build#13
leefanv merged 1 commit into
mainfrom
ci/release-whoami

Conversation

@leefanv
Copy link
Copy Markdown
Owner

@leefanv leefanv commented May 11, 2026

Adds a one-step `npm whoami` check right after install. Catches three NPM_TOKEN failure modes early:

  • secret never set → explicit `::error::` with setup hint
  • token expired / revoked → 401/403 from registry
  • token wrong scope → 403

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

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>
@leefanv leefanv merged commit 35d01ea into main May 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant