fix: use matchResource for importModule when available (#1162) #1143
Annotations
77 errors and 29 warnings
|
Test - ubuntu-latest - Node v22.x, Webpack latest, old API
Process completed with exit code 1.
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest, old API:
src/loader.js#L364
Object is possibly 'undefined'.
|
|
Test - macos-latest - Node v14.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Lint - ubuntu-latest - Node vlts/*
Process completed with exit code 1.
|
|
Lint - ubuntu-latest - Node vlts/*:
src/loader.js#L364
Object is possibly 'undefined'.
|
|
Test - macos-latest - Node v24.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - macos-latest - Node v18.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - macos-latest - Node v16.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - macos-latest - Node v12.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - macos-latest - Node v22.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - macos-latest - Node v20.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - macos-latest - Node v20.x, Webpack latest, old API
A task was canceled.
|
|
Test - windows-latest - Node v14.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - windows-latest - Node v14.x, Webpack latest, old API
The operation was canceled.
|
|
Test - windows-latest - Node v16.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - windows-latest - Node v16.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest, old API:
src/loader.js#L364
Object is possibly 'undefined'.
|
|
Test - windows-latest - Node v18.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - windows-latest - Node v18.x, Webpack latest, old API
The operation was canceled.
|
|
Test - windows-latest - Node v12.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - windows-latest - Node v12.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v24.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - ubuntu-latest - Node v24.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v24.x, Webpack latest, old API:
src/loader.js#L364
Object is possibly 'undefined'.
|
|
Test - windows-latest - Node v20.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - windows-latest - Node v20.x, Webpack latest, old API
The operation was canceled.
|
|
Test - windows-latest - Node v22.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - windows-latest - Node v22.x, Webpack latest, old API
The operation was canceled.
|
|
Test - windows-latest - Node v24.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - windows-latest - Node v24.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v16.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - ubuntu-latest - Node v16.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v12.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - ubuntu-latest - Node v12.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v14.x, Webpack latest, old API
The strategy configuration was canceled because "test-old-api.ubuntu-latest_22_x" failed
|
|
Test - ubuntu-latest - Node v14.x, Webpack latest, old API
The operation was canceled.
|
|
Test - ubuntu-latest - Node v24.x, Webpack latest
Process completed with exit code 1.
|
|
Test - ubuntu-latest - Node v24.x, Webpack latest:
src/loader.js#L364
Object is possibly 'undefined'.
|
|
Test - macos-latest - Node v20.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - macos-latest - Node v22.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - macos-latest - Node v12.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - macos-latest - Node v24.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - macos-latest - Node v16.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - macos-latest - Node v18.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - macos-latest - Node v14.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - windows-latest - Node v12.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - windows-latest - Node v12.x, Webpack latest
The operation was canceled.
|
|
Test - windows-latest - Node v20.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - windows-latest - Node v20.x, Webpack latest
The operation was canceled.
|
|
Test - ubuntu-latest - Node v12.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - ubuntu-latest - Node v12.x, Webpack latest
The operation was canceled.
|
|
Test - windows-latest - Node v16.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - windows-latest - Node v16.x, Webpack latest
The operation was canceled.
|
|
Test - windows-latest - Node v24.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - windows-latest - Node v24.x, Webpack latest
The operation was canceled.
|
|
Test - windows-latest - Node v14.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - windows-latest - Node v14.x, Webpack latest
The operation was canceled.
|
|
Test - windows-latest - Node v18.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - windows-latest - Node v18.x, Webpack latest
The operation was canceled.
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest
The operation was canceled.
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest:
src/loader.js#L364
Object is possibly 'undefined'.
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest
The operation was canceled.
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest:
src/loader.js#L364
Object is possibly 'undefined'.
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest
The operation was canceled.
|
|
Test - windows-latest - Node v22.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - windows-latest - Node v22.x, Webpack latest
The operation was canceled.
|
|
Test - ubuntu-latest - Node v14.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - ubuntu-latest - Node v14.x, Webpack latest
The operation was canceled.
|
|
Test - ubuntu-latest - Node v16.x, Webpack latest
The strategy configuration was canceled because "test.ubuntu-latest_24_x_latest" failed
|
|
Test - ubuntu-latest - Node v16.x, Webpack latest
The operation was canceled.
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint - 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 2nd, 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 v14.x, Webpack latest, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v16.x, Webpack latest, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v12.x, Webpack latest, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.x, Webpack latest, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.x, Webpack latest, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v16.x, Webpack latest, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v12.x, Webpack latest, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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, old API
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v14.x, Webpack latest, old API
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@v7, 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/
|
|
Test - ubuntu-latest - Node v24.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v12.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v12.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v16.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v14.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
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@v7, 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/
|
|
Test - ubuntu-latest - Node v18.x, Webpack latest
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@v7, 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/
|
|
Test - windows-latest - Node v22.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v14.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 v16.x, Webpack latest
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@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|