refactor: remove @angular-devkit/core logger and its dependencies f…
#1777
Annotations
9 errors and 6 warnings
|
workflow (build-unit-tests)
google-github-actions/auth failed with: failed to generate Google Cloud federated token for //iam.googleapis.com/projects/823469418460/locations/global/workloadIdentityPools/measurables-tracking/providers/angular: {"error":"unauthorized_client","error_description":"The given credential is rejected by the attribute condition."}
|
|
workflow (devkit-core-tests)
The strategy configuration was canceled because "workflow.build-unit-tests" failed
|
|
workflow (devkit-core-tests)
google-github-actions/auth failed with: failed to generate Google Cloud federated token for //iam.googleapis.com/projects/823469418460/locations/global/workloadIdentityPools/measurables-tracking/providers/angular: {"error":"unauthorized_client","error_description":"The given credential is rejected by the attribute condition."}
|
|
workflow (build-cli)
The strategy configuration was canceled because "workflow.build-unit-tests" failed
|
|
workflow (build-cli)
google-github-actions/auth failed with: failed to generate Google Cloud federated token for //iam.googleapis.com/projects/823469418460/locations/global/workloadIdentityPools/measurables-tracking/providers/angular: {"error":"unauthorized_client","error_description":"The given credential is rejected by the attribute condition."}
|
|
workflow (devkit-core-tests-rerun)
The strategy configuration was canceled because "workflow.build-unit-tests" failed
|
|
workflow (devkit-core-tests-rerun)
google-github-actions/auth failed with: failed to generate Google Cloud federated token for //iam.googleapis.com/projects/823469418460/locations/global/workloadIdentityPools/measurables-tracking/providers/angular: {"error":"unauthorized_client","error_description":"The given credential is rejected by the attribute condition."}
|
|
workflow (modules-builder-tests)
The strategy configuration was canceled because "workflow.build-unit-tests" failed
|
|
workflow (modules-builder-tests)
The operation was canceled.
|
|
list
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
workflow (build-unit-tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
workflow (devkit-core-tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
workflow (build-cli)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
workflow (devkit-core-tests-rerun)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|
|
workflow (modules-builder-tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
|