github.com held commits this host lacked, which refuses the mirror push
("fetch first") and stops github receiving anything at all. Merging rather
than overwriting, so the mirror is a fast-forward again and neither side's
work is dropped.
Adds .hanzo/workflows/cicd.yml calling the canonical pipeline and drops the
GitHub-hosted workflows it replaces. Lands here because this is where the repo
is written — git.hanzo.ai is upstream and github.com is its push mirror, so the
same change made on github.com never reaches the runner fleet.
Apache-2.0 §4(c) asks a derivative work to carry the attribution of what it was
built from. This tree carried none: LICENSE was the unmodified boilerplate with
its copyright line still the [yyyy] [name of copyright owner] placeholder, and
no NOTICE existed. The upstream is named directly here.
github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.
Co-authored-by: Hanzo Dev <[email protected]>
1 module(s) in this repo declared go < 1.22. Go 1.22 changed for-loop
variable scoping to per-iteration, so raising the directive past 1.22 can
change runtime behaviour. Each module here was scanned for loops whose
loop variable is captured by a func literal / goroutine / defer, or has its
address taken: zero such sites were found, so the bump is behaviour-preserving.
Verified per module with go build, go vet and go test (-mod=readonly).
Co-authored-by: Hanzo Dev <[email protected]>
zeekay
