From 9cf346775d4e2ac4a8605203a98ecfa4e5474334 Mon Sep 17 00:00:00 2001 From: Michael Harp Date: Wed, 17 Jun 2026 09:50:50 -0400 Subject: [PATCH] Raise deploy ship timeout to 5 minutes 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 Co-Authored-By: Claude Opus 4.8 --- .github/workflows/deploy.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/deploy.yaml b/.github/workflows/deploy.yaml index 15ad29960..7adf845b5 100644 --- a/.github/workflows/deploy.yaml +++ b/.github/workflows/deploy.yaml @@ -40,7 +40,10 @@ jobs: ship: runs-on: ubuntu-24.04 - timeout-minutes: 1 + # Pulling and extracting the full-site archive, uploading the Pages artifact, + # and the GH Pages deployment together exceed 1 minute as the site grows, so + # give the job headroom above the previous tight 1-minute cap. + timeout-minutes: 5 needs: - setup permissions: