fix(proxy): match the HMR upgrade path exactly like the ws server #7413
Annotations
67 errors, 35 warnings, and 16 notices
|
Lint - ubuntu-latest - Node vlts/*
Process completed with exit code 1.
|
|
Test - macos-latest - Node v22.x, Webpack latest (2/4)
Canceling since a higher priority waiting request for test-macos-latest-v22.x-latest-2/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v24.15, Webpack latest (4/4)
Canceling since a higher priority waiting request for test-macos-latest-v24.15-latest-4/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v20.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for test-macos-latest-v20.x-latest-3/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v24.15, Webpack latest (1/4)
Canceling since a higher priority waiting request for test-macos-latest-v24.15-latest-1/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v18.x, Webpack latest (2/4)
Canceling since a higher priority waiting request for test-macos-latest-v18.x-latest-2/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v22.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for test-macos-latest-v22.x-latest-3/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v18.x, Webpack latest (4/4)
Canceling since a higher priority waiting request for test-macos-latest-v18.x-latest-4/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v20.x, Webpack latest (1/4)
Canceling since a higher priority waiting request for test-macos-latest-v20.x-latest-1/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v24.15, Webpack latest (3/4)
Canceling since a higher priority waiting request for test-macos-latest-v24.15-latest-3/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v20.x, Webpack latest (4/4)
Canceling since a higher priority waiting request for test-macos-latest-v20.x-latest-4/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v20.x, Webpack latest (2/4)
Canceling since a higher priority waiting request for test-macos-latest-v20.x-latest-2/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v18.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for test-macos-latest-v18.x-latest-3/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v22.x, Webpack latest (1/4)
Canceling since a higher priority waiting request for test-macos-latest-v22.x-latest-1/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v24.15, Webpack latest (2/4)
Canceling since a higher priority waiting request for test-macos-latest-v24.15-latest-2/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v22.x, Webpack latest (1/4)
Canceling since a higher priority waiting request for test-windows-latest-v22.x-latest-1/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v22.x, Webpack latest (1/4)
The operation was canceled.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
Canceling since a higher priority waiting request for test-windows-latest-v18.x-latest-1/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
The operation was canceled.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v24.15, Webpack latest (1/4)
Canceling since a higher priority waiting request for test-windows-latest-v24.15-latest-1/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v24.15, Webpack latest (1/4)
The operation was canceled.
|
|
Test - windows-latest - Node v20.x, Webpack latest (2/4)
Canceling since a higher priority waiting request for test-windows-latest-v20.x-latest-2/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v20.x, Webpack latest (2/4)
The operation was canceled.
|
|
Test - windows-latest - Node v22.x, Webpack latest (4/4)
Canceling since a higher priority waiting request for test-windows-latest-v22.x-latest-4/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v22.x, Webpack latest (4/4)
The operation was canceled.
|
|
Test - windows-latest - Node v24.15, Webpack latest (4/4)
Canceling since a higher priority waiting request for test-windows-latest-v24.15-latest-4/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for test-windows-latest-v18.x-latest-3/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
The operation was canceled.
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
Canceling since a higher priority waiting request for test-windows-latest-v18.x-latest-4/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
The operation was canceled.
|
|
Test - windows-latest - Node v24.15, Webpack latest (4/4)
The operation was canceled.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v20.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for test-windows-latest-v20.x-latest-3/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v20.x, Webpack latest (3/4)
The operation was canceled.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
Canceling since a higher priority waiting request for test-windows-latest-v18.x-latest-2/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
The operation was canceled.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v24.15, Webpack latest (2/4)
Canceling since a higher priority waiting request for test-windows-latest-v24.15-latest-2/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v24.15, Webpack latest (2/4)
The operation was canceled.
|
|
Test - windows-latest - Node v24.15, Webpack latest (3/4)
Canceling since a higher priority waiting request for test-windows-latest-v24.15-latest-3/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v24.15, Webpack latest (3/4)
The operation was canceled.
|
|
Test - windows-latest - Node v20.x, Webpack latest (1/4)
Canceling since a higher priority waiting request for test-windows-latest-v20.x-latest-1/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v20.x, Webpack latest (1/4)
The operation was canceled.
|
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
Canceling since a higher priority waiting request for test-windows-latest-v22.x-latest-2/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
The operation was canceled.
|
|
Test - windows-latest - Node v22.x, Webpack latest (3/4)
Canceling since a higher priority waiting request for test-windows-latest-v22.x-latest-3/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v22.x, Webpack latest (3/4)
The operation was canceled.
|
|
Test - windows-latest - Node v20.x, Webpack latest (4/4)
Canceling since a higher priority waiting request for test-windows-latest-v20.x-latest-4/4-refs/pull/5678/merge exists
|
|
Test - windows-latest - Node v20.x, Webpack latest (4/4)
The operation was canceled.
|
|
Test - macos-latest - Node v22.x, Webpack latest (4/4)
Canceling since a higher priority waiting request for test-macos-latest-v22.x-latest-4/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v22.x, Webpack latest (4/4)
The operation was canceled.
|
|
Test - macos-latest - Node v18.x, Webpack latest (1/4)
Canceling since a higher priority waiting request for test-macos-latest-v18.x-latest-1/4-refs/pull/5678/merge exists
|
|
Test - macos-latest - Node v18.x, Webpack latest (1/4)
The operation was canceled.
|
|
Lint - ubuntu-latest - Node vlts/*
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/
|
|
Test - ubuntu-latest - Node v24.15, Webpack latest (2/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest (2/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest (2/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest (2/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v24.15, Webpack latest (4/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest (4/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest (4/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest (4/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v24.15, Webpack latest (3/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v24.15, Webpack latest (1/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest (1/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest (3/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest (3/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest (3/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest (1/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest (1/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v22.x, Webpack latest (1/4)
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/
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
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/
|
|
Test - windows-latest - Node v24.15, Webpack latest (1/4)
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/
|
|
Test - windows-latest - Node v20.x, Webpack latest (2/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v22.x, Webpack latest (4/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v24.15, Webpack latest (4/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v20.x, Webpack latest (3/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v24.15, Webpack latest (2/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v24.15, Webpack latest (3/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v20.x, Webpack latest (1/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v22.x, Webpack latest (3/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - windows-latest - Node v20.x, Webpack latest (4/4)
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, 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/
|
|
Test - macos-latest - Node v22.x, Webpack latest (4/4)
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/
|
|
Test - macos-latest - Node v18.x, Webpack latest (1/4)
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/
|
|
Test - windows-latest - Node v22.x, Webpack latest (1/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v24.15, Webpack latest (1/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v20.x, Webpack latest (2/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v22.x, Webpack latest (4/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v24.15, Webpack latest (4/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v20.x, Webpack latest (3/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v24.15, Webpack latest (2/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v24.15, Webpack latest (3/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v20.x, Webpack latest (1/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v22.x, Webpack latest (3/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test - windows-latest - Node v20.x, Webpack latest (4/4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|