fix(cli): Expose projectPath/workspacePath as CLI flags for list-schemes #815
cameroncookeAnnotations
2 errors and 4 warnings
|
build-and-test (24.x)
Process completed with exit code 1.
|
|
src/mcp/tools/project-discovery/__tests__/list_schemes.test.ts > list_schemes plugin > Export Field Validation (Literal) > should expose an empty public schema:
src/mcp/tools/project-discovery/__tests__/list_schemes.test.ts#L29
AssertionError: expected true to be false // Object.is equality
- Expected
+ Received
- false
+ true
❯ src/mcp/tools/project-discovery/__tests__/list_schemes.test.ts:29:92
|
|
build-and-test (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test (24.x):
src/daemon.ts#L213
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
build-and-test (24.x):
src/daemon.ts#L212
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|
|
build-and-test (24.x):
src/daemon.ts#L211
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
|