Fly deploy: install flyctl manually so PATH propagates to next step#38
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The previous workflow run failed at "Ensure Fly app exists" with:
superfly/flyctl-actions/setup-flyctl@masterran the previous step but didn't propagate flyctl to PATH for subsequent steps. Likely a regression on@master(unpinned versions are fragile).Fix
Replace the action with a manual install that pipes Fly's published install script to
$HOME/.fly/bin, then explicitly appends that directory to$GITHUB_PATH. Verifies the binary in the same step using its absolute path (PATH changes only take effect for later steps).This is the install pattern Fly's docs recommend when you don't want to depend on a third-party action.
Test plan
flyctl v…version line, and "Ensure Fly app exists" should now findflyon PATHGenerated by Claude Code