Skip to content

fix: add compile dependency to test:command-reference tasks #1646

fix: add compile dependency to test:command-reference tasks

fix: add compile dependency to test:command-reference tasks #1646

Triggered via push June 3, 2026 17:31
Status Failure
Total duration 4m 16s
Artifacts

test.yml

on: push
yarn-lockfile-check  /  lockfile-check
9s
yarn-lockfile-check / lockfile-check
linux-unit-tests  /  determine-node-versions
7s
linux-unit-tests / determine-node-versions
linux-unit-tests  /  ...  /  prevent-typescript-dependency
21s
linux-unit-tests / prevent-typescript-dependency / prevent-typescript-dependency
Matrix: linux-unit-tests / linux-unit-tests
windows-unit-tests  /  determine-node-versions
windows-unit-tests / determine-node-versions
Matrix: windows-unit-tests / windows-unit-tests
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 9 warnings, and 1 notice
linux-unit-tests / linux-unit-tests (24.16.0)
Final attempt failed. Child_process exited with error code 1
linux-unit-tests / linux-unit-tests (22)
Final attempt failed. Child_process exited with error code 1
yarn-lockfile-check / lockfile-check
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/
linux-unit-tests / determine-node-versions
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
linux-unit-tests / prevent-typescript-dependency / prevent-typescript-dependency
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/
linux-unit-tests / linux-unit-tests (24.16.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, nick-fields/retry@3f757583fb1b1f940bc8ef4bf4734c8dc02a5847. 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/
linux-unit-tests / linux-unit-tests (24.16.0)
Attempt 2 failed. Reason: Child_process exited with error code 1
linux-unit-tests / linux-unit-tests (24.16.0)
Attempt 1 failed. Reason: Child_process exited with error code 1
linux-unit-tests / linux-unit-tests (22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, nick-fields/retry@3f757583fb1b1f940bc8ef4bf4734c8dc02a5847. 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/
linux-unit-tests / linux-unit-tests (22)
Attempt 2 failed. Reason: Child_process exited with error code 1
linux-unit-tests / linux-unit-tests (22)
Attempt 1 failed. Reason: Child_process exited with error code 1
linux-unit-tests / determine-node-versions
Node version 26 is disabled via env var