fix(release): give desktop closure staging 30min in bun binary builds

The CLI full-package build's nested @fusion/desktop build stages the
production closure via pnpm deploy (~1300+ packages); on cold-store macOS
release runners that exceeded runWorkspaceCommand's default 10-minute
timeout and killed every v0.73.0-beta.* bun-darwin-arm64 release leg with
exit 143. Raise the desktop sub-build budget to 30 minutes and widen the
build-binaries job timeout to 45 minutes to match.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
gsxdsm
2026-07-23 22:56:52 -07:00
parent f9f2832936
commit da0d73c853
2 changed files with 13 additions and 2 deletions

View File

@@ -24,7 +24,10 @@ jobs:
build-binaries:
name: Build ${{ matrix.target }}
runs-on: ${{ matrix.os }}
timeout-minutes: 30
# FNXC:Release 2026-07-23-23:05: 45 min (was 30): the desktop pnpm-deploy closure staging
# inside the CLI full-package build can take >10 min alone on cold-store macOS runners
# (killed every v0.73.0-beta.* bun-darwin-arm64 leg); tsup now allows it 30 min.
timeout-minutes: 45
# Job-level env so the signing steps' `if:` can detect whether the
# signing certificate secrets are configured (secrets can't be read in `if:` directly).
env: