From 45df1c9d848df6ac0358430ce5054b3493e5c8a4 Mon Sep 17 00:00:00 2001 From: vvillait88 Date: Fri, 31 Jul 2026 01:04:24 -0700 Subject: [PATCH] ci: typecheck through the pinned script, not bunx `bunx tsc --noEmit` resolves TypeScript independently of the project, so CI was not necessarily compiling with the version this repo pins. That is a documented trap: a bunx-resolved tsc has fetched a different major and printed its help text while exiting non-zero, which reads exactly like a real type error and sends a verification down a false path. It is live now rather than theoretical: TypeScript is held at ^6 org-wide and 7.0.2 is published, so bunx had a newer major available to reach for. `bun run typecheck` runs the same `tsc --noEmit` against the pinned version. Co-Authored-By: Claude Opus 5 (1M context) --- .github/workflows/ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 663b125..0982fcb 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -28,7 +28,7 @@ jobs: restore-keys: ${{ runner.os }}-bun- - run: bun install --frozen-lockfile - run: bun run lint - - run: bunx tsc --noEmit + - run: bun run typecheck - run: bun run knip - run: bun run test -- --coverage - run: bun run build