Pass Apple Rust build tools into Bazel actions
Some checks failed
Build Rust / Cargo Test (push) Successful in 4m5s
Build Site / Next.js Build (push) Failing after 6s
Lint Governance / BEP Metadata (push) Successful in 1s

This commit is contained in:
Conrad Kramer 2026-06-07 10:45:30 -07:00
parent 5150faad99
commit ddbfa47587
4 changed files with 29 additions and 3 deletions

View file

@ -68,6 +68,9 @@ The same change also makes the forge itself the release authority: release tags
- Bazel repository and disk caches must live outside the checked-out repository
on macOS runners. Bazel 9 rejects a repository contents cache inside the main
repo because it can create spurious build graph failures.
- Bazel Apple genrules must explicitly pass the Nix CI shell tool path and
`PROTOC` into the action environment. Xcode build phases run with a reduced
path, and the Rust Network Extension build depends on `protoc`.
- 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.