From 66635f3fe7d2d061b52b39b02dfbecd1c0971647 Mon Sep 17 00:00:00 2001 From: shrinishLT Date: Sun, 30 Aug 2026 12:09:10 +0530 Subject: [PATCH] fix(ci): pin pnpm@9 to unblock publish The v4.1.80 publish failed with ERR_PNPM_IGNORED_BUILDS. release.yaml installs pnpm unpinned (npm install -g pnpm), so it picked up pnpm 10, which turned ignored build scripts from a warning into a hard error. v4.1.79 published fine on Aug 10; pnpm 10 landed in between, so the next publish was going to fail whoever cut it. Pin pnpm@9: the version that generated the committed lockfile (lockfileVersion 9.0) and produced every successful publish to date. The five blocked packages (sharp, esbuild, the three @playwright/browser-*) all need their postinstall scripts, and pnpm 9 runs them by default. Deliberately not adding pnpm.onlyBuiltDependencies: once that allowlist exists, pnpm 10 silently skips scripts for any package not listed, so a future dependency needing one would break quietly instead of failing loudly as it did here. Co-Authored-By: Claude Opus 5 (1M context) --- .github/workflows/release.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml index e10f80bd..983d575f 100644 --- a/.github/workflows/release.yaml +++ b/.github/workflows/release.yaml @@ -22,7 +22,7 @@ jobs: run: rm -rf pnpm-lock.yaml - name: Install pnpm - run: npm install -g pnpm + run: npm install -g pnpm@9 - name: Install dependencies run: pnpm install