Skip to content

chore(deps): update dependency tmp to v0.2.4 [security] #137

chore(deps): update dependency tmp to v0.2.4 [security]

chore(deps): update dependency tmp to v0.2.4 [security] #137

Triggered via pull request March 31, 2026 08:37
Status Failure
Total duration 2m 47s
Artifacts

test.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
Test - windows-latest - Node v22.x)
Process completed with exit code 1.
sri-plugin/examples.test.js > sri-plugin/examples/webpack > lazy-e2e/webpack: 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"%3A1774946391832%2C"pid"%3A4276%2C"hostname"%3A"runnervm3zftq"%2C"msg"%3A"Server listening at http%3A//[%3A%3A1]%3A50292"} (node%3A4276) [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 7504 (child process of PID 5772) could not be terminated. Reason%3A There is no running instance of the task. ERROR%3A The process with PID 1112 (child process of PID 5772) could not be terminated. Reason%3A There is no running instance of the task.
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/