Skip to content

fix(release): pass npm token to publish#18

Merged
drewstone merged 1 commit into
mainfrom
fix/npm-publish-token-env
Jul 2, 2026
Merged

fix(release): pass npm token to publish#18
drewstone merged 1 commit into
mainfrom
fix/npm-publish-token-env

Conversation

@drewstone

Copy link
Copy Markdown
Contributor

Summary

  • bind the repo NPM_TOKEN secret to NODE_AUTH_TOKEN for the npm publish step
  • set the tangle-network/traces repo NPM_TOKEN secret from the validated local COMPANY_NPM_TOKEN

Diagnosis

  • Publish failed after typecheck/test/build at npm upload with E404
  • repo had no NPM_TOKEN secret before this fix
  • local COMPANY_NPM_TOKEN authenticates as drewstone and has read-write access to @tangle-network/traces

Verification

  • gh-drew secret list --repo tangle-network/traces shows NPM_TOKEN updated at 2026-07-02T05:10:41Z
  • npm whoami with COMPANY_NPM_TOKEN -> drewstone
  • npm access list packages @tangle-network includes @tangle-network/traces: read-write
  • pnpm typecheck
  • pnpm test
  • pnpm build
  • git merge-tree --write-tree origin/main HEAD

@tangletools tangletools left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved drewstone PR — 6984e74a

This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

tangletools · auto-approval · reason: drewstone_author · 2026-07-02T05:12:06Z

@drewstone drewstone merged commit 91a238e into main Jul 2, 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.

2 participants