Skip to content

ci(release-npm): preflight npm-auth check (loud-fail on bad/expired token) #342

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
avrabe merged 1 commit into from
May 30, 2026
Merged

ci(release-npm): preflight npm-auth check (loud-fail on bad/expired token) #342

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions .github/workflows/release-npm.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,23 @@ jobs:
node-version: "20"
registry-url: "https://registry.npmjs.org"

# Preflight: fail loud + early if NPM_TOKEN can't authenticate, instead
# of letting each per-package `npm publish` crash with a cryptic E404
# (expired/no-access) or EOTP (a classic *Publish* token, which the
# org's 2FA-on-publish rejects in CI). npm publish needs a classic
# *Automation* token or a granular token with read-write on
# @pulseengine/*. This turns a silently-frozen npm channel (it sat at
# 0.10.1 for ~6 releases) into an immediate, labeled failure.
- name: Preflight — verify npm auth
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
run: |
if ! who=$(npm whoami 2>/dev/null); then
echo "::error title=npm auth failed::NPM_TOKEN is invalid, expired, or the wrong type. npm publish needs a classic *Automation* token (or a granular token with read-write on @pulseengine/*); a classic *Publish* token fails under 2FA with EOTP. Regenerate at npmjs.com -> Access Tokens and update the NPM_TOKEN secret."
exit 1
fi
echo "npm auth OK as: $who"

- name: Resolve version
id: version
env:
Expand Down Expand Up @@ -153,6 +170,23 @@ jobs:
node-version: "20"
registry-url: "https://registry.npmjs.org"

# Preflight: fail loud + early if NPM_TOKEN can't authenticate, instead
# of letting each per-package `npm publish` crash with a cryptic E404
# (expired/no-access) or EOTP (a classic *Publish* token, which the
# org's 2FA-on-publish rejects in CI). npm publish needs a classic
# *Automation* token or a granular token with read-write on
# @pulseengine/*. This turns a silently-frozen npm channel (it sat at
# 0.10.1 for ~6 releases) into an immediate, labeled failure.
- name: Preflight — verify npm auth
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
run: |
if ! who=$(npm whoami 2>/dev/null); then
echo "::error title=npm auth failed::NPM_TOKEN is invalid, expired, or the wrong type. npm publish needs a classic *Automation* token (or a granular token with read-write on @pulseengine/*); a classic *Publish* token fails under 2FA with EOTP. Regenerate at npmjs.com -> Access Tokens and update the NPM_TOKEN secret."
exit 1
fi
echo "npm auth OK as: $who"

- name: Resolve version
id: version
env:
Expand Down
Loading