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]>
The npm publisher was deleted this morning without a replacement, so
@hanzo/brand had no producer anywhere: no workflow, no failing run, just a
package that would stop moving. It is back, byte-identical, at
.hanzo/workflows/publish.yml where the forge reads it.
.github/workflows now holds the canonical sync.yml alone — refs to
git.hanzo.ai and nothing else. The file it replaces asked Gitea to pull, which
only makes sense while GitHub is upstream.
The site follows the same shape as every other Hanzo surface: index.html is
self-contained, so the Dockerfile copies it into ghcr.io/hanzoai/static with no
build stage, and deploy.yml publishes ghcr.io/hanzoai/brand:<sha> without
deploying it. hanzoai/universe crs/brand.yaml names the tag that serves and is
inert until a human pins one. Replaces the GitHub Pages push that Pages never
built — brand.hanzo.ai has answered 404 from our own ingress the whole time.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev