From 6d15d7c4e0d17da6000c3edf534ab6d5f86d9411 Mon Sep 17 00:00:00 2001 From: Murph Murphy Date: Fri, 16 Oct 2026 15:41:09 -0600 Subject: [PATCH] Drop registry-url from typescript-release's setup-node setup-node v7 no longer exports a placeholder NODE_AUTH_TOKEN, so the .npmrc it writes for registry-url leaves ${NODE_AUTH_TOKEN} unresolved and yarn v1 fails before install. npm Trusted Publishing uses the default registry and needs no .npmrc. --- .github/workflows/typescript-release.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/typescript-release.yaml b/.github/workflows/typescript-release.yaml index ab0a94b..031510b 100644 --- a/.github/workflows/typescript-release.yaml +++ b/.github/workflows/typescript-release.yaml @@ -35,10 +35,11 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v7 + # No registry-url: its .npmrc references ${NODE_AUTH_TOKEN}, which setup-node v7 leaves unset + # and yarn v1 rejects. Trusted Publishing needs no .npmrc. - uses: actions/setup-node@v7 with: node-version: ${{ inputs.node_version }} - registry-url: "https://registry.npmjs.org" # Need newer npm to use Trusted Publishing - name: Use newer npm version run: |