Skip to content

[stable32] Fix npm audit #5051

[stable32] Fix npm audit

[stable32] Fix npm audit #5051

Triggered via pull request April 19, 2026 04:14
Status Success
Total duration 1h 15m 38s
Artifacts

cypress-e2e.yml

on: pull_request
Matrix: init
Matrix: cypress
cypress-summary
6s
cypress-summary
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
init (stable32)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0RV7kaQAAAACWmwO5ken7RLjBpQwvGfElRFVTMzBFREdFMDgyMABFZGdl
init (stable32)
Failed to restore: Cache service responded with 400
runner 7
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. 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/
runner 6
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. 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/
runner 3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. 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/
runner 4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. 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/
runner 2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. 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/
runner 1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@3e70d19e31d6a8030aeddf6ed8dbe601f94d09f4, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1. 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/