Skip to content

fix(release): TS strict cast for unknown-status fixture (v7.0.0 hotfix)#74

Merged
m0n0x41d merged 1 commit intomainfrom
dev
Apr 29, 2026
Merged

fix(release): TS strict cast for unknown-status fixture (v7.0.0 hotfix)#74
m0n0x41d merged 1 commit intomainfrom
dev

Conversation

@m0n0x41d
Copy link
Copy Markdown
Owner

Summary

  • Cast fixture.unknown_status_examples entries to ProjectReadiness at the test call site
  • Unblocks desktop/frontend tsc -b strict mode in the release workflow's Build CLI matrix
  • Caught by Build CLI linux-arm64 failing first → fail-fast cancelled the rest of the matrix on the original v7.0.0 tag run

Test plan

  • npm --prefix desktop/frontend run build green locally
  • go test ./... green via lefthook pre-push
  • Re-tag v7.0.0 → release matrix builds green

🤖 Generated with Claude Code

…ract test

The release pipeline runs `tsc -b` in desktop/frontend strict mode, which
the regular CI does not — so this slipped through PR #72 and PR #73 and
broke v7.0.0 tag-build matrix on linux-arm64 (and fail-fast cancelled
the rest).

`fixture.unknown_status_examples` is `readonly string[]` by design — the
test deliberately feeds invalid strings to `projectReadiness` to verify
that `isProjectReadiness` filtering rejects them. TS strict refuses
`string -> "ready" | "needs_init" | "needs_onboard" | "missing" |
undefined` without a cast. Casting at the call site preserves the test's
intent (exercise the rejection path) while satisfying the type checker.
@m0n0x41d m0n0x41d merged commit 292196b into main Apr 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant