Skip to main content

​
CI Pipeline

The CI runs on every push to main and every pull request. It uses smart scoping to skip expensive jobs when only docs or native code changed.

​
Job Overview

JobPurposeWhen it runs
docs-scopeDetect docs-only changesAlways
changed-scopeDetect which areas changed (node/macos/android)Non-docs PRs
checkTypeScript types, lint, formatNon-docs changes
check-docsMarkdown lint + broken link checkDocs changed
code-analysisLOC threshold check (1000 lines)PRs only
secretsDetect leaked secretsAlways
build-artifactsBuild dist once, share with other jobsNon-docs, node changes
release-checkValidate npm pack contentsAfter build
checksNode/Bun tests + protocol checkNon-docs, node changes
checks-windowsWindows-specific testsNon-docs, node changes
macosSwift lint/build/test + TS testsPRs with macos changes
androidGradle build + testsNon-docs, android changes

​
Fail-Fast Order

Jobs are ordered so cheap checks fail before expensive ones run:
  1. docs-scope + code-analysis + check (parallel, ~1-2 min)
  2. build-artifacts (blocked on above)
  3. checks, checks-windows, macos, android (blocked on build)

​
Runners

RunnerJobs
blacksmith-16vcpu-ubuntu-2404Most Linux jobs, including scope detection
blacksmith-16vcpu-windows-2025checks-windows
macos-latestmacos, ios

​
Local Equivalents

pnpm check          # types + lint + format
pnpm test           # vitest tests
pnpm check:docs     # docs format + lint + broken links
pnpm release:check  # validate npm pack

​
Strict TypeScript Baseline

pnpm check:strict still runs the full native TypeScript check with pnpm tsgo. It is intentionally left as the repo-wide truth source, even while older strict debt remains in unrelated areas. Use these helper gates while the repo-wide cleanup is in progress: 
pnpm check:strict:baseline
pnpm check:strict:scoped
check:strict:baseline writes the current full output and grouped summary under .artifacts/strict/. It is a reporting command and does not hide failures. check:strict:scoped also runs pnpm tsgo, but it fails only when strict errors appear in the wallet, Marketplace, mining, and recently touched UI/tool files. This gives those lanes a usable no-regression gate while older ACPX, ACP spawn, config/debug UI, SDK typing, and other repo-wide strict buckets are cleaned in separate commits.