release: cut the v21.2.5 release #2231
ci.yml
on: push
lint
2m 7s
api_golden_checks
25s
e2e
21s
integration
23s
test
0s
build
0s
publish_snapshots
0s
deploy_doc_site
0s
browserstack
53s
Annotations
6 errors and 3 warnings
|
browserstack
Process completed with exit code 1.
|
|
publish_snapshots
Canceling since a higher priority waiting request for CI-refs/heads/21.2.x exists
|
|
CI
Canceling since a higher priority waiting request for CI-refs/heads/21.2.x exists
|
|
test
Canceling since a higher priority waiting request for CI-refs/heads/21.2.x exists
|
|
build
Canceling since a higher priority waiting request for CI-refs/heads/21.2.x exists
|
|
deploy_doc_site
Canceling since a higher priority waiting request for CI-refs/heads/21.2.x exists
|
|
e2e
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: angular/dev-infra/github-actions/bazel/configure-remote@a3baba2402ef0efd781913544a5bbc13a51a1bc8. 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/
|
|
integration
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: angular/dev-infra/github-actions/bazel/configure-remote@a3baba2402ef0efd781913544a5bbc13a51a1bc8. 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/
|
|
api_golden_checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: angular/dev-infra/github-actions/bazel/configure-remote@a3baba2402ef0efd781913544a5bbc13a51a1bc8. 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/
|