Files
zeekayandHanzo Dev 2fb8b0bfd1 ci: canonical pair — hanzo.yml + forge caller
github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-06 02:36:43 -07:00

24 lines
1.0 KiB
YAML

# hanzoai/zip-js — the Zip build/runtime toolkit (TypeScript, npm). A library:
# it publishes to npm from a tag, builds no image and deploys nowhere.
#
# The repo's own three CI steps, verbatim: install from the lockfile, compile,
# run the suite.
# npm ci — installs exactly package-lock.json, so a lockfile that has
# drifted from package.json fails here instead of resolving to
# something no other machine will ever install.
# npm run build — `tsc -p tsconfig.json`. This is the typecheck AND the
# published artifact; there is no separate check to skip.
# npm test — node:test over the handler and the goja/javy/cli runtimes.
#
# Not `npm run examples` / `npm run verify`: those compile the example guests
# through the Javy toolchain, which downloads a WASM build at run time. A gate
# that reaches the network fails when the network does, and says nothing about
# the commit.
test:
- name: build-and-test
run: |
set -e
npm ci
npm run build
npm test