Skip to content

fix(ci): add environment: npm to wasm publish for Trusted Publishing #2239

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
douenergy merged 1 commit into from
May 5, 2026
+4 −6
Merged

fix(ci): add environment: npm to wasm publish for Trusted Publishing #2239

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: 4 additions & 6 deletions .github/workflows/publish-wren-core-wasm.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,9 @@ jobs:
build-and-publish:
name: Build WASM + publish to npm
runs-on: ubuntu-latest
# Required by the npm Trusted Publisher config (Environment name: npm).
# The 'npm' environment must exist under repo Settings → Environments.
environment: npm
permissions:
contents: read
id-token: write
Expand Down Expand Up @@ -58,13 +61,8 @@ jobs:
uses: actions/setup-node@v4
with:
# Trusted Publishing requires Node.js >= 22.14.0; pin to 24 (latest LTS line).
# Intentionally do NOT pass registry-url here: setup-node would auto-write
# an .npmrc containing
# //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
# always-auth=true
# which prevents npm from falling back to OIDC, so Trusted Publishing
# fails with a confusing 404 even when correctly configured on npm.
node-version: 24
registry-url: https://registry.npmjs.org

- name: Ensure npm meets Trusted Publishing requirement (>= 11.5.1)
run: npm install -g npm@latest
Expand Down
Loading