Retry bun install in build.sh to survive transient GitHub 5xx#26
Merged
Conversation
bun install resolves git dependencies (e.g. ghostty-web pinned to #main) by fetching tarballs from the GitHub API. That endpoint intermittently returns 504, which failed four of six platform legs of the v0.4.0 release build even though the code and lockfile were sound. Wrap the install in a 3-attempt retry with linear backoff so a transient blip no longer sinks a tagged release; a genuinely broken lockfile still fails after the final attempt. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
What
Wrap
bun installinscripts/build.shwith a 3-attempt retry (linear backoff: 10s, 20s).Why
The
v0.4.0release build failed on 4 of 6 platform legs with:bun installresolves git dependencies (likeghostty-web, pinned to#main) by fetching tarballs from the GitHub API, which intermittently returns504. The code and lockfile were sound — the darwin legs and a local build of the same commit passed — but the transient blip still sank the tagged release and required a manual re-run of the failed jobs.Behavior
bash -nclean.🤖 Generated with Claude Code