mirror of
https://github.com/hanzoai/iam-js-sdk.git
synced 2026-10-30 18:34:08 +00:00
zeekay
9cd1bc5e08
.hanzo/workflows/ already exists here, so the forge resolves that directory and neither file in .github/workflows/ has been reachable. Both also asked for ubuntu-latest, which no runner on this fleet advertises. build.yml ran install, test, coverage and build — the same ground hanzo.yml already declares, minus the Codecov upload, which went to a service reached through the GitHub app and has no equivalent here. Coverage is still computable with `yarn coverage`; nothing reports it. release.yml is dropped rather than ported. It ran semantic-release on push to master behind `if: github.repository == 'iam/iam-js-sdk'` — a repository this one has never been — so it has published nothing from here. Porting it would need an NPM_TOKEN, which is not among the secrets available on this forge. Cutting a release is now `yarn semantic-release` run deliberately. Correct the hanzo.yml header, which described release.yml as staying.
19 lines
766 B
YAML
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
|