Skip to content

ci: add workflow for typecheck, test, and build#3

Merged
govindkavaturi-art merged 1 commit into
mainfrom
ci/initial-workflow
May 4, 2026
Merged

ci: add workflow for typecheck, test, and build#3
govindkavaturi-art merged 1 commit into
mainfrom
ci/initial-workflow

Conversation

@govindkavaturi-art
Copy link
Copy Markdown
Member

Summary

Adds the first CI workflow to cueapi-mcp. The repo had no `.github/workflows/` despite 45 vitest tests and an actively published `@cueapi/mcp` package on npm (currently v0.2.0). Every prior release shipped without automated verification.

Workflow

Runs on push to main + pull_request:

  • `npm ci` — reproducible installs
  • `npx tsc --noEmit` — typecheck (separate from build so a type error fails distinctly from a bundling error)
  • `npm test` → `vitest run` (45 tests across oauth-flow, pkce, token-store, tools)
  • `npm run build` → `tsc`

Actions pinned to commit SHAs (`checkout` v4.1.7, `setup-node` v5.3.0) matching the pinning convention used in cuechain / cueapi-python.

Local verification

All three steps pass on Node 20:

  • Typecheck: no errors
  • Tests: 45 passed (pkce.test.ts: 8, tools.test.ts: 9, oauth-flow.test.ts: 13, token-store.test.ts: 15)
  • Build: no errors

Out of scope

  • Branch protection — not configured by this PR. After CI has a green baseline, repo owner can toggle required status checks in repo settings.
  • Publish automation — intentionally not wired. `prepublishOnly: npm run build` already gates local publishes; an automated publish workflow can come later.
  • Lint — no ESLint/Biome config in the repo yet; not added here to keep scope minimal.

Test plan

  • CI green on this PR
  • After merge: verify ci.yml runs on next PR

The repo had no .github/workflows/ despite 45 vitest tests and an
actively published @cueapi/mcp package on npm (currently v0.2.0).
Every prior release shipped without automated verification.

Workflow runs on push to main + pull_request:
- npm ci for reproducible installs
- tsc --noEmit for typechecking (separate from build so a type
  error fails distinctly from a bundling error)
- npm test → vitest run (45 tests across oauth-flow, pkce,
  token-store, tools)
- npm run build → tsc

Actions pinned to commit SHAs (checkout v4.1.7, setup-node v5.3.0)
matching the pinning convention used in cuechain/cueapi-python.

Local verification: all three steps pass on Node 20.

Does NOT add branch protection — that's a separate settings-only
change the repo owner can make after this lands and CI has a green
baseline to gate on.
@govindkavaturi-art govindkavaturi-art merged commit 30e6c99 into main May 4, 2026
1 check failed
govindkavaturi-art pushed a commit that referenced this pull request May 4, 2026
…y-paste error from #3)

The SHA f677139bbe7f9c59b41e40162b753c062f5d49a3 is for actions/setup-python@v5.3.0,
not actions/setup-node. CI failed with "Unable to resolve action ... unable to find
version" on every run since #3 merged. Replacing with actions/setup-node@v4.4.0's
correct SHA so CI actually runs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
govindkavaturi-art added a commit that referenced this pull request May 4, 2026
* chore(ci): add Mergify Dependabot batching + dependabot.yml

Mirrors the pattern in cueapi-core / cueapi-cli / cueapi/cueapi:
- .mergify.yml: 5-at-a-time Dependabot batch with 30 min max wait,
  gated on the new `Typecheck, Test, Build` check from #3.
- .github/dependabot.yml: weekly Monday npm + GitHub Actions updates
  with patch+minor grouping.

Mergify GitHub App is installed on the cueapi org with all-repositories
access (since 2026-05-04T10:24); this config will activate on merge.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(ci): correct actions/setup-node SHA (was setup-python's SHA — copy-paste error from #3)

The SHA f677139bbe7f9c59b41e40162b753c062f5d49a3 is for actions/setup-python@v5.3.0,
not actions/setup-node. CI failed with "Unable to resolve action ... unable to find
version" on every run since #3 merged. Replacing with actions/setup-node@v4.4.0's
correct SHA so CI actually runs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Gk <gk@Gks-MacBook-Pro.local>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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