mirror of
https://github.com/hanzoai/trace-js.git
synced 2026-10-30 18:19:26 +00:00
zeekayandHanzo Dev
0438f2012e
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]>
22 lines
978 B
YAML
22 lines
978 B
YAML
# hanzoai/trace-js — the JS/TS tracing SDKs (hanzo-core, hanzo, hanzo-node,
|
|
# hanzo-langchain, hanzo-vercel) in one yarn workspace. Publishes to npm from a
|
|
# tag; no image, no deploy.
|
|
#
|
|
# The build IS the typecheck: `yarn compile` is the rollup pipeline that emits
|
|
# every package's cjs/esm bundle and its .d.ts, so a type error in any of the
|
|
# five packages fails here — and the artifact this repo exists to publish is
|
|
# exactly what gets built.
|
|
#
|
|
# Not `yarn test`: every test script is `dotenv -- jest`, and the suites talk to
|
|
# a live ingest host with keys from .env. That is an integration lane; it fails
|
|
# for a missing credential, which is not a statement about the commit.
|
|
# Not `yarn lint` either: that script is `eslint --fix`, which REPAIRS what it
|
|
# measures. A check that rewrites the tree can report success for code that was
|
|
# wrong when the job started.
|
|
test:
|
|
- name: compile
|
|
run: |
|
|
set -e
|
|
yarn install --frozen-lockfile
|
|
yarn compile
|