From 82c33077d0836ed0c2deb4d25f38dfc1416ced20 Mon Sep 17 00:00:00 2001 From: Michael Harp Date: Wed, 17 Jun 2026 09:15:48 -0400 Subject: [PATCH] Raise publish build timeout to 10 minutes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The publish `build` job is capped at `timeout-minutes: 5`, but the build was already running ~4m41s (references:all clones and generates docs for three products, which is network-variable). The component-version refresh tasks added in #339 make additional live GitHub API calls, pushing a representative build to ~5m06s — over the cap — so the job was cancelled at the Archive step and the deploy was skipped, leaving master unpublished. Raise the cap to 10 minutes to restore publishing and give headroom for the network-variable build. Signed-off-by: Michael Harp Co-Authored-By: Claude Opus 4.8 --- .github/workflows/build.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml index a35151cd0..838ea4dc1 100644 --- a/.github/workflows/build.yaml +++ b/.github/workflows/build.yaml @@ -57,7 +57,10 @@ jobs: build: runs-on: ubuntu-24.04 - timeout-minutes: 5 + # references:all clones and generates docs for three products and the + # component-version tasks make live GitHub API calls, so the build is network- + # variable and runs ~5 min; give headroom above the previous tight 5-min cap. + timeout-minutes: 10 needs: - setup env: