Files
build/hanzo.yml
T
Zach Kelling 296622e66e Signed in only: a visitor is drawn nothing and goes to hanzo.id in this tab, and comes back to where they were
There is no popup. hanzo.id answers an authorize from a session it already
holds with a code and no screen, so a person signed in anywhere Hanzo signs
people in is signed in here by a bounce; anyone else signs in there and is
returned to the address they asked for (app/enter.ts). The page signs in
as hanzo-app, the Hanzo App's client, and stops publishing to hanzo.build,
which redirects to the same place on hanzo.ai/dev.

What New holds unsent waits in this tab across the trip, words carried as
?q= among it, and a draft sent while signed out is sent once its person is
in. The visitor's page (the product header over New, and the pitch) goes:
no host draws the builder for a visitor. The specs of what the builder
draws for nobody run under the mount harness, whose host now signs in.
2026-09-28 11:32:43 -07:00

28 lines
1009 B
YAML

# Hanzo CI/CD — build. All real config is here; .hanzo/workflows/cicd.yml is
# triggers and an import of hanzoai/ci.
test:
# Frozen, so the gate resolves the same tree the Dockerfile does. The lockfile
# ships, and a stale one fails here rather than silently building something
# else.
- name: install
run: |
set -e
corepack enable
pnpm install --frozen-lockfile
# Verbatim the build line the image runs, run before there is an image, so a
# break arrives in a minute instead of after a full layer stack. `pnpm build`
# is `tsc --noEmit` then `vite build`. A vite build that emits nothing still
# exits 0, hence the file tests.
- name: build
run: |
set -e
pnpm build
test -s dist/index.html
test -d dist/assets
# Nothing is published: the builder is used at hanzo.ai (its Dev mode), and
# hanzo.build redirects there (hanzoai/universe static-sites build-to-hanzo-ai).
# What ships is the package on npm (.github/workflows/publish.yml).