chore(deps-dev): bump vitest from 3.2.4 to 4.1.0 in the npm_and_yarn group across 1 directory #28
pnarayanaswamymain.yml
on: pull_request
Matrix: Build, lint, and test / Prepare
Check workflows
26s
Matrix: Build, lint, and test / Build
Matrix: Build, lint, and test / Compatibility test
Matrix: Build, lint, and test / Lint
Matrix: Build, lint, and test / Test
Matrix: Analyse code / CodeQL analysis
Publish release
/
publish-npm
Annotations
30 errors and 16 warnings
|
Build, lint, and test / Test (24.x)
Process completed with exit code 1.
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > delegate methods > delegates all DeviceBackend methods through resolve:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.tapCoordinates src/backends/index.ts:213:11
❯ src/backends/lazy-backend.test.ts:363:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > error propagation > allows retry after non-multi-device error:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:348:20
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > platform getter > returns resolved platform after connection:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("android", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:315:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > multiple device handling > selectDevice clears previous connection state:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:238:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > multiple device handling > resolves after selectDevice is called:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:225:20
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > single device resolution > passes explicitPlatform to detectPlatform:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("android", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:174:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > single device resolution > passes explicitDeviceId to detectPlatform:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("android", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:158:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > single device resolution > reuses backend across multiple calls:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:143:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > single device resolution > defers backend creation until first tool call:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:130:7
|
|
Build, lint, and test / Lint (24.x)
Process completed with exit code 1.
|
|
Build, lint, and test / Test (22.x)
The strategy configuration was canceled because "build-lint-test.test._24_x" failed
|
|
Build, lint, and test / Test (22.x)
The operation was canceled.
|
|
Build, lint, and test / Test (20.x)
The strategy configuration was canceled because "build-lint-test.test._24_x" failed
|
|
Build, lint, and test / Test (20.x)
The operation was canceled.
|
|
Build, lint, and test / Compatibility test (24.x)
Process completed with exit code 1.
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > delegate methods > delegates all DeviceBackend methods through resolve:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.tapCoordinates src/backends/index.ts:213:11
❯ src/backends/lazy-backend.test.ts:363:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > error propagation > allows retry after non-multi-device error:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:348:20
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > platform getter > returns resolved platform after connection:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("android", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:315:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > multiple device handling > selectDevice clears previous connection state:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:238:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > multiple device handling > resolves after selectDevice is called:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:225:20
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > single device resolution > passes explicitPlatform to detectPlatform:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("android", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:174:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > single device resolution > passes explicitDeviceId to detectPlatform:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("android", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:158:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > single device resolution > reuses backend across multiple calls:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:143:7
|
|
src/backends/lazy-backend.test.ts > createLazyBackend > single device resolution > defers backend creation until first tool call:
src/backends/index.ts#L97
TypeError: (deviceId) => ({
...createMockBackendFields("ios", deviceId),
ensureConnected: mockEnsureConnected
}) is not a constructor
❯ createBackend src/backends/index.ts:97:12
❯ Object.getDeviceInfo src/backends/index.ts:190:11
❯ src/backends/lazy-backend.test.ts:130:7
|
|
Build, lint, and test / Compatibility test (22.x)
The strategy configuration was canceled because "build-lint-test.compatibility-test._24_x" failed
|
|
Build, lint, and test / Compatibility test (22.x)
The operation was canceled.
|
|
Build, lint, and test / Compatibility test (20.x)
The strategy configuration was canceled because "build-lint-test.compatibility-test._24_x" failed
|
|
Build, lint, and test / Compatibility test (20.x)
The operation was canceled.
|
|
All jobs pass
Process completed with exit code 1.
|
|
Build, lint, and test / Prepare (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Prepare (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Check workflows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Prepare (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Analyse code / Setup
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 16th, 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/
|
|
Build, lint, and test / 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/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Build (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Lint (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Test (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Test (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Compatibility 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/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Compatibility test (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Analyse code / Semgrep analysis
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 will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build, lint, and test / Compatibility test (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Analyse code / CodeQL analysis (actions)
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 will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Analyse code / CodeQL analysis (javascript-typescript)
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 will be forced to run with Node.js 24 by default starting June 16th, 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/
|