Files
zeekayandHanzo Dev 79eee21f84 Build nchain on the lane that publishes to both registries
Moves off hanzoai/.github's docker-build.yml, which pushes to ghcr and stops,
onto hanzoai/ci's build.yml, which makes the same push and then copies the tag
set to oci.hanzo.ai server-side. So the image exists at both addresses and the
fleet can pull from ours. ghcr is not retired — it stays as the public mirror,
the same arrangement source has with the forge canonical and GitHub mirroring it.

The version keeps its series: imgver takes the max of the declared version and
the registry floor, this repo declares no manifest, so the floor decides and the
next patch follows it rather than restarting.

It also gains a gate it did not have — the old lane ran none. go build ./... and
go vet ./... both pass on this tree today, which is what makes adding them safe
rather than a wager.

Only the image-build caller is removed. Anything else under .hanzo/workflows or
.github/workflows is left alone.

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

29 lines
949 B
YAML

# Hanzo nchain — the one file that says how this repo builds, gates and ships.
#
# It replaces a caller of hanzoai/.github's docker-build.yml, which pushes to
# ghcr and stops there. hanzoai/ci's build.yml makes the same push and then
# copies the tag set to oci.hanzo.ai server-side, so the image exists at both
# addresses. ghcr stays as the public mirror — the same arrangement source has,
# with the forge canonical and GitHub mirroring it.
#
# The Dockerfile declares no ARGs, so nothing is passed; the reusable stamps
# provenance as a label regardless.
#
# The version is derived, never typed: this repo declares no manifest, so imgver
# takes the registry floor (0.1.1 today) and publishes the next patch.
test:
- name: build-and-vet
run: |
set -e
go build ./...
go vet ./...
images:
- name: nchain
context: .
dockerfile: Dockerfile
repo: ghcr.io/hanzoai/nchain
platforms:
- linux/amd64