See associated pull request for more information.

(cherry picked from commit d0db51e)

Prior to this change, there was a flaw in its handling of the retry logic, specifically within the `setTimeout` block. The function had a recursive promise resolution problem and an incorrect handling of the rejected state.

(cherry picked from commit 0c0f89e)

Currently, we are getting a lot of flakes due to `accept4 failed 110` error, this commit tries to reduce this by reducing the batching

(cherry picked from commit 0371781)

Two E2E tests have been added to test initial capabilities of the
experimental unit-test builder with the vitest runner. This also ensures
that the generated tests are compatible with both the karma/jasmine-based
runner and the vitest runner.

(cherry picked from commit 43a3111)

This approach has been recommanded by a Node.js member in nodejs/help#5063 (comment)

Closes #30821

(cherry picked from commit 1a01e18)

This approach has been recommanded by a Node.js member in nodejs/help#5063 (comment)

Closes #30821

(cherry picked from commit dd90a81)

…ray and has an enum

This commit enhances the command-line parser in `@angular/cli` by adding support for displaying available choices when a command option is of type `array` and has an `enum`.

(cherry picked from commit 04094e8)

This improves the prompt wording and adds more context.

(cherry picked from commit 1feac5f)

This commit includes minor changes to how analytics are handled, including:

- Removing unnecessary type castings.
- Concatenating arrays into strings for Google Analytics, as it doesn't support arrays.
- Applying default values to multi-select prompts for a smoother user experience.

(cherry picked from commit aace49e)

This commit fixes an issue where the `default` option was not being applied to `array` type options in yargs.

This seemingly minor change required refactoring in some tests, which revealed that a `.coerce` validation was incorrectly throwing an error on failure. The validation logic was moved to a `.check` to ensure proper error handling and prevent unexpected failures.

(cherry picked from commit c3789e4)

This commit fixes the Node.js toolchain setup that is needed for bazel modules.

The error message now will contain the changes.

…ock` data

This file was missing from the data

(cherry picked from commit 2a94e21)

The angular.dev documenation now uses `main` elements within each page to
indicate the actual content. To reduce the amount of HTML passed back in
the MCP `search_documentation` tool, only the `main` element is now used
instead of the entire `body` element.

(cherry picked from commit f88fd74)

…sfulNavigation` breaking changing"

This reverts commit 2fde130.

…f78982

This contains a fix for updating the bazel lock file during the release, which otherwise would cause the build and CI to break.

See: angular/dev-infra#2975

`20.2` is no longer is pre-release.