Files
zeekayandHanzo Dev 264d3c2578 one runner label, one go toolchain
The label names the platform, not the org, and the toolchain is 1.26.8
everywhere.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-09 00:03:34 -07:00

25 lines
1.1 KiB
YAML

# ~7-line canonical caller — all real config lives in /hanzo.yml.
# Runs on OUR zap-proto arc scale set (never a GitHub-hosted runner).
name: CI/CD
on:
workflow_dispatch:
push:
branches: [main]
tags: ['v*']
pull_request:
jobs:
cicd:
# No runner override. The fleet carries org-prefixed labels for hanzo,
# hanzoai, lux, zoo, pars, zen and luxfi and NONE for zap-proto, so asking
# for linux-amd64 asked for a pool that does not exist and
# both runs this repo has ever had sat queued with no runner while 27 sat
# idle. The default is linux-amd64, which 28 of 30 carry and
# which zap-proto/http already builds on.
# Pinned past v1 deliberately. v1 is at v1.0.89 and this repo needs
# v1.0.91, where the fallback registry sign-in warns instead of refusing —
# without it the gate dies at a GHCR login for a repo that publishes no
# image. hanzoai/ci pins ITSELF to a version for the same reason. Move to
# v1 once that tag carries v1.0.91 or later.
uses: hanzoai/ci/.hanzo/workflows/[email protected]
secrets: inherit