jwdb's PR is being checked. #291
bluewwPrValidation.yml
on: pull_request
BlobTest_Ubuntu_Node16
36s
BlobTest_Ubuntu_Node18
33s
BlobTest_Ubuntu_Node20
30s
BlobTest_Ubuntu_Node22
35s
BlobTest_Win_Node20
1m 6s
BlobTest_Win_Node18
59s
BlobTest_MacOS_Node16
1m 3s
BlobTest_MacOS_Node22
44s
BlobTest_MySQL_Ubuntu_Node22
30s
BlobTest_MySQL_Ubuntu_Node16
34s
QueueTest_Ubuntu_Node22
34s
QueueTest_Ubuntu_Node20
33s
QueueTest_Win_Node16
1m 25s
QueueTest_Win_Node18
1m 14s
QueueTest_MacOS_Node20
44s
QueueTest_MacOS_Node18
56s
TableTest_Ubuntu_Node22
34s
TableTest_Ubuntu_Node16
39s
TableTest_Win_Node20
2m 56s
TableTest_Win_Node16
1m 16s
TableTest_MacOS_Node20
1m 0s
TableTest_MacOS_Node18
58s
Azurite_Linux_Node18
32s
Azurite_Linux_Node16
36s
Azurite_Win_Node22
1m 19s
Azurite_Win_Node20
1m 9s
Azurite_Mac_Node20
52s
Azurite_Mac_Node16
1m 2s
Azurite_Docker
31s
Azurite_Windows_Docker
1m 14s
Azurite_ExeTest
1m 7s
Azurite_LinuxBinaryTest
33s
Annotations
61 errors and 32 warnings
|
BlobTest_Ubuntu_Node20
Process completed with exit code 2.
|
|
BlobTest_Ubuntu_Node20:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_MySQL_Ubuntu_Node22
Process completed with exit code 2.
|
|
BlobTest_MySQL_Ubuntu_Node22:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_Linux_Node18
Process completed with exit code 2.
|
|
Azurite_Linux_Node18:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
QueueTest_Ubuntu_Node20
Process completed with exit code 2.
|
|
QueueTest_Ubuntu_Node20:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_Docker
Process completed with exit code 2.
|
|
QueueTest_Ubuntu_Node22
Process completed with exit code 2.
|
|
QueueTest_Ubuntu_Node22:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_Ubuntu_Node18
Process completed with exit code 2.
|
|
BlobTest_Ubuntu_Node18:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_LinuxBinaryTest
Process completed with exit code 2.
|
|
Azurite_LinuxBinaryTest:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
TableTest_Ubuntu_Node22
Process completed with exit code 2.
|
|
TableTest_Ubuntu_Node22:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_MySQL_Ubuntu_Node16
Process completed with exit code 2.
|
|
BlobTest_MySQL_Ubuntu_Node16:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_Ubuntu_Node22
Process completed with exit code 1.
|
|
BlobTest_Ubuntu_Node16
Process completed with exit code 2.
|
|
BlobTest_Ubuntu_Node16:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_Linux_Node16
Process completed with exit code 2.
|
|
Azurite_Linux_Node16:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
TableTest_Ubuntu_Node16
Process completed with exit code 2.
|
|
TableTest_Ubuntu_Node16:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
QueueTest_MacOS_Node20
Process completed with exit code 2.
|
|
BlobTest_MacOS_Node22
Process completed with exit code 2.
|
|
QueueTest_MacOS_Node20:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_MacOS_Node22:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_Mac_Node20
Process completed with exit code 2.
|
|
Azurite_Mac_Node20:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
QueueTest_MacOS_Node18
Process completed with exit code 2.
|
|
QueueTest_MacOS_Node18:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
TableTest_MacOS_Node18
Process completed with exit code 2.
|
|
TableTest_MacOS_Node18:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_Win_Node18
Process completed with exit code 1.
|
|
BlobTest_Win_Node18:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
TableTest_MacOS_Node20
Process completed with exit code 2.
|
|
TableTest_MacOS_Node20:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_Mac_Node16
Process completed with exit code 2.
|
|
Azurite_Mac_Node16:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_MacOS_Node16
Process completed with exit code 2.
|
|
BlobTest_MacOS_Node16:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_Win_Node20
Process completed with exit code 1.
|
|
BlobTest_Win_Node20:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_ExeTest
Process completed with exit code 1.
|
|
Azurite_ExeTest:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_Win_Node20
Process completed with exit code 1.
|
|
Azurite_Win_Node20:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_Windows_Docker
Process completed with exit code 1.
|
|
QueueTest_Win_Node18
Process completed with exit code 1.
|
|
QueueTest_Win_Node18:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
TableTest_Win_Node16
Process completed with exit code 1.
|
|
TableTest_Win_Node16:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
Azurite_Win_Node22
Process completed with exit code 1.
|
|
Azurite_Win_Node22:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
QueueTest_Win_Node16
Process completed with exit code 1.
|
|
QueueTest_Win_Node16:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
TableTest_Win_Node20
Process completed with exit code 1.
|
|
TableTest_Win_Node20:
tests/table/KeepAlive/tableKeepAliveTimeout.test.ts#L12
Cannot find module '@azure/core-client/types/latest/core-client' or its corresponding type declarations.
|
|
BlobTest_Ubuntu_Node20
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/
|
|
BlobTest_MySQL_Ubuntu_Node22
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/
|
|
Azurite_Linux_Node18
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/
|
|
QueueTest_Ubuntu_Node20
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/
|
|
Azurite_Docker
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 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/
|
|
QueueTest_Ubuntu_Node22
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/
|
|
BlobTest_Ubuntu_Node18
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/
|
|
Azurite_LinuxBinaryTest
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/
|
|
TableTest_Ubuntu_Node22
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/
|
|
BlobTest_MySQL_Ubuntu_Node16
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/
|
|
BlobTest_Ubuntu_Node22
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/
|
|
BlobTest_Ubuntu_Node16
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/
|
|
Azurite_Linux_Node16
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/
|
|
TableTest_Ubuntu_Node16
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/
|
|
BlobTest_MacOS_Node22
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/
|
|
QueueTest_MacOS_Node20
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/
|
|
Azurite_Mac_Node20
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/
|
|
QueueTest_MacOS_Node18
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/
|
|
TableTest_MacOS_Node18
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/
|
|
BlobTest_Win_Node18
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/
|
|
TableTest_MacOS_Node20
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/
|
|
Azurite_Mac_Node16
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/
|
|
BlobTest_MacOS_Node16
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/
|
|
BlobTest_Win_Node20
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/
|
|
Azurite_ExeTest
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/
|
|
Azurite_Win_Node20
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/
|
|
Azurite_Windows_Docker
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 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/
|
|
QueueTest_Win_Node18
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/
|
|
TableTest_Win_Node16
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/
|
|
Azurite_Win_Node22
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/
|
|
QueueTest_Win_Node16
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/
|
|
TableTest_Win_Node20
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/
|