Prefer age for release secret decrypt
Some checks failed
Cache: Publish Nix / Publish Nix Cache (push) Has been cancelled
Build Rust / Cargo Test (push) Successful in 4m0s
Build Site / Next.js Build (push) Failing after 4s
Lint Governance / BEP Metadata (push) Successful in 1s

This commit is contained in:
Conrad Kramer 2026-06-07 11:56:04 -07:00
parent 83da429854
commit ef7023f9be
3 changed files with 16 additions and 1 deletions

View file

@ -75,6 +75,11 @@ The same change also makes the forge itself the release authority: release tags
by the deployed forge. The v4 artifact actions assume GitHub's newer artifact
service and fail on this Forgejo install before downstream signing/upload
jobs can consume the staged Apple artifacts.
- The release secret decrypt action must be self-contained after the Nix
bootstrap step. Linux Namespace signing jobs install Nix at runtime, so the
bootstrap writes Nix profile directories to `GITHUB_PATH`, the decrypt action
resolves Nix from those profile paths, and the action builds `.#age` before
falling back to `.#agenix`.
- 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.