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

Make Namespace cache setup fail open
Some checks failed
Build: Android / Android Rust Core Stub (push) Failing after 22s
Details
Build Rust / Cargo Test (push) Successful in 4m3s
Details
Build Site / Next.js Build (push) Failing after 5s
Details
Lint Governance / BEP Metadata (push) Successful in 1s
Details

Browse source
This commit is contained in:
Conrad Kramer 2026-06-07 09:51:35 -07:00
parent dba641035b
commit 2da04bc317
2 changed files with 29 additions and 13 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

@ -47,6 +47,10 @@ The same change also makes the forge itself the release authority: release tags
- `//bazel/apple:release_macos_stamp`
These targets wrap the existing Xcode project and give the workflow one stable entrypoint that shares the same Bazel/Nix cache setup while Burrow decides whether deeper `rules_apple` targets are worth the migration.
- Use Namespace cache setup before Bazel/Nix work. Prefer the Namespace Bazel remote cache when `nsc` is authenticated and fall back to a local disk/repository cache when remote setup is unavailable.
Cache setup is optional release acceleration: Bazel-only cache steps must not
install filesystem-cache helpers such as `spacectl`, and Namespace cache
probes must be timeout-bounded so Apple builds can continue without the
remote cache.
- Produce unsigned Apple validation artifacts when signing is absent, but require signing for an App Store requested iOS release and for a Sparkle tester release. Uploadable artifacts are produced only after provisioning profiles can be synced from App Store Connect credentials and the relevant Apple certificate is proven to match the selected Google KMS key.
- Resolve release credentials through age/agenix before signed Apple lanes run. Forgejo secrets should carry only the runner age identity fallback and the Authentik WIF client secret until OpenBao can mint the runner token directly. App Store Connect keys and signing certificates live as sealed files under `secrets/`.
- Persist the forge runner SSH key as `/var/lib/forgejo-runner-agent/age_keystore` and export `BURROW_RUNNER_AGE_IDENTITY_PATH` so jobs can resolve agenix identities without embedding long-lived material in every workflow.