Skip to content

ci(release): drop registry-url so npm uses OIDC trusted publishing #853

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
Aymericr merged 1 commit into from
Sep 11, 2026
Merged

ci(release): drop registry-url so npm uses OIDC trusted publishing #853

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
6 changes: 5 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,10 +77,14 @@ jobs:
with:
bun-version: 1.3.14

# No registry-url here: with it, actions/setup-node writes an .npmrc whose
# auth token falls back to the placeholder XXXXX-XXXXX-XXXXX-XXXXX, npm
# sends that fake token, the registry answers 404, and the OIDC trusted
# publishing exchange never runs. npm publishes to registry.npmjs.org by
# default and each publish step passes --access public explicitly.
- uses: actions/setup-node@v4
with:
node-version: 22
registry-url: "https://registry.npmjs.org"

# npm refuses direct publishing with 2FA-bypass tokens (EOTP, see
# https://gh.io/npm-gat-bypass2fa-deprecation), so no NODE_AUTH_TOKEN is set
Expand Down
Loading