hackclub/burrow
1
0
Fork 0
Code Pull requests Releases Packages Activity Actions

Add dedicated TestFlight distribution workflow
Some checks failed
Build Site / Next.js Build (push) Waiting to run
Details
Lint Governance / BEP Metadata (push) Waiting to run
Details
Build Rust / Cargo Test (push) Has been cancelled
Details

Browse source
This commit is contained in:
Conrad Kramer 2026-06-07 19:07:00 -07:00
parent 02b7509eaf
commit 13a0bc2fc6
2 changed files with 75 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
evolution/proposals/BEP-0009-release-infrastructure-and-store-upload-pipeline.md
View file

@ -198,7 +198,9 @@ The same change also makes the forge itself the release authority: release tags
repo change. `publish-store-uploads` has a separate no-`needs`
`distribute-ios-testflight` retry job for `distribute_testflight=true` and
`upload_app_store=false`, so skipped upload/signing jobs cannot suppress
distribution of an already-uploaded build.
distribution of an already-uploaded build. `distribute-testflight` is the
narrower one-job retry workflow when only App Store Connect processing and
tester assignment need to be retried.
- 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.