From f900a81ec99f025758169360e8e8468886dfd81d Mon Sep 17 00:00:00 2001 From: diegosouzapw Date: Tue, 10 Mar 2026 09:48:35 -0300 Subject: [PATCH] fix(ci): use npm install in npm-publish to survive lock file drift on old tags MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit npm ci fails if the tag commit's lock file is out of sync (as happened with v2.2.0 when @swc/helpers was missing). npm install is safe here because the publish workflow only needs deps to run prepublish.mjs — strict lock enforcement is not required for the publish step. --- .github/workflows/npm-publish.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/npm-publish.yml b/.github/workflows/npm-publish.yml index 1089ad4ee8..14b08da04a 100644 --- a/.github/workflows/npm-publish.yml +++ b/.github/workflows/npm-publish.yml @@ -23,7 +23,7 @@ jobs: registry-url: https://registry.npmjs.org - name: Install dependencies (skip scripts to avoid heavy build) - run: npm ci --ignore-scripts + run: npm install --ignore-scripts --no-audit --no-fund - name: Sync version from release tag run: |