Extend TestFlight processing wait
Some checks failed
Build Site / Next.js Build (push) Waiting to run
Lint Governance / BEP Metadata (push) Waiting to run
Build Rust / Cargo Test (push) Has been cancelled

This commit is contained in:
Conrad Kramer 2026-06-07 18:58:31 -07:00
parent dd7dc89341
commit 2410de5e51
3 changed files with 24 additions and 2 deletions

View file

@ -190,6 +190,12 @@ The same change also makes the forge itself the release authority: release tags
- Generate staged appcast content from the signed macOS artifact when present.
- Publish `sparkle/<channel>/`, `sparkle/appcast.xml`, and `sparkle/default/` pointers from `publish-store-uploads`.
- The macOS app embeds Sparkle and consumes the `https://releases.burrow.net/sparkle/appcast.xml` feed.
- Treat TestFlight distribution as a retryable post-upload step. Apple build
processing can exceed 30 minutes after a successful IPA upload, so
`apple-distribute-testers` and `publish-store-uploads` wait up to 7200
seconds by default and allow Forgejo variable
`TESTFLIGHT_WAIT_PROCESSING_TIMEOUT_SECONDS` to tune that ceiling without a
repo change.
- Add `infra/releases` as the OpenTofu boundary for the GCS release and package repository backup buckets. Garage is the required S3-compatible primary distribution target after host bootstrap. `infra/identity` remains the boundary for Google KMS signing keys, the Authentik WIF pool/provider, and the runner service account.
- Serve `releases.burrow.net` and `packages.burrow.net` from the forge Caddy
edge as stable Burrow domains backed by the GCS release and package buckets.