Files
zooqueenandHanzo Dev 53905542ff The gate holds on amd64, and both images release as 1.5.89
The gate calls hanzoai/ci [email protected] with linux-amd64 as the only
architecture that gates, and linux-arm64 as an advisory leg that runs and
reports without holding anything. The o11y pod is scheduled on amd64, and the
one shared arm64 node kept the release queued for hours behind other repos.

hanzo.yml states version 1.5.89. The two images' series had drifted apart
(o11y at 1.5.88, o11y-site at 1.5.82) and far ahead of the git tags (v1.5.75), so
a derived number differed per image and a git tag would have overwritten an
August image of the same name. imgver publishes the declared version once and
the next patch thereafter, for both images alike.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-24 10:53:08 -07:00

23 lines
875 B
YAML

# Canonical caller — every knob lives in /hanzo.yml, none here.
# Runs on the git-runner fleet at git.hanzo.ai, the only pool serving these
# labels. github.com resolves only .github/workflows and has no runner for
# them, so a caller placed there is a gate that cannot be scheduled.
name: CI/CD
on:
push:
branches: [main]
tags: ['v*']
pull_request:
workflow_dispatch:
jobs:
cicd:
uses: hanzoai/ci/.github/workflows/[email protected]
with:
# Only linux-amd64 gates: the o11y pod runs on amd64 (nodeSelector
# kubernetes.io/arch: amd64), and the one arm64 node is shared with every
# other runner, so its leg queued for hours and held the release. arm64
# still runs and reports as the advisory leg, which nothing waits on.
test-runners: '["linux-amd64"]'
advisory-runners: '["linux-arm64"]'
secrets: inherit