Skip to content

fix(@angular/ssr): add support for configuring trusted proxy headers via environment variable #14175

fix(@angular/ssr): add support for configuring trusted proxy headers via environment variable

fix(@angular/ssr): add support for configuring trusted proxy headers via environment variable #14175

Re-run triggered May 29, 2026 20:36
Status Success
Total duration 8m 33s
Artifacts 1

pr.yml

on: pull_request
Matrix: e2e-package-managers
Matrix: e2e
Matrix: e2e-snapshots
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 1 notice
e2e-package-managers (ubuntu-latest, 22, yarn, 0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, angular/dev-infra/github-actions/bazel/configure-remote@1f047e7dbae43ea969c2cafb53b33207e86b800f, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Skipped setting up Bazel RBE
No credential was provided.