From 4f0ec077013735c639c6bb038ff09bc3aacc0f1d Mon Sep 17 00:00:00 2001 From: Junyi Ou Date: Thu, 18 Jun 2026 12:10:20 -0400 Subject: [PATCH] ci(publish-libraries): fix NODE_AUTH_TOKEN workaround for PowerShell The OIDC workaround from #1636 used bash-style inline env assignment (`NODE_AUTH_TOKEN="" npm publish`), but the step runs under pwsh, which parses `NODE_AUTH_TOKEN=` as a command name -> CommandNotFoundException. Set the env var the PowerShell way instead. This path was never exercised until web-recorder@0.1.0 (the first new package version since #1636), so the latent bug only surfaced now. --- ci/npm-publish.ps1 | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ci/npm-publish.ps1 b/ci/npm-publish.ps1 index 64e165115..df63606f1 100755 --- a/ci/npm-publish.ps1 +++ b/ci/npm-publish.ps1 @@ -35,7 +35,9 @@ try else { Write-Host "Publishing..." - NODE_AUTH_TOKEN="" npm publish "$Tarball" "--access=$Access" # NODE_AUTH_TOKEN is a workaround for https://github.com/actions/setup-node/issues/1440 + # Reset NODE_AUTH_TOKEN to empty is a workaround for https://github.com/actions/setup-node/issues/1440 (OIDC trusted publishing) + $env:NODE_AUTH_TOKEN = "" + npm publish "$Tarball" "--access=$Access" } } finally