build: update cross-repo angular dependencies (main) #12525
angular-robotpr.yml
on: pull_request
build
2m 9s
analyze
5s
build-e2e-windows-subset
2m 14s
lint
2m 14s
test
2m 8s
Matrix: e2e-package-managers
Matrix: e2e
Matrix: e2e-snapshots
e2e-windows-subset
3m 36s
Annotations
69 errors and 39 warnings
|
e2e (22, esbuild, 2)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, esbuild, 2)
The operation was canceled.
|
|
e2e-snapshots (22, esbuild, 1)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, webpack, 4)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, webpack, 4)
The operation was canceled.
|
|
e2e-snapshots (22, esbuild, 1)
The operation was canceled.
|
|
e2e-snapshots (22, webpack, 3)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, webpack, 3)
The operation was canceled.
|
|
e2e (22, webpack, 5)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, webpack, 5)
The operation was canceled.
|
|
e2e (22, esbuild, 4)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, esbuild, 4)
The operation was canceled.
|
|
e2e-snapshots (22, webpack, 0)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, webpack, 0)
The operation was canceled.
|
|
e2e-snapshots (22, webpack, 4)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, webpack, 4)
The operation was canceled.
|
|
e2e-snapshots (22, esbuild, 0)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, esbuild, 0)
The operation was canceled.
|
|
e2e (22, esbuild, 5)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, esbuild, 5)
The operation was canceled.
|
|
e2e-snapshots (22, esbuild, 2)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, esbuild, 2)
The operation was canceled.
|
|
e2e (22, webpack, 3)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, esbuild, 0)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, webpack, 3)
The operation was canceled.
|
|
e2e (22, esbuild, 0)
The operation was canceled.
|
|
e2e (22, esbuild, 1)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, esbuild, 1)
The operation was canceled.
|
|
e2e-package-managers (22, yarn, 2)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, yarn, 2)
The operation was canceled.
|
|
e2e-package-managers (22, pnpm, 2)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, esbuild, 5)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, pnpm, 2)
The operation was canceled.
|
|
e2e-snapshots (22, esbuild, 5)
The operation was canceled.
|
|
e2e (22, esbuild, 3)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, webpack, 1)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, esbuild, 3)
The operation was canceled.
|
|
e2e-snapshots (22, webpack, 1)
The operation was canceled.
|
|
e2e-package-managers (22, bun, 2)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, bun, 2)
The operation was canceled.
|
|
e2e-windows-subset
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, bun, 0)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, bun, 0)
The operation was canceled.
|
|
e2e-windows-subset
The operation was canceled.
|
|
e2e-snapshots (22, esbuild, 4)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, esbuild, 4)
The operation was canceled.
|
|
e2e (22, webpack, 2)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, yarn, 1)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, webpack, 2)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, webpack, 2)
The operation was canceled.
|
|
e2e-snapshots (22, webpack, 2)
The operation was canceled.
|
|
e2e-package-managers (22, yarn, 1)
The operation was canceled.
|
|
e2e-package-managers (22, yarn, 0)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, yarn, 0)
The operation was canceled.
|
|
e2e (22, webpack, 1)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, webpack, 1)
The operation was canceled.
|
|
e2e (22, webpack, 0)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e (22, webpack, 0)
The operation was canceled.
|
|
e2e-snapshots (22, esbuild, 3)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, esbuild, 3)
The operation was canceled.
|
|
e2e-package-managers (22, pnpm, 0)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, pnpm, 0)
The operation was canceled.
|
|
e2e-package-managers (22, bun, 1)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, bun, 1)
The operation was canceled.
|
|
e2e-package-managers (22, pnpm, 1)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-package-managers (22, pnpm, 1)
The operation was canceled.
|
|
e2e-snapshots (22, webpack, 5)
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
e2e-snapshots (22, webpack, 5)
The operation was canceled.
|
|
Pull Request
Canceling since a higher priority waiting request for Pull Request-refs/pull/32738/merge exists
|
|
analyze
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
build
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
build-e2e-windows-subset
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
test
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, esbuild, 2)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, esbuild, 1)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, webpack, 4)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, webpack, 3)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, webpack, 5)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, esbuild, 4)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, webpack, 0)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, webpack, 4)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, esbuild, 0)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, esbuild, 5)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, esbuild, 2)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, webpack, 3)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, esbuild, 0)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, esbuild, 1)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, yarn, 2)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, pnpm, 2)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, esbuild, 5)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, esbuild, 3)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, webpack, 1)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, bun, 2)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-windows-subset
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, bun, 0)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, esbuild, 4)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, webpack, 2)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, webpack, 2)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, yarn, 1)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, yarn, 0)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, webpack, 1)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e (22, webpack, 0)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, esbuild, 3)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, pnpm, 0)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, bun, 1)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-package-managers (22, pnpm, 1)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
|
e2e-snapshots (22, webpack, 5)
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@e030fa052f7f4356b23a706203dc8ea1ef764127, pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
packages
|
3.53 MB |
sha256:39e935d53b3ddd855f8de0ac46e3aa462afd346c0116836498228c838de010ee
|
|
|
win-e2e-build-artifacts
|
163 MB |
sha256:38b408b0d6086b883596afe22d09e805368efa3c53748d2a716f1454792d12ea
|
|