feat: v1.6.0 — unified AI-agent interface (P0-P5) - #5
Closed
chenliuyun wants to merge 17 commits into
Closed
Annotations
11 errors and 1 warning
|
|
|
tests/commands/mcp.test.ts#L373
AssertionError: expected +0 to be 2 // Object.is equality
- Expected
+ Received
- 2
+ 0
❯ tests/commands/mcp.test.ts:373:31
|
|
tests/commands/mcp.test.ts#L341
AssertionError: expected true to be falsy
- Expected
+ Received
- false
+ true
❯ tests/commands/mcp.test.ts:341:25
|
|
tests/commands/mcp.test.ts#L311
SyntaxError: Unexpected token N in JSON at position 0
❯ tests/commands/mcp.test.ts:311:25
|
|
tests/commands/mcp.test.ts#L297
AssertionError: expected true to be falsy
- Expected
+ Received
- false
+ true
❯ tests/commands/mcp.test.ts:297:25
|
|
tests/commands/mcp.test.ts#L276
SyntaxError: Unexpected token N in JSON at position 0
❯ tests/commands/mcp.test.ts:276:25
|
|
tests/commands/mcp.test.ts#L248
AssertionError: expected 'No credentials configured (expected f…' to match /No device with id/
- Expected:
/No device with id/
+ Received:
"No credentials configured (expected file: /home/runner/.switchbot/config.json)"
❯ tests/commands/mcp.test.ts:248:18
|
|
tests/commands/mcp.test.ts#L232
SyntaxError: Unexpected token N in JSON at position 0
❯ tests/commands/mcp.test.ts:232:25
|
|
tests/commands/mcp.test.ts#L206
SyntaxError: Unexpected token N in JSON at position 0
❯ tests/commands/mcp.test.ts:206:25
|
|
tests/commands/mcp.test.ts#L196
AssertionError: expected true to be falsy
- Expected
+ Received
- false
+ true
❯ tests/commands/mcp.test.ts:196:25
|
|
tests/commands/mcp.test.ts#L160
AssertionError: expected true to be falsy
- Expected
+ Received
- false
+ true
❯ tests/commands/mcp.test.ts:160:25
|
|
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
The logs for this run have expired and are no longer available.
Loading