From 05007ca0dbfb553e73bc95c60520bd0f40557ee5 Mon Sep 17 00:00:00 2001 From: Oscar Watson-Smith Date: Mon, 13 Jul 2026 19:05:47 +1000 Subject: [PATCH] fix: restore registry-url so npm 12 has a registry context for OIDC Without registry-url npm never attempts the OIDC exchange and fails with ENEEDAUTH. npm's Trusted Publishing setup keeps registry-url and just omits the token; the empty-token concern was a red herring (the earlier 404 was a stale npm 10.x, now fixed by the separate upgrade step). --- .github/workflows/release.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index d7344ab..4975a27 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -19,6 +19,7 @@ jobs: - uses: actions/setup-node@v4 with: node-version: 22 + registry-url: https://registry.npmjs.org - run: bun install --frozen-lockfile - name: Verify the release tag matches package.json run: |