Commit e3e313d
committed
Migrate npm publishing workflow to trusted publishing via OIDC
The npm package configuration is already prepared for trusted
publishing, so the release workflow should stop relying on long-
lived NPM tokens. This updates the GitHub Actions release job to
use OIDC permissions with direct `npm publish`, removes temporary
`.npmrc` token setup, and refreshes checkout/setup-node actions
while keeping the tag-driven release flow intact.
Constraint: npm trusted publishing validates the exact GitHub workflow filename and requires `id-token: write`
Constraint: Trusted publishing requires npm CLI support and a sufficiently new Node runtime in CI
Rejected: Keep token-based publish as fallback in the same workflow | defeats the security goal and complicates release diagnostics
Confidence: high
Scope-risk: narrow
Directive: Keep publish authentication tokenless in CI; if future installs need auth, use separate read-only credentials only for install steps
Tested: Release workflow file reviewed against npm trusted publisher requirements; local package/docs verification already green on the tagged candidate
Not-tested: GitHub Actions trusted publish end-to-end until the updated tag is pushed and the workflow runs1 parent 4e57997 commit e3e313d
1 file changed
Lines changed: 5 additions & 9 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
15 | | - | |
| 15 | + | |
16 | 16 | | |
17 | 17 | | |
18 | 18 | | |
19 | 19 | | |
20 | | - | |
| 20 | + | |
21 | 21 | | |
22 | | - | |
| 22 | + | |
23 | 23 | | |
24 | 24 | | |
25 | 25 | | |
| |||
36 | 36 | | |
37 | 37 | | |
38 | 38 | | |
39 | | - | |
40 | | - | |
41 | | - | |
42 | | - | |
43 | | - | |
44 | 39 | | |
45 | | - | |
| 40 | + | |
| 41 | + | |
46 | 42 | | |
47 | 43 | | |
48 | 44 | | |
| |||
0 commit comments