From 17e1f312766b97804821142bd6b6b1f1c62306d2 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 16 May 2026 16:32:16 +0000 Subject: [PATCH] Fly deploy: install flyctl manually so subsequent steps see it on PATH MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit superfly/flyctl-actions/setup-flyctl@master left the runner without flyctl on PATH for the next step — "Ensure Fly app exists" hit "fly: command not found" with exit 127. Likely a recent regression in the action's PATH propagation. Replace with a manual install that: - curls Fly's install script to $HOME/.fly/bin - appends that directory to $GITHUB_PATH so every subsequent step sees flyctl - verifies the binary in the same step with an absolute path --- .github/workflows/fly-deploy.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/.github/workflows/fly-deploy.yml b/.github/workflows/fly-deploy.yml index 3f63fef..74816df 100644 --- a/.github/workflows/fly-deploy.yml +++ b/.github/workflows/fly-deploy.yml @@ -108,7 +108,16 @@ jobs: echo "wrote $(wc -l < $RUNNER_TEMP/secrets.env) entries" - name: Setup flyctl - uses: superfly/flyctl-actions/setup-flyctl@master + # superfly/flyctl-actions/setup-flyctl@master left flyctl off + # the runner PATH for the next step (cmd-not-found, exit 127). + # Install manually + append to GITHUB_PATH so every subsequent + # step sees the binary. + run: | + curl -L https://fly.io/install.sh | sh + echo "$HOME/.fly/bin" >> "$GITHUB_PATH" + # Verify in this same step (uses absolute path because the + # PATH change only takes effect for later steps). + "$HOME/.fly/bin/flyctl" version - name: Ensure Fly app exists env: