Commit 493544b
ci(publish-smoke): surface the app's resolved pnpm + build approvals before install (#3157)
The Publish Smoke gate died on ERR_PNPM_IGNORED_BUILDS with no way to see
why: the failure was CI-only and every local repro (pnpm 10.31/10.33)
honored the allowlist and exited 0.
The missing fact: the scaffolded app declares no packageManager field (by
design — it must test what a fresh user's pnpm resolves, not this repo's
pin), so with corepack enabled the `pnpm` that installs the app is the
LATEST pnpm (11.x), not the repo-pinned 10.31.0. pnpm 11 makes an
unapproved build script a hard error where pnpm 10 only warned. The app's
build approvals were declared for pnpm 11 in #3119; this adds the missing
visibility so a future red run answers on its own which pnpm ran and
whether it parsed the approvals.
Prints, from inside the app dir right before install: `pnpm --version`,
the build-approval keys pnpm actually resolved (onlyBuiltDependencies via
either allowBuilds or onlyBuiltDependencies), and the pnpm-workspace.yaml
as written. Diagnostics only — never fails the smoke.
Claude-Session: https://claude.ai/code/session_01MN39HnZs8M92iDGqAMcvsK
Co-authored-by: Claude <noreply@anthropic.com>1 parent fc5a3a2 commit 493544b
1 file changed
Lines changed: 20 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
171 | 171 | | |
172 | 172 | | |
173 | 173 | | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
174 | 194 | | |
175 | 195 | | |
176 | 196 | | |
| |||
0 commit comments