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-16 02:36:51 -07:00
co-authored by Hanzo Dev
parent 68b70d4e04
commit 3b78d2e0cd
+1 -1
View File
@@ -18,7 +18,7 @@ on:
jobs:
publish:
runs-on: [hanzo-build-linux-amd64]
runs-on: [linux-amd64]
steps:
- uses: actions/checkout@v4