ci: include nvm manager in renovate post-upgrade tasks #9051
alan-agius4Annotations
11 errors and 5 warnings
|
rules_sass
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
rules_sass
The operation was canceled.
|
|
rules_browsers/test
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
rules_browsers/test
The operation was canceled.
|
|
rules_angular
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
rules_angular
The operation was canceled.
|
|
rules_browsers
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
rules_browsers
The operation was canceled.
|
|
dev-infra
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
dev-infra
The operation was canceled.
|
|
CI
Canceling since a higher priority waiting request for CI-refs/heads/main exists
|
|
rules_sass
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./github-actions/bazel/configure-remote. 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/
|
|
rules_browsers/test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./github-actions/bazel/configure-remote. 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/
|
|
rules_angular
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./github-actions/bazel/configure-remote. 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/
|
|
rules_browsers
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./github-actions/bazel/configure-remote. 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/
|
|
dev-infra
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./github-actions/bazel/configure-remote. 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/
|