mirror of
https://github.com/AgentSeal/codeburn.git
synced 2026-08-23 07:25:16 +00:00
4a971ee8a7
The repo moved to npm workspaces and CI followed the core package: there is a job for typecheck, test, build, verify-dist and pack across three node versions. Nothing runs the CLI's suite — roughly 2470 tests, including the 29 provider bridge suites that byte-compare against goldens captured before the extraction. Issue #809 says every phase PR passes a byte-identical parity gate; until now nothing enforced it. Two things stood in the way. The CLI's test script was `vitest`, which is watch mode — in CI that hangs a runner instead of failing. And the root test script forwarded only to the CLI workspace, so core's guardrail suite never ran from the command a contributor reaches for, while the CLI half of it could not run from a clean checkout at all: core's exports resolve to dist, which is gitignored. The root script now builds core before running either suite. That costs a build on every local run, which is a real annoyance, but the alternative is a script that only works if you happen to have built core earlier. The CLI job runs the suite on two node lines: the engines floor (22.13.x) and 24.x. The second leg is not matrix sprawl — the zed bridge parity suite seeds its fixture with zlib's zstd, which only landed in 22.15, so a floor-only job would silently skip the byte-compare gate this job exists to run and still go green. The floor leg keeps the >=22.13 promise enforced; the 24.x leg makes the parity gate actually execute. The job carries a 15-minute timeout — measured wall time for the whole suite is ~2 minutes — so a hung run cannot burn a runner for the default six hours, and the workspace-versions check runs before npm ci: it only reads the three manifests and the lockfile, so a drift fails in a second instead of after a full install. |
||
|---|---|---|
| .. | ||
| workflows | ||
| FUNDING.yml | ||
| PULL_REQUEST_TEMPLATE.md | ||