Update dependency xstate to v5 #2544
pull-requests.yml
on: pull_request
validate
/
branch
31s
lint
/
branch
41s
Matrix: upload / tarball
upload
/
win
46s
upload
/
macos
30s
upload
/
npm
34s
upload
/
shell
37s
Matrix: e2e-tests / tarball
Waiting for pending jobs
Matrix: integration-tests / brew
Waiting for pending jobs
Matrix: integration-tests / cicd-shell
Waiting for pending jobs
Matrix: integration-tests / standalone-shell
Waiting for pending jobs
Matrix: integration-tests / tarball
Waiting for pending jobs
integration-tests
/
macos
integration-tests
/
npm
integration-tests
/
proxy
integration-tests
/
win
github-actions-tests
/
mobile-build-upload
github-actions-tests
/
mobile-test-run
github-actions-tests
/
web-test-run
approved
4s
Annotations
23 errors and 26 warnings
|
lint / branch
Process completed with exit code 1.
|
|
lint / branch:
src/autify/mobile/mobilelink/mobile-link-manager/MobileLinkManager.ts#L9
Unable to resolve path to module 'xstate/lib/waitFor'
|
|
lint / branch:
src/autify/connect/client-manager/ClientManager.ts#L21
Unable to resolve path to module 'xstate/lib/waitFor'
|
|
upload / win
Process completed with exit code 1.
|
|
upload / npm:
src/autify/connect/client-manager/StateMachine.ts#L65
Property 'errors' does not exist on type 'AssignArgs<ClientStateMachineContext, { type: "FAIL"; error: Error; }, ClientStateMachineEvent, ProvidedActor>'.
|
|
upload / npm:
src/autify/connect/client-manager/StateMachine.ts#L64
'event' is possibly 'undefined'.
|
|
upload / npm:
src/autify/connect/client-manager/StateMachine.ts#L64
Property 'errors' does not exist on type 'AssignArgs<ClientStateMachineContext, { type: "FAIL"; error: Error; }, ClientStateMachineEvent, ProvidedActor>'.
|
|
upload / npm:
src/autify/connect/client-manager/StateMachine.ts#L46
Expected 11-12 type arguments, but got 3.
|
|
upload / npm:
src/autify/connect/client-manager/StateMachine.ts#L34
Type 'Interpreter' is not generic.
|
|
upload / npm:
src/autify/connect/client-manager/ClientManager.ts#L333
Parameter 'error' implicitly has an 'any' type.
|
|
upload / npm:
src/autify/connect/client-manager/ClientManager.ts#L316
Parameter 'state' implicitly has an 'any' type.
|
|
upload / npm:
src/autify/connect/client-manager/ClientManager.ts#L216
Parameter 'event' implicitly has an 'any' type.
|
|
upload / npm:
src/autify/connect/client-manager/ClientManager.ts#L216
Parameter 'state' implicitly has an 'any' type.
|
|
upload / npm:
src/autify/connect/client-manager/ClientManager.ts#L21
Cannot find module 'xstate/lib/waitFor' or its corresponding type declarations.
|
|
upload / tarball (linux-x64)
Process completed with exit code 1.
|
|
upload / tarball (darwin-arm64)
Process completed with exit code 1.
|
|
upload / tarball (linux-arm)
Process completed with exit code 1.
|
|
upload / tarball (darwin-x64)
Process completed with exit code 1.
|
|
upload / tarball (linux-arm64)
Process completed with exit code 1.
|
|
upload / tarball (win32-x64)
Process completed with exit code 1.
|
|
upload / tarball (win32-x86)
Process completed with exit code 1.
|
|
upload / macos
Process completed with exit code 1.
|
|
approved
Process completed with exit code 1.
|
|
validate / branch
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/
|
|
validate / branch
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
lint / branch
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/
|
|
lint / branch
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / win
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, aws-actions/configure-aws-credentials@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/
|
|
upload / win
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / npm
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, aws-actions/configure-aws-credentials@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/
|
|
upload / npm
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / tarball (linux-x64)
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, aws-actions/configure-aws-credentials@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/
|
|
upload / tarball (linux-x64)
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / shell
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, aws-actions/configure-aws-credentials@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/
|
|
upload / shell
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / tarball (darwin-arm64)
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, aws-actions/configure-aws-credentials@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/
|
|
upload / tarball (darwin-arm64)
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / tarball (linux-arm)
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, aws-actions/configure-aws-credentials@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/
|
|
upload / tarball (linux-arm)
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / tarball (darwin-x64)
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, aws-actions/configure-aws-credentials@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/
|
|
upload / tarball (darwin-x64)
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / tarball (linux-arm64)
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, aws-actions/configure-aws-credentials@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/
|
|
upload / tarball (linux-arm64)
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / tarball (win32-x64)
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, aws-actions/configure-aws-credentials@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/
|
|
upload / tarball (win32-x64)
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / tarball (win32-x86)
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, aws-actions/configure-aws-credentials@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/
|
|
upload / tarball (win32-x86)
Both node-version and node-version-file inputs are specified, only node-version will be used
|
|
upload / macos
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, aws-actions/configure-aws-credentials@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/
|
|
upload / macos
Both node-version and node-version-file inputs are specified, only node-version will be used
|