Raise deploy ship timeout to 5 minutes#341
Merged
corporate-gadfly merged 1 commit intoJun 17, 2026
Merged
Conversation
The deploy `ship` job is capped at `timeout-minutes: 1`, but pulling and extracting the full-site archive, uploading the Pages artifact, and the GH Pages deployment now total just over a minute as the site has grown (older deploys ran ~30s). A manual deploy of master hit the cap and was cancelled at the "Deploy to GH Pages" step, so the build never went live. Raise the cap to 5 minutes to give headroom. Signed-off-by: Michael Harp <mike@mikeharp.com> Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
corporate-gadfly
approved these changes
Jun 17, 2026
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.
What
Raise the deploy
shipjob'stimeout-minutesfrom 1 to 5.Why
Follow-up to #340. A manual deploy of
masterwas cancelled at the Deploy to GH Pages step: theshipjob ran 1m02s and hit its 1-minute cap.The job pulls + extracts the full-site archive, uploads the Pages artifact, and runs the GH Pages deployment. As the site has grown these now total just over a minute (older deploys ran ~30s), leaving no budget for the final deploy step. The successful build had already pushed the archive to GHCR, so this purely a wall-clock cap, not a content/build problem.