Skip to content

Let npm use trusted publishing in CI #62

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
yusuftor merged 1 commit into from
Nov 3, 2026
Merged

Let npm use trusted publishing in CI #62

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
10 changes: 6 additions & 4 deletions .github/workflows/build-test-publish-superscript-npm.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,10 +24,12 @@ jobs:
uses: actions/checkout@v3

- name: Setup Node.js
uses: actions/setup-node@v3
uses: actions/setup-node@v4
with:
node-version: '20'
registry-url: 'https://registry.npmjs.org'
# Trusted publishing needs Node 22.14+. No registry-url: it makes
# setup-node write an .npmrc with a placeholder token, which npm
# sends instead of using trusted publishing.
node-version: '22'
- name: Setup Bun
uses: oven-sh/setup-bun@v2

Expand Down Expand Up @@ -159,7 +161,7 @@ jobs:
- name: Publish to NPM
if: github.event_name == 'push' && github.ref == 'refs/heads/master'
run: |
# Trusted publishing needs npm 11.5.1 or later; npm 12 needs Node 22+.
# Trusted publishing needs npm 11.5.1 or later.
npm install -g npm@^11.5.1
cd wasm
# Try a normal publish first; if it fails (e.g. first-time publish of a
Expand Down
Loading