chore(deps): update all non-major dependencies #130
Annotations
10 errors and 3 warnings
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > terser-banner/rspack:
sri-plugin/examples.test.js#L54
test timed out in 60000ms (no expect assertions completed)
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > webpack-preload/rspack:
file:///D:/a/rspack-plugin-ci/rspack-plugin-ci/node_modules/.pnpm/puppeteer-core@24.40.0/node_modules/puppeteer-core/lib/esm/puppeteer/node/BrowserLauncher.js#L139
child process exited with code 2%3A (node%3A3156) [FST_MODULE_DEP_FASTIFY-STATIC] FastifyWarning.fastify-static%3A fastify-static has been deprecated. Use @fastify/static@5.0.0 instead.
(Use `node --trace-warnings ...` to show where the warning was created)
[rspack-cli] Error%3A The browser is already running for C%3A\Users\RUNNER~1\AppData\Local\Temp\puppeteer_dev_chrome_profile-E9hQTA. Use a different `userDataDir` or stop the running browser first.
at ChromeLauncher.launch (file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/node_modules/.pnpm/puppeteer-core@24.40.0/node_modules/puppeteer-core/lib/esm/puppeteer/node/BrowserLauncher.js%3A139%3A23)
at async testWithPuppeteer (file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js%3A89%3A19)
at async file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js%3A121%3A9
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > mini-css-extract-plugin/rspack:
file:///D:/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js#L56
child process exited with code 2%3A {"level"%3A30%2C"time"%3A1774665620518%2C"pid"%3A1520%2C"hostname"%3A"runnervm3zftq"%2C"msg"%3A"Server listening at http%3A//[%3A%3A1]%3A62900"}
(node%3A1520) [FST_MODULE_DEP_FASTIFY-STATIC] FastifyWarning.fastify-static%3A fastify-static has been deprecated. Use @fastify/static@5.0.0 instead.
(Use `node --trace-warnings ...` to show where the warning was created)
[rspack-cli] Error%3A Timeout loading page
at Timeout._onTimeout (file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js%3A56%3A14)
at listOnTimeout (node%3Ainternal/timers%3A585%3A17)
at process.processTimers (node%3Ainternal/timers%3A521%3A7)
ERROR%3A The process with PID 9248 (child process of PID 1100) could not be terminated.
Reason%3A There is no running instance of the task.
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > lazy-modified/rspack:
sri-plugin/examples.test.js#L54
test timed out in 60000ms (no expect assertions completed)
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > lazy-e2e/rspack:
sri-plugin/examples.test.js#L54
test timed out in 60000ms (no expect assertions completed)
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > issue-154/rspack:
file:///D:/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js#L56
child process exited with code 2%3A {"level"%3A30%2C"time"%3A1774665607485%2C"pid"%3A544%2C"hostname"%3A"runnervm3zftq"%2C"msg"%3A"Server listening at http%3A//[%3A%3A1]%3A54385"}
(node%3A544) [FST_MODULE_DEP_FASTIFY-STATIC] FastifyWarning.fastify-static%3A fastify-static has been deprecated. Use @fastify/static@5.0.0 instead.
(Use `node --trace-warnings ...` to show where the warning was created)
[rspack-cli] Error%3A Timeout loading page
at Timeout._onTimeout (file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js%3A56%3A14)
at listOnTimeout (node%3Ainternal/timers%3A585%3A17)
at process.processTimers (node%3Ainternal/timers%3A521%3A7)
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > dynamic-modified/rspack:
file:///D:/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js#L56
child process exited with code 2%3A {"level"%3A30%2C"time"%3A1774665589246%2C"pid"%3A4440%2C"hostname"%3A"runnervm3zftq"%2C"msg"%3A"Server listening at http%3A//[%3A%3A1]%3A50323"}
(node%3A4440) [FST_MODULE_DEP_FASTIFY-STATIC] FastifyWarning.fastify-static%3A fastify-static has been deprecated. Use @fastify/static@5.0.0 instead.
(Use `node --trace-warnings ...` to show where the warning was created)
[rspack-cli] Error%3A Timeout loading page
at Timeout._onTimeout (file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js%3A56%3A14)
at listOnTimeout (node%3Ainternal/timers%3A585%3A17)
at process.processTimers (node%3Ainternal/timers%3A521%3A7)
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > dynamic-named-chunks/rspack:
file:///D:/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js#L56
child process exited with code 2%3A {"level"%3A30%2C"time"%3A1774665584284%2C"pid"%3A8652%2C"hostname"%3A"runnervm3zftq"%2C"msg"%3A"Server listening at http%3A//[%3A%3A1]%3A50322"}
(node%3A8652) [FST_MODULE_DEP_FASTIFY-STATIC] FastifyWarning.fastify-static%3A fastify-static has been deprecated. Use @fastify/static@5.0.0 instead.
(Use `node --trace-warnings ...` to show where the warning was created)
[rspack-cli] Error%3A Timeout loading page
at Timeout._onTimeout (file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js%3A56%3A14)
at listOnTimeout (node%3Ainternal/timers%3A585%3A17)
at process.processTimers (node%3Ainternal/timers%3A521%3A7)
ERROR%3A The process with PID 3556 (child process of PID 1380) could not be terminated.
Reason%3A There is no running instance of the task.
ERROR%3A The process with PID 8176 (child process of PID 1380) could not be terminated.
Reason%3A There is no running instance of the task.
ERROR%3A The process with PID 9392 (child process of PID 1380) could not be terminated.
Reason%3A There is no running instance of the task.
ERROR%3A The process with PID 10636 (child process of PID 1380) could not be terminated.
Reason%3A There is no running instance of the task.
ERROR%3A The process with PID 6884 (child process of PID 1380) could not be terminated.
Reason%3A There is no running instance of the task.
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > dll-plugin/rspack:
file:///D:/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js#L56
child process exited with code 2%3A {"level"%3A30%2C"time"%3A1774665564398%2C"pid"%3A9668%2C"hostname"%3A"runnervm3zftq"%2C"msg"%3A"Server listening at http%3A//[%3A%3A1]%3A50320"}
(node%3A9668) [FST_MODULE_DEP_FASTIFY-STATIC] FastifyWarning.fastify-static%3A fastify-static has been deprecated. Use @fastify/static@5.0.0 instead.
(Use `node --trace-warnings ...` to show where the warning was created)
[rspack-cli] Error%3A Timeout loading page
at Timeout._onTimeout (file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js%3A56%3A14)
at listOnTimeout (node%3Ainternal/timers%3A585%3A17)
at process.processTimers (node%3Ainternal/timers%3A521%3A7)
ERROR%3A The process with PID 6308 (child process of PID 4292) could not be terminated.
Reason%3A There is no running instance of the task.
|
|
sri-plugin/examples.test.js > sri-plugin/examples/rspack > hwp-basic/rspack:
file:///D:/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js#L56
child process exited with code 2%3A {"level"%3A30%2C"time"%3A1774665564333%2C"pid"%3A9852%2C"hostname"%3A"runnervm3zftq"%2C"msg"%3A"Server listening at http%3A//[%3A%3A1]%3A50321"}
(node%3A9852) [FST_MODULE_DEP_FASTIFY-STATIC] FastifyWarning.fastify-static%3A fastify-static has been deprecated. Use @fastify/static@5.0.0 instead.
(Use `node --trace-warnings ...` to show where the warning was created)
[rspack-cli] Error%3A Timeout loading page
at Timeout._onTimeout (file%3A///D%3A/a/rspack-plugin-ci/rspack-plugin-ci/sri-plugin/examples/wsi-test-helper.js%3A56%3A14)
at listOnTimeout (node%3Ainternal/timers%3A585%3A17)
at process.processTimers (node%3Ainternal/timers%3A521%3A7)
|
|
Test - ubuntu-latest - Node v22.x)
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/
|
|
Test - macos-latest - Node v22.x)
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/
|
|
Test - windows-latest - Node v22.x)
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/
|