Commit 0319de4
fix(ci): drop registry-url from setup-node so OIDC trusted publishing works
The 1.1.0 release attempt — the first pure-OIDC publish after PR #11
dropped the bootstrap NPM_TOKEN — failed in
https://github.com/ylabonte/github-actions-updater/actions/runs/25931442199
inside changesets/action's `pnpm release` step.
`actions/setup-node` with `registry-url:` writes an `.npmrc` line
`//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}`. npm 11 sees a
configured token entry and skips the OIDC exchange; we don't set
NODE_AUTH_TOKEN (we want OIDC), so the resulting auth is empty and
`npm publish` 4xx's, which is what bubbled up as the pnpm exit 1.
Trusted publishing only kicks in with no token configured at all.
Default registry is the public one, so dropping `registry-url:` is
functionally a no-op for the registry pointer.
Refs:
- https://github.com/orgs/community/discussions/176761
- https://docs.npmjs.com/trusted-publishers/
Other release.yml polish items (rename `app-id` → `client-id` to silence
the v3 deprecation warning, pin pnpm/action-setup, pin `npm install -g`)
are intentionally out of scope — they are warnings, not the failure, and
client-id ≠ app-id so the rename needs a coordinated secret rotation.1 parent 2d8193e commit 0319de4
1 file changed
Lines changed: 7 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
38 | 45 | | |
39 | 46 | | |
40 | 47 | | |
41 | 48 | | |
42 | | - | |
43 | 49 | | |
44 | 50 | | |
45 | 51 | | |
| |||
0 commit comments