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

Fix Namespace Apple runner dispatch
Some checks failed
Build Rust / Cargo Test (push) Successful in 4m15s
Details
Build Site / Next.js Build (push) Failing after 5s
Details
Lint Governance / BEP Metadata (push) Successful in 1s
Details
Cache: Publish Nix / Publish Nix Cache (push) Failing after 20s
Details

Browse source
This commit is contained in:
Conrad Kramer 2026-06-07 08:26:23 -07:00
parent 212b129c31
commit a4db952d3f
12 changed files with 77 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -103,6 +103,17 @@ The same change also makes the forge itself the release authority: release tags
- `namespace-profile-linux-medium`
- `namespace-profile-macos-large`
- `namespace-profile-windows-large`
- Use dedicated Apple distribution labels for the focused tester-distribution
workflow so stale generic Namespace jobs cannot consume Apple release runners:
- `namespace-profile-linux-medium-apple`
- `namespace-profile-macos-large-apple`
- Run forge Namespace services with the repo-owned `nsc` package and keep it
current with the token format expected by Namespace. `nsc 0.0.520` is the
first required baseline for revokable token-file auth.
- Render the sealed Namespace runner token with `nsc token create --token_file`
instead of `nsc auth generate-dev-token`. The dev-token output is for direct
API/registry access, while the dispatcher needs the JSON token-file format
consumed by `nsc run`.
- Add a Rust `burrow-windows-stub` binary so the Windows lane can validate packaging and upload mechanics before native Windows networking support is implemented.
- Treat Sparkle as a macOS public-channel upload lane:
- Generate staged appcast content from the signed macOS artifact when present.