Files
zeekay b974e05a41 gate the package instead of only releasing it
.github/workflows held one file: the changesets release lane. So `vitest run`
and `tsc --noEmit` were declared in package.json and run by nothing, and every
push to main went straight at a publish with no check in front of it.

hanzo.yml now runs lint, types and the suite on every push and pull request,
through the canonical caller.

What the dropped lane did that this does not: open changesets version pull
requests and publish to registry.npmjs.org. The forge holds no npm credential,
so porting it would have produced a lane that cannot reach the registry.
Publishing is a manual `pnpm run release` until there is one.
2026-08-13 21:07:31 -07:00

20 lines
645 B
YAML

# Canonical CI/CD config for hanzoai/mdx — read by the hanzoai/ci reusable
# (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
#
# No `images:`: this is an npm library, not a service.
#
# The repo had no gate at all — .github/workflows held only the changesets
# release lane, so `vitest run` and `tsc --noEmit` were declared in package.json
# and never run by anything. They run now, on every push and pull request.
test:
- name: lint and types
run: |
set -euo pipefail
pnpm install --frozen-lockfile
pnpm run lint
pnpm run types:check
- name: unit
run: |
set -euo pipefail
pnpm run test