From 206d9f4ed8ece7188b633bb88f29604c7b97b7c7 Mon Sep 17 00:00:00 2001 From: Ahnaf An Nafee Date: Sat, 29 Aug 2026 20:53:24 -0400 Subject: [PATCH] fix(ci): avoid unresolved npm auth during cache setup setup-node v7 no longer provides a dummy NODE_AUTH_TOKEN when registry-url is configured. During Yarn Classic cache discovery, the generated npm configuration therefore contains an unresolved token placeholder and aborts the release job before dependency installation. Remove registry-url from the Node setup step because this workflow publishes VSIX artifacts through vsce and ovsx rather than npm. Yarn caching remains enabled without creating an unused authenticated npm configuration. The exact yarn cache dir reproduction failed before the change and passed afterward with NODE_AUTH_TOKEN unset. actionlint, frozen install, lint, the zero-finding dependency audit, and all 7 extension-host tests also passed. --- .github/workflows/release.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 306a40d..ef9b96a 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -18,7 +18,6 @@ jobs: with: node-version: 24 cache: "yarn" - registry-url: https://registry.npmjs.org/ - name: Install dependencies run: | npm install --global @vscode/vsce@3.9.2 ovsx@1.1.1