Deploy Site failing: `wrangler: not found` in preCommands after #4102

[waynesun09]

Summary

Every Deploy Site run since PR #4102 merged (2026-07-14 17:18 UTC) has failed with:

/bin/sh: 1: wrangler: not found
##[error]Process failed with exit code 127

Both the production deploy and PR-preview jobs in .github/workflows/site-deploy.yml are affected.

Root cause

PR #4102's second commit (0f14ac0) changed preCommands in both cloudflare/wrangler-action steps from an explicit npx wrangler@<version> ... invocation to bare wrangler ..., based on qodo-code-review's "duplicated version pin" finding. The commit message states:

wrangler-action already installs the pinned version and rewrites any command starting with wrangler to npx wrangler ... (no version)

That's accurate for wrangler-action's execCommands() (pinned commit 9acf94a, v3.15.0) — but the rewrite only fires when the entire preCommands line starts with the literal string "wrangler":

const cmd = command.startsWith("wrangler")
    ? `${packageManager.exec} ${command}`
    : command;

Our preCommands are single compound shell lines (by design — see the comments above each step: preCommands runs each newline as a separate /bin/sh invocation, so the mktemp/write/wrangler/cleanup sequence must stay on one line to share the same temp file path):

set -eu; secrets_file="$(mktemp)"; ...; wrangler versions secret bulk "$secrets_file" ...; rm -f "$secrets_file"

This line starts with "set", not "wrangler", so wrangler-action's rewrite never triggers, and bare wrangler runs with nothing on $PATH to resolve it. This was true regardless of dependency versions — the "duplicate pin" fix broke deploys by relying on a mechanism that structurally cannot apply to this workflow's compound-line pattern.

Fix

Restore explicit npx wrangler@4.110.0 inside both compound preCommands lines in .github/workflows/site-deploy.yml (production deploy step and PR-preview step), matching the file's pre-#4102 pattern but with the updated version.

Impact

All production deploys and PR preview deploys of the site are currently broken (since 2026-07-14 17:18 UTC).

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 5:54 PM UTC · Completed 5:57 PM UTC
Commit: 5cd495a · View workflow run →

[fullsend-ai-triage]

Triage Summary

Severity: Critical — All production and PR-preview deploys are broken since PR #4102 merged.

Problem

The Deploy Site workflow fails with wrangler: not found (exit code 127) in both production and PR-preview jobs. This regression was introduced when PR #4102 replaced explicit npx wrangler@4.110.0 with bare wrangler in compound shell preCommands lines.

Root Cause

cloudflare/wrangler-action's command rewrite only fires when a preCommands line starts with the literal string "wrangler". The workflow's compound shell lines start with set -eu;, so the rewrite never triggers and bare wrangler has nothing on $PATH to resolve to.

Recommended Fix

Restore explicit npx wrangler@4.110.0 inside both compound preCommands lines in .github/workflows/site-deploy.yml (production deploy step and PR-preview step).

Proposed Test

1. Apply the fix to site-deploy.yml
2. Trigger a Deploy Site workflow run
3. Verify preCommands step resolves wrangler (no exit code 127)
4. Verify secrets bulk-upload succeeds via npx wrangler@4.110.0
5. Verify full deploy completes without errors

Regression prevention: consider a CI lint check that flags bare
wrangler invocations in compound shell lines where
wrangler-action rewrite cannot apply.

---

Labels: This is a confirmed CI/deployment bug with critical severity — all deploys are broken. Applying type/bug, component/ci, and priority/critical to match repo label conventions.

[fullsend-ai-coder]

🤖 Finished Code · ❌ Failure · Started 5:58 PM UTC · Completed 6:06 PM UTC
Commit: 5cd495a · View workflow run →