mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-10 09:13:53 +08:00
PR CI ran tests but never built the binary or smoke-tested it, so built-binary regressions only surfaced at the release dry run — e.g. the Windows CreateProcess argv-quoting bug (worker got mangled JSON) slipped all the way to the release gate. Add a path-gated light smoke: on PRs that touch product code (src/, internal/, Makefile.cbm, build.sh, smoke-test.sh, env.sh), build the PRODUCTION binary and run scripts/smoke-test.sh on ubuntu-latest + macos-14 + windows-latest (native, reliable — not the flaky broad/emulated legs). Every leg gates. Docs/CI/test PRs skip it and stay fast (gh pr diff --name-only filter). The full broad/emulated smoke stays in the release dry run. SMOKE_DOWNLOAD_URL is intentionally unset so smoke-test.sh's download/update phases self-skip; the core index/search/trace phases (which catch the CreateProcess class) still run. ci-ok now treats skipped as OK so PRs that skip smoke still pass. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>