hanzo.yml declares the one image, ghcr.io/hanzoai/bootnode:<version>-web,
built from the repository root with console/Dockerfile and named by the
console's own package version, and gates it on the console's unit tests
and typecheck. .hanzo/workflows/cicd.yml runs hanzoai/ci build.yml@v1 on
push to main.
The console manifest names every dependency from the pnpm catalog, and the
catalog carries the versions this code builds against: @luxfi/ui 7.4.3 with
@hanzo/gui 7.3, next 16.2, TypeScript 5.9 and the Zen faces from
@hanzo/font 1.8.0. `pnpm install --frozen-lockfile` and `next build` both
pass. The unused geist and lucide-react entries and the npm lockfile are
gone, tests report in TAP so the pipeline can count them, and the README no
longer calls this repository a retired copy.
Co-authored-by: Hanzo Dev <[email protected]>
ghcr.io/hanzoai/static served only linux/amd64 from v0.5.1 through 0.5.14,
so an image built on it has no manifest an arm64 node can pull. 0.5.15 is
the same server source published as an index over both architectures.
Co-authored-by: Hanzo Dev <[email protected]>
Names the two halves for what they are. The repo already holds both (12407e9 merged
bootnode/bootnode into this history); this makes the frontend directory say so, so the layout
reads the way the owner describes the system: backend and frontend separate, one repo.
git mv throughout — 187 renames, history preserved. Every path reference follows: hanzo.yml
build context and dockerfile, compose.yml, compose.prod.yml, start.sh, LLM.md,
infra/k8s/web-deployments.yaml, infra/cloud/deploy.sh, and the Dockerfile's own COPY paths.
Image and container names (bootnode-web, the -web tag suffix) are deliberately NOT renamed here:
those are a deploy contract the App CR and ingress bind to on port 3001, and breaking them is a
separate, staged change.
Console builds green after the move; the Go tree builds.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev