Files
engine/hanzo.yml
zandGitHub 90e241dd36 Build the image through hanzoai/ci
deploy.yml ran buildx on a runner with no Docker daemon, so it never
published. hanzo.yml now declares the image and cicd.yml hands it to the
build door.

Also: the site action is now called by its GitHub path, since GitHub
does not resolve a URL in uses:.

Claude-Session: https://claude.ai/code/session_01HuMDfgFssPUptYUzgZ6Cp8
2026-09-24 10:26:51 -07:00

34 lines
1.4 KiB
YAML

# Canonical CI/CD config for hanzoai/engine — read by the hanzoai/ci reusable
# (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
#
# The Zen inference engine: a 23-crate Rust workspace.
#
# The image is declared at the end of this file and built by the build door;
# it is the Dockerfile's one builder. The GPU/FFI/release lanes sit beside it.
#
# `rustup component add rustfmt` first: the toolchain this workflow provisions
# (dtolnay/rust-toolchain@stable) installs the compiler ALONE, so `cargo fmt`
# dies with "'cargo-fmt' is not installed for the toolchain" before reading a
# line of code — a red run that says nothing about the repo. ci.yml buys this
# with `components:` on the toolchain action; the provision step above is not
# ours to configure, so the gate buys it itself. It is idempotent.
#
# The gates are the repo's own (.hanzo/workflows/ci.yml), cheapest first: fmt
# is seconds and catches what needs no compiler, then a full type-check of every
# member. `cargo check` — not `cargo build` — because nothing here consumes a
# binary; the question this gate asks is whether the workspace still compiles.
test:
- name: fmt
run: rustup component add rustfmt && cargo fmt --all -- --check
- name: check
run: cargo check --workspace
# Built by the build door, one BuildKit Job per platform.
images:
- name: engine
context: .
dockerfile: Dockerfile
repo: ghcr.io/hanzoai/engine
platforms: [linux/amd64]