mirror of https://github.com/hanzoai/build-demo.git synced 2026-09-30 20:48:40 +00:00

T

zeekayandHanzo Dev 14f93675fb ci: canonical forge caller

hanzo.yml declared a gate with nothing to run it: github.com has no runner for
hanzo-build-linux-amd64, so a caller under .github/workflows can never be
scheduled. This is the ~7-line caller on the plane that can, pinned @v1.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-06 01:16:15 -07:00

.hanzo/workflows

ci: canonical forge caller

2026-08-06 01:16:15 -07:00

cmd/demo

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

src

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

go.mod

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

hanzo.yml

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

LICENSE

legal: dual-license MIT OR Apache-2.0 under Hanzo AI, Inc.

2026-08-04 01:14:58 -07:00

LICENSE-APACHE

legal: dual-license MIT OR Apache-2.0 under Hanzo AI, Inc.

2026-08-04 01:14:58 -07:00

LICENSE-MIT

legal: dual-license MIT OR Apache-2.0 under Hanzo AI, Inc.

2026-08-04 01:14:58 -07:00

NOTICE

legal: dual-license MIT OR Apache-2.0 under Hanzo AI, Inc.

2026-08-04 01:14:58 -07:00

package.json

legal: dual-license MIT OR Apache-2.0 under Hanzo AI, Inc.

2026-08-04 01:14:58 -07:00

README.md

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

tsconfig.json

build-demo: a recipe whose artifacts are a Go binary and an npm package

2026-07-27 22:42:09 -07:00

README.md

build-demo

The smallest proof that hanzo.app builds software, not just container images.

hanzo.yml declares two artifacts and no Dockerfile:

hanzo-demo — a static Go binary, cross-built for linux/amd64 and darwin/arm64
@hanzo/build-demo — a real npm package: tsc compiles src/, npm pack tars it

Both are built by POST /v1/runner on the platform's own cluster and published to https://s3.hanzo.ai/plugins/hanzoai/build-demo/<tag>/, with a binaries.json index carrying the URL and SHA-256 of each file.