ci: gate packages/types on tsc - #828
Closed
lilyshen0722 wants to merge 1 commit into
Closed
Conversation
packages/types defines `typecheck: tsc --noEmit` and nothing has ever invoked it — the same defined-but-uninvoked shape #826 fixes for the frontend. It is green today, which is the only moment a gate is free. Costs no install: the package has zero dependencies and zero external imports, so it typechecks with the compiler the backend step already installed. Two lines and a comment. packages/commonly-apps is deliberately left out. It has the identical uninvoked `tsc:check` script, but it needs @types/node and this job never npm ci's it, so gating it means adding an install step. Its real state is unknown rather than assumed green — reporting it as green off a TS2688 "cannot find type definition file for 'node'" would be reporting an environment gap as a result. Mutation-checked: a deliberate `const x: number = "str"` in src/user.ts fails the step with TS2322 (exit 2), and the step returns to exit 0 once reverted, so the gate can actually go red. Stacked on #826 (25e6de7) because it is the only other open PR touching tests.yml; merging it first avoids a conflict in the same hunk. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #826 — base is that branch, not
main, because #826 is the only other open PR touchingtests.ymland this lands in the adjacent hunk. Merge #826 first and this rebases to nothing.packages/typesdefinestypecheck: tsc --noEmitand nothing has ever invoked it — the same defined-but-uninvoked shape #826 fixes for the frontend. @ux-lead found it; this gates it.It costs no install
The package has zero dependencies and zero external imports, so it typechecks with the compiler the backend step already installed:
That's a correction to the framing it was handed to me with ("a two-line add whose only cost is an install step") — there is no install step. Verified:
deps: {},devDeps: {}, and no non-relative import anywhere insrc/.It is green today, which is the only moment a gate is free.
Mutation-checked
A gate that cannot go red is decoration, so:
exit 0export const __mutationProbe: number = "not a number"insrc/user.tsTS2322, exit 2exit 0,git statuscleanWorkflow YAML re-parsed after the edit; step lands after both existing typechecks and before the test steps.
packages/commonly-apps is deliberately NOT here
It has the identical uninvoked
tsc:check, but it needs@types/nodeand this job nevernpm cis it, so gating it means adding an install step — a different change with a different cost. Running it as-is yieldsTS2688 cannot find type definition file for 'node', which is an environment gap, not a finding. Its real state is unknown, not assumed green. Flagging rather than silently scoping it out.Not verified
Any follow-up that adds the
packages/*install +commonly-appsstep touches.github/workflows/again and needs the workflow-scoped token — same constraint this push had.🤖 Generated with Claude Code