From c1f728658ac80cd3c008fd667bae6c68df6052a2 Mon Sep 17 00:00:00 2001 From: JeanExtreme002 Date: Fri, 9 Oct 2026 16:22:33 -0300 Subject: [PATCH] ci: validate the npm tarball with pack instead of a publish dry run Since npm 12, `npm publish --dry-run` checks the registry first and refuses a version that is already published. The publish job upgrades to npm@latest, so every workflow_dispatch rehearsal on a released version now fails at that step even though nothing is wrong with the package. `npm pack --dry-run` prints the same tarball listing without talking to the registry; the real publish still refuses a duplicate. --- .github/workflows/publish.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 82dfb7c..967f2e6 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -235,7 +235,7 @@ jobs: run: npm run test:offline - name: Validate package contents - run: npm publish --dry-run + run: npm pack --dry-run # publish --dry-run on npm 12 refuses an already-published version - name: Publish to npm if: github.event_name == 'release' || inputs.dry_run == false