Files
chat/hanzo.yml
T
zeekayandHanzo Dev 2f1e47a75f hanzo.chat ships as a site, not an image
hanzo.chat is the chat2 project on the Sites plane, served by cloud by Host,
and nothing runs ghcr.io/hanzoai/chat2. So the lane that matters is the site:
build the export, publish it to s3://hanzo-sites/hanzo/chat2. The image and its
Dockerfile go.

The trigger named master and this repository has only main, so no push has run
this lane since the rename.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-19 09:58:18 -07:00

37 lines
1.1 KiB
YAML

# Hanzo CI/CD — chat. All real config is here; .github/workflows/cicd.yml is
# triggers and an import of hanzoai/ci.
test:
# Frozen, so the gate resolves the same tree the site is built from.
- name: install
run: |
set -e
corepack enable
pnpm install --frozen-lockfile
# `pnpm build` is `tsc --noEmit && vite build`. A vite build that emits
# nothing still exits 0, hence the file test.
- name: build
run: |
set -e
pnpm build
test -s dist/index.html
# 22 assertions over the chunk fold and the SDK against a stub transport —
# node --test with type stripping, no framework. This is the gate that did not
# exist: every surface here is new code and none of it had ever been run by
# anything but a person.
- name: unit
run: |
set -e
pnpm test
# hanzo.chat is this export: the `chat2` project on the Sites plane
# (s3://hanzo-sites/hanzo/chat2), served by cloud by Host and calling only
# api.hanzo.ai. No image, no pod.
site:
slug: chat2
dir: dist
build: corepack enable && pnpm install --frozen-lockfile && pnpm build
on: [main]