Skip to content

ci: upgrade npm in publish step — OIDC trusted publishing needs npm >= 11.5 #5

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
Acro merged 1 commit into from
Jul 12, 2026
Merged

ci: upgrade npm in publish step — OIDC trusted publishing needs npm >= 11.5 #5

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
9 changes: 8 additions & 1 deletion .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,13 @@ jobs:
node --unhandled-rejections=strict smoke.mjs

- name: Publish with provenance
run: npm publish --provenance --access public
# npm >= 11.5 is required for OIDC trusted publishing (the "connect a
# GitHub repo" flow on npmjs.com); Node 22 ships npm 10.x. With a
# trusted publisher configured, no token is needed — OIDC takes
# precedence. A classic NPM_TOKEN secret keeps working as a fallback.
run: |
npm install -g npm@latest
npm --version
npm publish --provenance --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
Loading