Repository navigation
Run the CLI CI job on Linux, Windows and macOS - #1537
Merged
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What
Turns the single-OS
CLI (test, build)job into a 3-OS matrix:ubuntu-latest,windows-latest,macos-latest.Why
@anythingmcp/cliis published to npm and installed on all three platforms. It has OS-specific code paths (e.g.browserCommandreturnsopen/rundll32/xdg-open, and the config dir resolves viaXDG_CONFIG_HOME/home dir), but CI only ever ran it on Ubuntu, so Windows/macOS regressions could ship unnoticed. The unit suite already asserts the Windows browser-command form; this makes the whole suite + build actually run on Windows and macOS each PR.Details
strategy.matrix.osover the three runners,fail-fast: falseso one OS failing still reports the others.defaults.run.shell: bashfor the job — Git Bash exists on the Windows runner, so the finaltest ! -e packages/cli/dist/cli.test.jsguard stays portable without rewriting it.npm ci --ignore-scripts: the CLI's only runtime dep is pure JS, so skipping workspace install scripts (Prisma engine download, native backend builds) keeps the job fast and avoids failing on an unrelated backend dependency on Windows/macOS. The CLI test/build touch no backend code.Shell-syntax sub-tests for shells not present on a runner (e.g. zsh/fish on Windows) self-skip, as fish already does on Linux.
No source changes; CI-only.