runs-on names a machine, not a purpose

The purpose-prefixed labels (hanzo-build-*, hanzo-deploy-*, hanzo-docs-build-*)
are retired in favour of the bare <os>-<arch> every runner already advertises.

They were not a capability, only a habit, and the habit cost builds: papers asked
for hanzo-build-linux-amd64, no online runner offered it, and two idle
linux-amd64 runners sat beside the queue while the build simply never ran. The
lux tree lost three days to lux-linux-amd64 the same way.

What a job is FOR is the workflow's name. runs-on is the machine it needs.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
2026-09-15 11:47:45 -07:00
co-authored by Hanzo Dev
parent 3100369fc3
commit ffc90b9157
+1 -1
View File
@@ -14,7 +14,7 @@ jobs:
# Apple pool. macos-arm64 is not one it lists, and a job
# asking for a label no runner advertises queues forever rather than
# failing — so the repo keeps looking like it has CI on this leg.
runs-on: darwin-arm64
runs-on: macos-arm64
timeout-minutes: 90
steps:
- uses: actions/checkout@v4