chore(ci): seed minimal GitHub Actions workflow#9
Merged
petterlindstrom79 merged 1 commit intomainfrom Apr 17, 2026
Merged
Conversation
This seeds a workflow file into main so that pull_request triggers on future PRs fire reliably. The Phase B+C PR (adds F-0-001..F-0-020) contains the real check steps — typecheck, vitest, lint:no-bare-catch, and the SSRF inventory guard — but those scripts don't exist on main yet, so running them here would fail. For now the seed just runs the build (mcp-server, then apps/api) which main has the infrastructure for today. The real CI steps land with the Phase B+C merge. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
petterlindstrom79
added a commit
that referenced
this pull request
Apr 17, 2026
…kage import apps/api/src/routes/mcp.ts imports from the `strale-mcp/tools` workspace package, which resolves to packages/mcp-server/dist/tools.js (+ .d.ts). The Dockerfile builds the MCP server before the API for exactly this reason — without it tsc --noEmit can't find the module and fails with TS2307. The seed workflow (PR #9, now on main) had this step; it was dropped by accident when Phase C's richer ci.yml was written. Restoring it before typecheck; leaving it before `npm test` as well since tests also type-check the imports transitively. CI failure pre-fix: src/routes/mcp.ts(31,8): error TS2307: Cannot find module 'strale-mcp/tools' src/routes/mcp.ts(81,50): error TS7006: Parameter 'c' implicitly has an 'any' type. src/routes/mcp.ts(82,53): error TS7006: Parameter 's' implicitly has an 'any' type. The two TS7006 errors cascade from the TS2307 (caps/sols become any[] when the import can't be resolved); they disappear once the build step is in place. Co-Authored-By: Claude Opus 4.7 (1M context) <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
1 participant
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.
Seeds a workflow file into main so that `pull_request` triggers on future PRs fire reliably. Enables the Phase B+C PR (#8) to run CI.
Why this exists as a separate small PR
Today there is no workflow file on main. When #8 was opened, GitHub didn't auto-trigger its workflow because introducing a workflow in a PR against a base that has never had one leaves the trigger in an ambiguous state. Seeding this tiny workflow first, then rebasing/merging #8 on top, gets #8's richer CI running.
What this workflow does
Just `npm ci` + `npm run build` (mcp-server then apps/api) — the only steps main's current package.json has scripts for.
What this PR does NOT include
After this merges, #8 will be updated to merge main back in (resolves conflicts), and its fuller ci.yml will land when #8 merges.
🤖 Generated with Claude Code