mirror of
https://github.com/hanzozt/zt.git
synced 2026-10-30 15:04:55 +00:00
zeekayandHanzo Dev
124c8bc5b1
ghcr.io/hanzozt/zt carries both roles and is built from this tree. hanzo.yml declares it for linux/amd64 and linux/arm64 and gates it on vet and the unit tests; cicd.yml hands it to hanzoai/ci, whose door builds each architecture natively. The deleted workflows built from dist/, which no longer exists, or pushed to docker.io. Co-authored-by: Hanzo Dev <[email protected]>
819 B
819 B
Releasing ZT
ZT ships one image, ghcr.io/hanzozt/zt, for linux/amd64 and linux/arm64.
It is built the one way every repo in the estate is built: /hanzo.yml declares
the image and the gate, and .github/workflows/cicd.yml hands it to
hanzoai/ci, whose build door compiles each architecture natively in-cluster
and joins the two under one index.
- A push to
mainruns the gate (test:inhanzo.yml) and publishes the next patch after the highest ofversion:and what the registry already holds. - A
v*tag publishes exactly that version. Tag only a commit whose gate is green.
Before tagging, the gate should pass locally:
go vet ./...
go test ./...
The image runs either role from its environment; zt controller --help and
zt router --help list the variables each one reads.