From 2175e10cd3febf83fc423b32aa0a17a9a1f139bc Mon Sep 17 00:00:00 2001 From: phall Date: Sun, 9 Aug 2026 13:27:23 -0400 Subject: [PATCH] fix(release): give the credential preflight a registry to authenticate against MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The preflight added in the previous commit failed with ENEEDAUTH rather than reporting the account, because the verify job's setup-node had no registry-url. That option is what writes the .npmrc containing the NODE_AUTH_TOKEN reference; without it the token sits in the environment and npm never reads it. The publish jobs already pass registry-url, so this only ever affected the diagnostic — but a diagnostic that cannot authenticate answers nothing. --- .github/workflows/fork-publish.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/fork-publish.yml b/.github/workflows/fork-publish.yml index 8f45d97..8171965 100644 --- a/.github/workflows/fork-publish.yml +++ b/.github/workflows/fork-publish.yml @@ -39,9 +39,14 @@ jobs: with: ref: ${{ inputs.tag || github.event.release.tag_name }} + # `registry-url` is what makes setup-node write the .npmrc that reads + # NODE_AUTH_TOKEN. Without it npm ignores the token entirely and every + # authenticated command fails with ENEEDAUTH, which is exactly what the + # credential preflight below hit the first time it ran. - uses: actions/setup-node@v6 with: node-version: 24 + registry-url: https://registry.npmjs.org/ - uses: oven-sh/setup-bun@v2