Files
zeekayandHanzo Dev 7bb234fa32 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:53 -07:00

19 lines
802 B
YAML

# hanzoai/insights-node — the Node client SDK for Insights. A library: it
# publishes to npm from a tag, builds no image and deploys nowhere.
#
# Install from the lockfile (so lockfile drift is a failure, not a silent
# re-resolve), then the repo's own suite — nyc + ava over tests/, which covers
# the parts of a capture client that break quietly: event validation, the
# feature-flag evaluator, and the batching/retry queue. A client that stops
# sending looks exactly like one with nothing to send.
#
# pnpm, not yarn: pnpm-lock.yaml is the lockfile in the tree and package.json
# pins packageManager to pnpm. The repo's ava-tests.yml still says `yarn`, which
# resolves against no lockfile here.
test:
- name: test
run: |
set -e
pnpm install --frozen-lockfile
pnpm test