Commit 699393e
ci(deps): use pnpm 11 allowBuilds map to approve esbuild + core-js
Context: commit 82aeaba tried to fix the pnpm 11 ERR_PNPM_IGNORED_BUILDS
CI failure by adding `onlyBuiltDependencies` to pnpm-workspace.yaml. That
fix passed a local check but CI still failed (run 26726781987) with the
same error.
Problem: `onlyBuiltDependencies` (the pnpm 10 list field) was REMOVED in
pnpm 11, which the bumped packageManager pin now installs. pnpm 11
ignores the unknown key and the build-script gate stays unsatisfied, so
esbuild@0.27.3 and core-js@3.49.0 are still flagged and the install
aborts. The earlier local verification was a false positive: it ran
against a populated node_modules, so pnpm reported "Already up to date"
and never evaluated build scripts at all.
Solution: replace `onlyBuiltDependencies` with pnpm 11's `allowBuilds`
map, marking esbuild and core-js as `true`.
Behavior: verified against a clean tree (rm -rf node_modules) with
`CI=true pnpm install --frozen-lockfile` -> exit 0, zero
ERR_PNPM_IGNORED_BUILDS, and esbuild's binary builds and runs
(`esbuild --version` -> 0.27.3). The same clean-install command on the
prior commit reproduced the CI failure (exit 1).
Files:
- pnpm-workspace.yaml:23-32 swap onlyBuiltDependencies list for the
allowBuilds map (esbuild: true, core-js: true)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>1 parent 677d29e commit 699393e
1 file changed
Lines changed: 7 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
24 | | - | |
25 | | - | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | | - | |
32 | | - | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
33 | 30 | | |
34 | | - | |
35 | 31 | | |
| 32 | + | |
0 commit comments