Skip to content

Publish to npm with trusted publishing - #60

Merged
yusuftor merged 1 commit into
masterfrom
ci/npm-trusted-publishing
Nov 3, 2026
Merged

yusuftor merged 1 commit into
masterfrom
ci/npm-trusted-publishing

Conversation

@yusuftor

@yusuftor yusuftor commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

The 1.0.17 npm publish failed with E404 because NPM_TOKEN no longer works, and npm is removing direct publishing with 2FA-bypass tokens in January 2027. This switches to trusted publishing, so GitHub Actions publishes without a stored token.

  • Grants the workflow id-token: write.
  • Updates npm before publishing (trusted publishing needs 11.5.1+; Node 20 ships 10.x).
  • Drops NODE_AUTH_TOKEN.
  • Adds repository to wasm/package.json, which npm checks against the publishing repo.

Before merging: add the trusted publisher on npmjs.com (@superwall/superscript → Settings → Trusted Publisher → GitHub Actions: superwall / superscript / build-test-publish-superscript-npm.yml). Merging publishes 1.0.17, since that version isn't on npm yet.

🤖 Generated with Claude Code

npm is removing direct publishing with 2FA-bypass tokens in January 2027,
and the stored NPM_TOKEN already fails (E404 on 1.0.17). Publish with
GitHub OIDC instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@yusuftor
yusuftor merged commit 9a9fcd6 into master Nov 3, 2026
2 checks 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