Skip to content

ng add fails to detect schematics on first run with private package registries #28085

ng add fails to detect schematics on first run with private package registries

ng add fails to detect schematics on first run with private package registries #28085

Triggered via issue April 28, 2026 03:36
Status Failure
Total duration 11s
Artifacts

dev-infra.yml

on: issues
labels
0s
labels
post_approval_changes
0s
post_approval_changes
issue_labels
9s
issue_labels
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
issue_labels
ApiError: {"error":{"code":429,"message":"Resource exhausted. Please try again later. Please refer to https://cloud.google.com/vertex-ai/generative-ai/docs/error-code-429 for more details.","status":"RESOURCE_EXHAUSTED"}}
issue_labels
Failed to generate content from Gemini.
issue_labels
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/labeling/issue@ba726e7bca0b08b125ccc6f93c233749e1213c17. 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/