chore(deps): update dependency @types/node to v22.19.17 #2404
Annotations
16 errors and 9 warnings
|
Build and Test on Node.js v20.x on ubuntu-latest
Process completed with exit code 1.
|
|
Build and Test on Node.js v22.x on ubuntu-latest
Process completed with exit code 1.
|
|
Build and Test on Node.js v18.x on macOS-latest
The strategy configuration was canceled because "build-test._20_x_ubuntu-latest" failed
|
|
Build and Test on Node.js v18.x on macOS-latest
The operation was canceled.
|
|
Build and Test on Node.js v20.x on macOS-latest
The strategy configuration was canceled because "build-test._20_x_ubuntu-latest" failed
|
|
Build and Test on Node.js v20.x on macOS-latest
The operation was canceled.
|
|
Build and Test on Node.js v18.x on ubuntu-latest
The strategy configuration was canceled because "build-test._20_x_ubuntu-latest" failed
|
|
Build and Test on Node.js v18.x on ubuntu-latest
The operation was canceled.
|
|
Build and Test on Node.js v22.x on macOS-latest
The strategy configuration was canceled because "build-test._20_x_ubuntu-latest" failed
|
|
Build and Test on Node.js v22.x on macOS-latest
The operation was canceled.
|
|
Build and Test on Node.js v20.x on windows-latest
The strategy configuration was canceled because "build-test._20_x_ubuntu-latest" failed
|
|
Build and Test on Node.js v20.x on windows-latest
The operation was canceled.
|
|
Build and Test on Node.js v22.x on windows-latest
The strategy configuration was canceled because "build-test._20_x_ubuntu-latest" failed
|
|
Build and Test on Node.js v22.x on windows-latest
The operation was canceled.
|
|
Build and Test on Node.js v18.x on windows-latest
The strategy configuration was canceled because "build-test._20_x_ubuntu-latest" failed
|
|
Build and Test on Node.js v18.x on windows-latest
The operation was canceled.
|
|
Build and Test on Node.js v20.x on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|
|
Build and Test on Node.js v22.x on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|
|
Build and Test on Node.js v18.x on macOS-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|
|
Build and Test on Node.js v20.x on macOS-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|
|
Build and Test on Node.js v18.x on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|
|
Build and Test on Node.js v22.x on macOS-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|
|
Build and Test on Node.js v20.x on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|
|
Build and Test on Node.js v22.x on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|
|
Build and Test on Node.js v18.x on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46. 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/
|