[gpmayorga]

This is blocking production promotion right now

promote-production.yml's Shift Production Traffic step is failing on apps-invest:

Error: Unable to locate executable file: pnpm. Please verify either the file path exists
or the file can be found within a directory specified by the PATH environment variable.

Root cause

Neither promote (app-promote-production.yml) nor rollback (app-rollback.yml) run setup-app/pnpm — they only shift Cloudflare traffic on an already-built version, no app build needed. But cloudflare/wrangler-action, when given wranglerVersion, does its own internal wrangler install and auto-detects the package manager from whatever lockfile sits in the checked-out working directory. Both jobs check out the full app repo tree (for the release-tag content / on-main ancestry check), which includes pnpm-lock.yaml — so the action decides to install wrangler via pnpm, which was never set up on that runner.

This has been live since the promote/rollback split was introduced; it just hadn't been exercised until today's real promotion attempts.

Fix

Pin packageManager: npm on both wrangler-action steps, so the install no longer depends on incidental lockfile presence in the checkout.

actions/deploy-app hits the identical wrangler-action code path but isn't broken in practice — every caller of it runs after setup-app's pnpm install (for the actual app build), so pnpm is genuinely on PATH there. Left it untouched to keep this fix minimal to the two jobs that are actually broken; happy to harden it too in a follow-up if preferred.

Verification

• yamllint clean on both files.
• Traced wrangler-action's own install behavior (triggered by the wranglerVersion input) against the exact log sequence reported: 🔍 Checking for existing Wrangler installation → 📦 Installing Wrangler → the pnpm error — matches this failure mode precisely.
• No change to the wrangler commands themselves, the resolve-tag/authorize logic, or any other step.

🤖 Generated with Claude Code

---

Generated by Claude Code