Files
zeekay d9ecb47849 ci: give the default branch the canonical pair
master is this repo's default branch on the forge and carried no native
lane at all — only .github/workflows, which the forge resolves solely when
.hanzo/workflows is absent. Both files in it asked for ubuntu-latest, a
label no runner on this fleet advertises, so every run queued rather than
failing. The pair here matches the one on main.

build.yml ran install, test, coverage and build — the ground hanzo.yml now
declares, minus the Codecov upload, which went to a service reached through
the GitHub app and has no equivalent here.

release.yml is dropped rather than ported. It ran semantic-release behind
`if: github.repository == 'iam/iam-js-sdk'` — a repository this one has never
been — so it has published nothing from here, and porting it would need an
NPM_TOKEN that this forge does not hold. Cutting a release is now
`yarn semantic-release` run deliberately.

The gate fails on this branch as written: tsconfig.json asks for
module/moduleResolution node16, which needs TypeScript 4.7 or newer, while
package.json pins typescript ^4.5.5, so ts-jest rejects both options before
a test runs. That is the state of the branch, not of the lane.
2026-08-13 21:08:33 -07:00

19 lines
766 B
YAML

# Canonical CI/CD config for hanzoai/iam-js-sdk — read by the hanzoai/ci
# reusable (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
#
# An npm package (the JS client for Hanzo IAM): builds no image, so no
# `images:` and no `deploy:`. Nothing publishes it from CI — the
# semantic-release lane that used to is gone, and `yarn semantic-release`
# remains the way to cut a version.
#
# `--frozen-lockfile` because yarn.lock is committed: without it a resolution
# that drifted from the lockfile passes here and breaks for whoever installs
# it. `build` runs both tsconfig projects (cjs + esm) — the two artifacts the
# package actually exports.
test:
- name: test
run: yarn install --frozen-lockfile && yarn test
- name: build
run: yarn build