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

Keep internal TestFlight off external beta review
Some checks failed
Build Rust / Cargo Test (push) Successful in 4m2s
Details
Build Site / Next.js Build (push) Failing after 4s
Details
Lint Governance / BEP Metadata (push) Successful in 1s
Details

Browse source
This commit is contained in:
Conrad Kramer 2026-06-07 20:34:59 -07:00
parent 0924e40463
commit ff4896a901
6 changed files with 40 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -205,6 +205,12 @@ The same change also makes the forge itself the release authority: release tags
upload/signing jobs cannot suppress 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.
- Internal TestFlight distribution must not submit the build for external beta
review. The internal lane waits for processing, sets export-compliance
metadata, uses Fastlane `skip_submission:true`, and relies on App Store
Connect's configured internal tester group availability. External TestFlight
distribution requires explicit groups plus beta-review metadata before it can
be enabled.
- 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.