Skip to content

Commit c549c7d

Browse files
committed
ci: use node 24 to enable npm trusted publishing
npm trusted publishing requires npm >= 11.5.1. Node 22 bundles npm 10, which never attempts the OIDC exchange, so the publish ran unauthenticated and the registry answered 404 on PUT. Node 24 bundles npm 11. Provenance is generated automatically under trusted publishing, so --provenance is no longer needed.
1 parent 01619f3 commit c549c7d

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎.github/workflows/release.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ jobs:
2626
- name: Setup Node
2727
uses: actions/setup-node@v4
2828
with:
29-
node-version: 22
29+
node-version: 24
3030
cache: "pnpm"
3131
registry-url: "https://registry.npmjs.org"
3232

@@ -48,4 +48,4 @@ jobs:
4848
- name: Publish to npm
4949
run: |
5050
node -e "const p=require('./package.json'); delete p.packageManager; if(p.devEngines) delete p.devEngines.packageManager; require('fs').writeFileSync('package.json', JSON.stringify(p, null, 2))"
51-
npm publish --provenance --access public
51+
npm publish --access public

0 commit comments

Comments
 (0)