fix(@angular/build): remap metafile paths when workspace root is a symlink or junction #14915
clydinpr.yml
on: pull_request
build
4m 6s
analyze
6s
build-e2e-windows-subset
4m 23s
lint
2m 41s
test
10m 2s
Matrix: e2e-package-managers
Matrix: e2e
Matrix: e2e-snapshots
e2e-windows-subset
4m 22s
Annotations
1 error and 25 warnings
|
test
Process completed with exit code 3.
|
|
lint
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: angular/dev-infra/github-actions/bazel/configure-remote@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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
|
1.89 MB |
sha256:c4051ce464e6459d371f8bb578ee588722e5525914480b639f140712ea34cc5d
|
|
|
win-e2e-build-artifacts
Expired
|
174 MB |
sha256:ebc8fa84df709cffb26be47860ff04a1218bf246b2733dbec18634680cf2492a
|
|