release: cut the v9.1.0 release

release: cut the v9.1.0-rc.2 release
fix(common): let KeyValuePipe accept type unions with null (#36093 )
2026-09-14 13:54:52 +08:00 · 2020-03-25 09:23:48 -07:00 · 2020-03-24 15:50:38 -07:00 · 2020-03-24 14:41:42 -07:00 · 2020-03-24 14:25:06 -07:00 · 2020-03-24 14:21:42 -07:00
15593 changed files with 848854 additions and 1255322 deletions
@@ -5,37 +5,93 @@
 .git
 node_modules
 dist
+aio/content
 aio/node_modules
 aio/tools/examples/shared/node_modules
-aio/tools/examples/shared/example-scaffold
-
+packages/bazel/node_modules
+integration/bazel/bazel-bazel
+integration/bazel/bazel-bin
+integration/bazel/bazel-out
+integration/bazel/bazel-testlogs
+integration/bazel-schematics/demo
 # All integration test node_modules folders
-integration/animations/node_modules
-integration/cli-elements-universal/node_modules
+integration/bazel/node_modules
+integration/bazel-schematics/node_modules
 integration/cli-hello-world/node_modules
+integration/cli-hello-world-ivy-compat/node_modules
 integration/cli-hello-world-ivy-i18n/node_modules
+integration/cli-hello-world-ivy-minimal/node_modules
 integration/cli-hello-world-lazy/node_modules
-integration/cli-hello-world-mocha/node_modules
-integration/cli-signal-inputs/node_modules
-integration/defer/node_modules
+integration/cli-hello-world-lazy-rollup/node_modules
 integration/dynamic-compiler/node_modules
-integration/forms/node_modules
+integration/hello_world__closure/node_modules
+integration/hello_world__systemjs_umd/node_modules
+integration/i18n/node_modules
 integration/injectable-def/node_modules
 integration/ivy-i18n/node_modules
-integration/ng-add-localize/node_modules
+integration/language_service_plugin/node_modules
 integration/ng_elements/node_modules
+integration/ng_elements_schematics/node_modules
 integration/ng_update/node_modules
 integration/ng_update_migrations/node_modules
-integration/nodenext_resolution/node_modules
-integration/npm_package_archives.bzl/node_modules
+integration/ngcc/node_modules
 integration/platform-server/node_modules
 integration/service-worker-schema/node_modules
 integration/side-effects/node_modules
-integration/standalone-bootstrap/node_modules
 integration/terser/node_modules
-integration/trusted-types/node_modules
-integration/typings_test_rxjs7/node_modules
-integration/typings_test_ts49/node_modules
-integration/typings_test_ts50/node_modules
-integration/typings_test_ts51/node_modules
-integration/typings_test_ts52/node_modules
+integration/typings_test_ts36/node_modules
+integration/typings_test_ts37/node_modules
+# All integration test .yarn_local_cache folders
+integration/bazel/.yarn_local_cache
+integration/bazel-schematics/.yarn_local_cache
+integration/cli-hello-world/.yarn_local_cache
+integration/cli-hello-world-ivy-compat/.yarn_local_cache
+integration/cli-hello-world-ivy-i18n/.yarn_local_cache
+integration/cli-hello-world-ivy-minimal/.yarn_local_cache
+integration/cli-hello-world-lazy/.yarn_local_cache
+integration/cli-hello-world-lazy-rollup/.yarn_local_cache
+integration/dynamic-compiler/.yarn_local_cache
+integration/hello_world__closure/.yarn_local_cache
+integration/hello_world__systemjs_umd/.yarn_local_cache
+integration/i18n/.yarn_local_cache
+integration/injectable-def/.yarn_local_cache
+integration/ivy-i18n/.yarn_local_cache
+integration/language_service_plugin/.yarn_local_cache
+integration/ng_elements/.yarn_local_cache
+integration/ng_elements_schematics/.yarn_local_cache
+integration/ng_update/.yarn_local_cache
+integration/ng_update_migrations/.yarn_local_cache
+integration/ngcc/.yarn_local_cache
+integration/platform-server/.yarn_local_cache
+integration/service-worker-schema/.yarn_local_cache
+integration/side-effects/.yarn_local_cache
+integration/terser/.yarn_local_cache
+integration/typings_test_ts36/.yarn_local_cache
+integration/typings_test_ts37/.yarn_local_cache
+# All integration test NPM_PACKAGE_MANIFEST.json folders
+integration/bazel/NPM_PACKAGE_MANIFEST.json
+integration/bazel-schematics/NPM_PACKAGE_MANIFEST.json
+integration/cli-hello-world/NPM_PACKAGE_MANIFEST.json
+integration/cli-hello-world-ivy-compat/NPM_PACKAGE_MANIFEST.json
+integration/cli-hello-world-ivy-i18n/NPM_PACKAGE_MANIFEST.json
+integration/cli-hello-world-ivy-minimal/NPM_PACKAGE_MANIFEST.json
+integration/cli-hello-world-lazy/NPM_PACKAGE_MANIFEST.json
+integration/cli-hello-world-lazy-rollup/NPM_PACKAGE_MANIFEST.json
+integration/dynamic-compiler/NPM_PACKAGE_MANIFEST.json
+integration/hello_world__closure/NPM_PACKAGE_MANIFEST.json
+integration/hello_world__systemjs_umd/NPM_PACKAGE_MANIFEST.json
+integration/i18n/NPM_PACKAGE_MANIFEST.json
+integration/injectable-def/NPM_PACKAGE_MANIFEST.json
+integration/ivy-i18n/NPM_PACKAGE_MANIFEST.json
+integration/language_service_plugin/NPM_PACKAGE_MANIFEST.json
+integration/ng_elements/NPM_PACKAGE_MANIFEST.json
+integration/ng_elements_schematics/NPM_PACKAGE_MANIFEST.json
+integration/ng_update/NPM_PACKAGE_MANIFEST.json
+integration/ng_update_migrations/NPM_PACKAGE_MANIFEST.json
+integration/ngcc/NPM_PACKAGE_MANIFEST.json
+integration/platform-server/NPM_PACKAGE_MANIFEST.json
+integration/service-worker-schema/NPM_PACKAGE_MANIFEST.json
+integration/side-effects/NPM_PACKAGE_MANIFEST.json
+integration/terser/NPM_PACKAGE_MANIFEST.json
+integration/typings_test_ts36/NPM_PACKAGE_MANIFEST.json
+integration/typings_test_ts37/NPM_PACKAGE_MANIFEST.json
@@ -1,9 +1,5 @@
 # Enable debugging tests with --config=debug
-test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test_strategy=exclusive --test_timeout=9999 --nocache_test_results --spawn_strategy=local
-
-# Do not attempt to de-flake locally.
-# On CI we might set this to `3` to run with deflaking.
-test --flaky_test_attempts=1
+test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test_strategy=exclusive --test_timeout=9999 --nocache_test_results

 ###############################
 # Filesystem interactions     #
@@ -37,13 +33,6 @@ build --incompatible_strict_action_env
 run --incompatible_strict_action_env
 test --incompatible_strict_action_env

-# Do not build runfile trees by default. If an execution strategy relies on runfile
-# symlink teee, the tree is created on-demand. See: https://github.com/bazelbuild/bazel/issues/6627
-# and https://github.com/bazelbuild/bazel/commit/03246077f948f2790a83520e7dccc2625650e6df
-build --nobuild_runfile_links
-
-build --enable_runfiles
-
 ###############################
 # Release support             #
 # Turn on these settings with #
@@ -53,35 +42,9 @@ build --enable_runfiles
 # Releases should always be stamped with version control info
 # This command assumes node on the path and is a workaround for
 # https://github.com/bazelbuild/bazel/issues/4802
-build:release --workspace_status_command="yarn -s ng-dev release build-env-stamp --mode=release"
+build:release --workspace_status_command="node ./tools/bazel_stamp_vars.js"
 build:release --stamp

-# Building AIO against local Angular deps requires stamping
-# versions in Angular packages due to CLI version checks.
-build:aio_local_deps --stamp
-build:aio_local_deps --workspace_status_command="yarn -s --cwd aio local-workspace-status"
-
-# Snapshots should also be stamped with version control information.
-build:snapshot-build --workspace_status_command="yarn -s ng-dev release build-env-stamp --mode=snapshot"
-build:snapshot-build --stamp
-
-##########################################################
-# AIO architect build configuration                      #
-# See aio/angular.json for available configurations.     #
-# To build with a partiular configuration:               #
-#   bazel build //aio:build --aio_build_config=<config>  #
-# Default config is `stable``.                           #
-##########################################################
-build --flag_alias=aio_build_config=//aio:flag_aio_build_config
-
-####################################
-# AIO first party dep substitution #
-# Turn on with                     #
-#  --config=aio_local_deps         #
-####################################
-
-build:aio_local_deps --//aio:flag_aio_local_deps
-
 ###############################
 # Output                      #
 ###############################
@@ -99,6 +62,26 @@ test --test_output=errors

 # Bazel flags for CircleCI are in /.circleci/bazel.linux.rc and /.circleci/bazel.windows.rc

+##################################
+# Settings for integration tests #
+##################################
+
+# Trick bazel into treating BUILD files under integration/bazel as being regular files
+# This lets us glob() up all the files inside this integration test to make them inputs to tests
+# (Note, we cannot use common --deleted_packages because the bazel version command doesn't support it)
+build --deleted_packages=integration/bazel,integration/bazel/src,integration/bazel/src/hello-world,integration/bazel/test,integration/bazel/test/e2e
+query --deleted_packages=integration/bazel,integration/bazel/src,integration/bazel/src/hello-world,integration/bazel/test,integration/bazel/test/e2e
+
+################################
+# Temporary Settings for Ivy   #
+################################
+# To determine if the compiler used should be Ivy instead of ViewEngine, one can use `--config=ivy`
+# on any bazel target. This is a temporary flag until codebase is permanently switched to Ivy.
+build --define=angular_ivy_enabled=False
+
+build:view-engine --define=angular_ivy_enabled=False
+build:ivy --define=angular_ivy_enabled=True
+
 ##################################
 # Remote Build Execution support #
 # Turn on these settings with    #
@@ -112,55 +95,32 @@ build:remote --define=EXECUTOR=remote
 # Set a higher timeout value, just in case.
 build:remote --remote_timeout=600

-# Bazel detects maximum number of jobs based on host resources.
-# Since we run remotely, we can increase this number significantly.
-common:remote --jobs=200
-
+# Increase the default number of jobs by 50% because our build has lots of
+# parallelism
+build:remote --jobs=150
 build:remote --google_default_credentials

-# Limit the number of test jobs for on an AIO local deps build. The example tests running
-# concurrently pushes the circleci executor RAM usage to its limits.
-test:aio_local_deps --jobs=24
-
 # Force remote exeuctions to consider the entire run as linux
 build:remote --cpu=k8
 build:remote --host_cpu=k8

 # Toolchain and platform related flags
-build:remote --crosstool_top=@npm//@angular/build-tooling/bazel/remote-execution/cpp:cc_toolchain_suite
-build:remote --extra_toolchains=@npm//@angular/build-tooling/bazel/remote-execution/cpp:cc_toolchain
-build:remote --extra_execution_platforms=@npm//@angular/build-tooling/bazel/remote-execution:platform
-build:remote --host_platform=@npm//@angular/build-tooling/bazel/remote-execution:platform
-build:remote --platforms=@npm//@angular/build-tooling/bazel/remote-execution:platform
+build:remote --host_javabase=@rbe_ubuntu1604_angular//java:jdk
+build:remote --javabase=@rbe_ubuntu1604_angular//java:jdk
+build:remote --host_java_toolchain=@bazel_tools//tools/jdk:toolchain_hostjdk8
+build:remote --java_toolchain=@bazel_tools//tools/jdk:toolchain_hostjdk8
+build:remote --crosstool_top=@rbe_ubuntu1604_angular//cc:toolchain
+build:remote --extra_toolchains=@rbe_ubuntu1604_angular//config:cc-toolchain
+build:remote --extra_execution_platforms=//tools:rbe_ubuntu1604-angular
+build:remote --host_platform=//tools:rbe_ubuntu1604-angular
+build:remote --platforms=//tools:rbe_ubuntu1604-angular

 # Remote instance and caching
-build:remote --remote_instance_name=projects/internal-200822/instances/primary_instance
-build:remote --bes_instance_name=internal-200822
+build:remote --remote_instance_name=projects/internal-200822/instances/default_instance
+build:remote --project_id=internal-200822
 build:remote --remote_cache=remotebuildexecution.googleapis.com
 build:remote --remote_executor=remotebuildexecution.googleapis.com

-# Use HTTP remote cache
-build:remote-cache --remote_cache=https://storage.googleapis.com/angular-team-cache
-build:remote-cache --remote_accept_cached=true
-build:remote-cache --remote_upload_local_results=true
-build:remote-cache --google_default_credentials
-
-# Ensure that tags like "no-remote-exec" get propagated to actions created by rules,
-# even if the rule implementation does not explicitly pass them to the execution requirements.
-# https://bazel.build/reference/command-line-reference#flag--experimental_allow_tags_propagation
-common --experimental_allow_tags_propagation
-
-# Disable network access in the sandbox by default. To enable network access
-# for a particular target, use:
-#
-# load("@npm//@angular/build-tooling/bazel/remote-execution:index.bzl", "ENABLE_NETWORK")
-# my_target(
-#   ...,
-#   exec_properties = ENABLE_NETWORK,   # Enables network in remote exec
-#   tags = ["requires-network"]         # Enables network in sandbox
-# )
-build --nosandbox_default_allow_network
-
 ##################################
 # Saucelabs tests settings       #
 # Turn on these settings with    #
@@ -171,15 +131,14 @@ build --nosandbox_default_allow_network
 # retry mechanism and we do not want to retry unnecessarily if Karma already tried multiple times.
 test:saucelabs --flaky_test_attempts=1

-################
-# Flag Aliases #
-################
+###############################
+# NodeJS rules settings
+# These settings are required for rules_nodejs
+###############################

-# --ng_perf will ask the Ivy compiler to produce performance results for each build.
-build --flag_alias=ng_perf=//packages/compiler-cli:ng_perf
-# --adev_fast will run adev build/serve in a faster mode, skipping things like prerendering
-# for local development.
-build --flag_alias=fast_adev=//adev:fast_build_mode
+# Turn on managed directories feature in Bazel
+# This allows us to avoid installing a second copy of node_modules
+common --experimental_allow_incremental_repository_updates

 ####################################################
 # User bazel configuration
@@ -188,4 +147,4 @@ build --flag_alias=fast_adev=//adev:fast_build_mode

 # Load any settings which are specific to the current user. Needs to be *last* statement
 # in this config, as the user configuration should be able to overwrite flags from this file.
-try-import %workspace%/.bazelrc.user
+try-import .bazelrc.user
@@ -1 +1,3 @@
-5.0.0
+2.1.1
+# [NB: this comment has to be after the first line, see https://github.com/bazelbuild/bazelisk/issues/117]
+# When updating the Bazel version you also need to update the RBE toolchains version in package.bzl
@@ -12,8 +12,8 @@ We use this as a symmetric AES encryption key to encrypt tokens like
 a GitHub token that enables publishing snapshots.

 To create the github_token file, we take this approach:
- Find the angular-builds:token in the internal pw database
+- Find the angular-builds:token in http://valentine
 - Go inside the CircleCI default docker image so you use the same version of openssl as we will at runtime: `docker run --rm -it circleci/node:10.12`
 - echo "https://[token]:@github.com" > credentials
 - openssl aes-256-cbc -e -in credentials -out .circleci/github_token -k $KEY
- If needed, base64-encode the result so you can copy-paste it out of docker: `base64 github_token`
+- If needed, base64-encode the result so you can copy-paste it out of docker: `base64 github_token`
@@ -1,16 +1,15 @@
 # Settings in this file should be OS agnostic. Use the bazel.<OS>.rc files for OS specific settings.

+# Don't be spammy in the logs
+build --noshow_progress
+
 # Print all the options that apply to the build.
 # This helps us diagnose which options override others
 # (e.g. /etc/bazel.bazelrc vs. tools/bazel.rc)
 build --announce_rc

 # Retry in the event of flakes, eg. https://circleci.com/gh/angular/angular/31309
-# By default this is set in the project `.bazelrc` to `1`.
-test --flaky_test_attempts=3
+test --flaky_test_attempts=2

 # More details on failures
 build --verbose_failures=true
-
-# CI supports colors but Bazel does not detect it.
-common --color=yes
@@ -12,12 +12,10 @@ build --repository_cache=/home/circleci/bazel_repository_cache

 # Workaround https://github.com/bazelbuild/bazel/issues/3645
 # Bazel doesn't calculate the memory ceiling correctly when running under Docker.
-# Limit Bazel to consuming resources that fit in CircleCI "2xlarge+" class
+# Limit Bazel to consuming resources that fit in CircleCI "xlarge" class
 # https://circleci.com/docs/2.0/configuration-reference/#resource_class
-build --local_cpu_resources=20
-build --local_ram_resources=40960
+build --local_resources=14336,8.0,1.0

 # All build executed remotely should be done using our RBE configuration.
 build:remote --google_default_credentials
-
 build --config=remote
@@ -6,9 +6,9 @@
 # https://docs.bazel.build/versions/master/guide.html#bazelrc-syntax-and-semantics
 try-import %workspace%/.circleci/bazel.common.rc

-# Manually set the local resources used in windows CI runs
-build --local_ram_resources=120000
-build --local_cpu_resources=32
+# Save downloaded repositories in a location that can be cached by CircleCI. This helps us
+# speeding up the analysis time significantly with Bazel managed node dependencies on the CI.
+build --repository_cache=C:/Users/circleci/bazel_repository_cache

 # All windows jobs run on master and should use http caching
 build --remote_http_cache=https://storage.googleapis.com/angular-team-cache
@@ -1,16 +1,911 @@
-# This config is remaining in place to prevent pull requests failing because of CircleCI config missing.
+# Configuration file for https://circleci.com/gh/angular/angular

+# Note: YAML anchors allow an object to be re-used, reducing duplication.
+# The ampersand declares an alias for an object, then later the `<<: *name`
+# syntax dereferences it.
+# See http://blog.daemonl.com/2016/02/yaml.html
+# To validate changes, use an online parser, eg.
+# http://yaml-online-parser.appspot.com/
+
+# CircleCI configuration version
+# Version 2.1 allows for extra config reuse features
+# https://circleci.com/docs/2.0/reusing-config/#getting-started-with-config-reuse
 version: 2.1

-jobs:
-  pass:
+# We don't want to include the current branch name in the cache key because that would prevent
+# PRs from being able to restore the cache since the branch names are always different for PRs.
+# The cache key should only consist of dynamic values that change whenever something in the
+# cache changes. For example:
+# 1) yarn lock file changes --> cached "node_modules" are different.
+# 2) bazel repository definitions change --> cached bazel repositories are different.
+# Windows needs its own cache key because binaries in node_modules are different.
+# **NOTE 1 **: If you change the cache key prefix, also sync the cache_key_fallback to match.
+# **NOTE 2 **: Keep the static part of the cache key as prefix to enable correct fallbacks.
+# See https://circleci.com/docs/2.0/caching/#restoring-cache for how prefixes work in CircleCI.
+var_3: &cache_key v4-angular-node-12-{{ checksum ".bazelversion" }}-{{ checksum "yarn.lock" }}-{{ checksum "WORKSPACE" }}-{{ checksum "packages/bazel/package.bzl" }}-{{ checksum "aio/yarn.lock" }}
+# We invalidate the cache if the Bazel version changes because otherwise the `bazelisk` cache
+# folder will contain all previously used versions and ultimately cause the cache restoring to
+# be slower due to its growing size.
+var_4: &cache_key_fallback v4-angular-node-12-{{ checksum ".bazelversion" }}
+var_3_win: &cache_key_win v5-angular-win-node-12-{{ checksum ".bazelversion" }}-{{ checksum "yarn.lock" }}-{{ checksum "WORKSPACE" }}-{{ checksum "packages/bazel/package.bzl" }}-{{ checksum "aio/yarn.lock" }}
+var_4_win: &cache_key_win_fallback v5-angular-win-node-12-{{ checksum ".bazelversion" }}
+
+# Cache key for the `components-repo-unit-tests` job. **Note** when updating the SHA in the
+# cache keys also update the SHA for the "COMPONENTS_REPO_COMMIT" environment variable.
+var_5: &components_repo_unit_tests_cache_key v5-angular-components-598db096e668aa7e9debd56eedfd127b7a55e371
+var_6: &components_repo_unit_tests_cache_key_fallback v5-angular-components-
+
+# Workspace initially persisted by the `setup` job, and then enhanced by `build-npm-packages` and
+# `build-ivy-npm-packages`.
+# https://circleci.com/docs/2.0/workflows/#using-workspaces-to-share-data-among-jobs
+# https://circleci.com/blog/deep-diving-into-circleci-workspaces/
+var_7: &workspace_location ~/
+
+# Filter to run a job on builds for pull requests only.
+var_8: &only_on_pull_requests
+  filters:
+    branches:
+      only:
+        - /pull\/\d+/
+
+# Filter to skip a job on builds for pull requests.
+var_9: &skip_on_pull_requests
+  filters:
+    branches:
+      ignore:
+        - /pull\/\d+/
+
+# Filter to run a job on builds for the master branch only.
+var_10: &only_on_master
+  filters:
+    branches:
+      only:
+        - master
+
+# Executor Definitions
+# https://circleci.com/docs/2.0/reusing-config/#authoring-reusable-executors
+# **NOTE 1**: Pin to exact images using an ID (SHA). See https://circleci.com/docs/2.0/circleci-images/#using-a-docker-image-id-to-pin-an-image-to-a-fixed-version.
+#             (Using the tag in not necessary when pinning by ID, but include it anyway for documentation purposes.)
+# **NOTE 2**: If you change the version of the docker images, also change the `cache_key` suffix.
+# **NOTE 3**: If you change the version of the `*-browsers` docker image, make sure the
+#             `--versions.chrome` arg in `integration/bazel-schematics/test.sh` specifies a
+#             ChromeDriver version that is compatible with the Chrome version in the image.
+executors:
+  default-executor:
+    parameters:
+      resource_class:
+        type: string
+        default: medium
    docker:
-      - image: cimg/base:2022.05
+      - image: circleci/node:12.14.1@sha256:f9de24fc0017059cc42ef7d07db060008af65a98b1f0cdd1ef3339213226bf6d
+    resource_class: << parameters.resource_class >>
+    working_directory: ~/ng
+
+  windows-executor:
+    working_directory: ~/ng
+    resource_class: windows.medium
+    # CircleCI windows VMs do have the GitBash shell available:
+    # https://github.com/CircleCI-Public/windows-preview-docs#shells
+    # But in this specific case we really should not use it because Bazel must not be ran from
+    # GitBash. These issues discuss why:
+    # https://github.com/bazelbuild/bazel/issues/5751
+    # https://github.com/bazelbuild/bazel/issues/5724#issuecomment-410194038
+    # https://github.com/bazelbuild/bazel/issues/6339#issuecomment-441600879
+    shell: powershell.exe -ExecutionPolicy Bypass
+    machine:
+      # Windows preview image that includes the following:
+      # - Visual Studio 2019 build tools
+      # - Node 12
+      # - yarn 1.17
+      # - Python 3 3.7.4
+      image: windows-server-2019-vs2019:201908-02
+
+# Command Definitions
+# https://circleci.com/docs/2.0/reusing-config/#authoring-reusable-commands
+commands:
+  custom_attach_workspace:
+    description: Attach workspace at a predefined location
    steps:
-      - run: echo "This too shall pass (always)"
+      - attach_workspace:
+          at: *workspace_location
+
+  # Install shared libs used by Chrome that is either provisioned by
+  # rules_webtesting or by puppeteer.
+  install_chrome_libs:
+    description: Install shared Chrome libs
+    steps:
+      - run:
+          name: Install shared Chrome libs
+          command: |
+            sudo apt-get update
+            # Install GTK+ graphical user interface (libgtk-3-0), advanced linux sound architecture (libasound2)
+            # and network security service libraries (libnss3) & X11 Screen Saver extension library (libssx1)
+            # which are dependendies of chrome & needed for karma & protractor headless chrome tests.
+            # This is a very small install which takes around 7s in comparing to using the full
+            # circleci/node:x.x.x-browsers image.
+            sudo apt-get -y install libgtk-3-0 libasound2 libnss3 libxss1
+
+  # Install java runtime which is required by some integration tests such as
+  # //integration:hello_world__closure_test, //integration:i18n_test and
+  # //integration:ng_elements_test to run the closure compiler
+  install_java:
+    description: Install java
+    steps:
+      - run:
+          name: Install java
+          command: |
+            sudo apt-get update
+            # Install java runtime
+            sudo apt-get install default-jre
+
+  # Initializes the CI environment by setting up common environment variables.
+  init_environment:
+    description: Initializing environment (setting up variables)
+    steps:
+      - run:
+          name: Set up environment
+          environment:
+              CIRCLE_GIT_BASE_REVISION: << pipeline.git.base_revision >>
+              CIRCLE_GIT_REVISION: << pipeline.git.revision >>
+          command: ./.circleci/env.sh
+      - run:
+          # Configure git as the CircleCI `checkout` command does.
+          # This is needed because we only checkout on the setup job.
+          # Add GitHub to known hosts
+          name: Configure git
+          command: |
+            mkdir -p ~/.ssh
+            echo 'github.com ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==' >> ~/.ssh/known_hosts
+            git config --global url."ssh://git@github.com".insteadOf "https://github.com" || true
+            git config --global gc.auto 0 || true
+
+  init_saucelabs_environment:
+    description: Sets up a domain that resolves to the local host.
+    steps:
+      - run:
+          name: Preparing environment for running tests on Saucelabs.
+          command: |
+            # For SauceLabs jobs, we set up a domain which resolves to the machine which launched
+            # the tunnel. We do this because devices are sometimes not able to properly resolve
+            # `localhost` or `127.0.0.1` through the SauceLabs tunnel. Using a domain that does not
+            # resolve to anything on SauceLabs VMs ensures that such requests are always resolved
+            # through the tunnel, and resolve to the actual tunnel host machine (i.e. the CircleCI VM).
+            # More context can be found in: https://github.com/angular/angular/pull/35171.
+            setPublicVar SAUCE_LOCALHOST_ALIAS_DOMAIN "angular-ci.local"
+            setSecretVar SAUCE_ACCESS_KEY $(echo $SAUCE_ACCESS_KEY | rev)
+      - run:
+          # Sets up a local domain in the machine's host file that resolves to the local
+          # host. This domain is helpful in Saucelabs tests where devices are not able to
+          # properly resolve `localhost` or `127.0.0.1` through the sauce-connect tunnel.
+          name: Setting up alias domain for local host.
+          command: echo "127.0.0.1 $SAUCE_LOCALHOST_ALIAS_DOMAIN" | sudo tee -a /etc/hosts
+
+  # Normally this would be an individual job instead of a command.
+  # But startup and setup time for each invidual windows job are high enough to discourage
+  # many small jobs, so instead we use a command for setup unless the gain becomes significant.
+  setup_win:
+    description: Setup windows node environment
+    steps:
+      # Use the Linux workspace directly, as it already has checkout, rebased and node modules.
+      - custom_attach_workspace
+      # Install Bazel pre-requisites that aren't in the preconfigured CircleCI Windows VM.
+      - run: ./.circleci/windows-env.ps1
+      - run: node --version
+      - run: yarn --version
+      - restore_cache:
+          keys:
+            - *cache_key_win
+            - *cache_key_win_fallback
+      # Reinstall to get windows binaries.
+      - run: yarn install --frozen-lockfile --non-interactive
+      # Install @bazel/bazelisk globally and use that for the first run.
+      # Workaround for https://github.com/bazelbuild/rules_nodejs/issues/894
+      # NB: the issue was for @bazel/bazel but the same problem applies to @bazel/bazelisk
+      - run: yarn global add @bazel/bazelisk@$env:BAZELISK_VERSION
+      - run: bazelisk info
+
+  notify_webhook_on_fail:
+    description: Notify a webhook about failure
+    parameters:
+      # `webhook_url_env_var` are secret env vars defined in CircleCI project settings.
+      # The URLs come from https://angular-team.slack.com/apps/A0F7VRE7N-circleci.
+      webhook_url_env_var:
+        type: env_var_name
+    steps:
+      - run:
+          when: on_fail
+          command: |
+            notificationJson="{\"text\":\":x: \`$CIRCLE_JOB\` job for $CIRCLE_BRANCH branch failed on build $CIRCLE_BUILD_NUM: $CIRCLE_BUILD_URL :scream:\"}"
+            curl --request POST --header "Content-Type: application/json" --data "$notificationJson" ${<< parameters.webhook_url_env_var >>}
+
+# Job definitions
+# Jobs can include parameters that are passed in the workflow job invocation.
+# https://circleci.com/docs/2.0/reusing-config/#authoring-parameterized-jobs
+jobs:
+  setup:
+    executor: default-executor
+    steps:
+      - checkout
+      - run:
+          name: Rebase PR on target branch
+          # After checkout, rebase on top of target branch.
+          command: >
+            if [[ -n "${CIRCLE_PR_NUMBER}" ]]; then
+              # User is required for rebase.
+              git config user.name "angular-ci"
+              git config user.email "angular-ci"
+              # Rebase PR on top of target branch.
+              node tools/rebase-pr.js angular/angular ${CIRCLE_PR_NUMBER}
+            else
+              echo "This build is not over a PR, nothing to do."
+            fi
+      # This cache is saved in the build-npm-packages so that Bazel cache is also included.
+      - restore_cache:
+          keys:
+            - *cache_key
+            - *cache_key_fallback
+      - init_environment
+      - run:
+          name: Running Yarn install
+          command: yarn install --frozen-lockfile --non-interactive
+          # Yarn's requests sometimes take more than 10mins to complete.
+          no_output_timeout: 45m
+      - run: yarn --cwd aio install --frozen-lockfile --non-interactive
+      # Make the bazel directories and add a file to them if they don't exist already so that
+      # persist_to_workspace does not fail.
+      - run: |
+          if [ ! -d ~/bazel_repository_cache ]; then
+            mkdir ~/bazel_repository_cache
+            touch ~/bazel_repository_cache/MARKER
+          fi
+      # Persist any changes at this point to be reused by further jobs.
+      # **NOTE**: To add new content to the workspace, always persist on the same root.
+      - persist_to_workspace:
+          root: *workspace_location
+          paths:
+            - ./ng
+            - ./bazel_repository_cache
+
+  lint:
+    executor: default-executor
+    steps:
+      - custom_attach_workspace
+      - init_environment
+
+      - run: 'yarn bazel:format -mode=check ||
+              (echo "BUILD files not formatted. Please run ''yarn bazel:format''" ; exit 1)'
+      # Run the skylark linter to check our Bazel rules
+      - run: 'yarn bazel:lint ||
+              (echo -e "\n.bzl files have lint errors. Please run ''yarn bazel:lint-fix''"; exit 1)'
+
+      - run: yarn lint
+      - run: yarn ts-circular-deps:check
+      - run: yarn -s ng-dev pullapprove:verify
+
+  test:
+    executor:
+      name: default-executor
+      # Now that large integration tests are running locally in parallel (they can't run on RBE yet
+      # as they require network access for yarn install), this test is running out of memory
+      # consistently with the xlarge machine.
+      # TODO: switch back to xlarge once integration tests are running on remote-exec
+      resource_class: 2xlarge+
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+      - install_java
+      - run:
+          command: yarn bazel test //... --build_tag_filters=-ivy-only --test_tag_filters=-ivy-only
+          no_output_timeout: 20m
+
+  # Temporary job to test what will happen when we flip the Ivy flag to true
+  test_ivy_aot:
+    executor:
+      name: default-executor
+      resource_class: xlarge
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+      # We need to explicitly specify the --symlink_prefix option because otherwise we would
+      # not be able to easily find the output bin directory when uploading artifacts for size
+      # measurements.
+      - run:
+          command: yarn test-ivy-aot //... --symlink_prefix=dist/
+          no_output_timeout: 20m
+
+        # Publish bundle artifacts which will be used to calculate the size change. **Note**: Make
+        # sure that the size plugin from the Angular robot fetches the artifacts from this CircleCI
+        # job (see .github/angular-robot.yml). Additionally any artifacts need to be stored with the
+        # following path format: "{projectName}/{context}/{fileName}". This format is necessary
+        # because otherwise the bot is not able to pick up the artifacts from CircleCI. See:
+        # https://github.com/angular/github-robot/blob/master/functions/src/plugins/size.ts#L392-L394
+      - store_artifacts:
+          path: dist/bin/packages/core/test/bundling/hello_world/bundle.min.js
+          destination: core/hello_world/bundle
+      - store_artifacts:
+          path: dist/bin/packages/core/test/bundling/todo/bundle.min.js
+          destination: core/todo/bundle
+      - store_artifacts:
+          path: dist/bin/packages/core/test/bundling/hello_world/bundle.min.js.br
+          destination: core/hello_world/bundle.br
+      - store_artifacts:
+          path: dist/bin/packages/core/test/bundling/todo/bundle.min.js.br
+          destination: core/todo/bundle.br
+
+  # NOTE: This is currently limited to master builds only. See the `monitoring` configuration.
+  saucelabs_view_engine:
+    executor:
+      name: default-executor
+      # In order to avoid the bottleneck of having a slow host machine, we acquire a better
+      # container for this job. This is necessary because we launch a lot of browsers concurrently
+      # and therefore the tunnel and Karma need to process a lot of file requests and tests.
+      resource_class: xlarge
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - init_saucelabs_environment
+      - run:
+          name: Run Bazel tests on Saucelabs with ViewEngine
+          # See /tools/saucelabs/README.md for more info
+          command: |
+            yarn bazel run //tools/saucelabs:sauce_service_setup
+            TESTS=$(./node_modules/.bin/bazelisk query --output label '(kind(karma_web_test, ...) intersect attr("tags", "saucelabs", ...)) except attr("tags", "ivy-only", ...) except attr("tags", "fixme-saucelabs-ve", ...)')
+            yarn bazel test --config=saucelabs ${TESTS}
+            yarn bazel run //tools/saucelabs:sauce_service_stop
+          no_output_timeout: 40m
+      - notify_webhook_on_fail:
+          webhook_url_env_var: SLACK_DEV_INFRA_CI_FAILURES_WEBHOOK_URL
+
+  # NOTE: This is currently limited to master builds only. See the `monitoring` configuration.
+  saucelabs_ivy:
+    executor:
+      name: default-executor
+      # In order to avoid the bottleneck of having a slow host machine, we acquire a better
+      # container for this job. This is necessary because we launch a lot of browsers concurrently
+      # and therefore the tunnel and Karma need to process a lot of file requests and tests.
+      resource_class: xlarge
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - init_saucelabs_environment
+      - run:
+          name: Run Bazel tests on Saucelabs with Ivy
+          # See /tools/saucelabs/README.md for more info
+          command: |
+            yarn bazel run //tools/saucelabs:sauce_service_setup
+            TESTS=$(./node_modules/.bin/bazelisk query --output label '(kind(karma_web_test, ...) intersect attr("tags", "saucelabs", ...)) except attr("tags", "no-ivy-aot", ...) except attr("tags", "fixme-saucelabs-ivy", ...)')
+            yarn bazel test --config=saucelabs --config=ivy ${TESTS}
+            yarn bazel run //tools/saucelabs:sauce_service_stop
+          no_output_timeout: 40m
+      - notify_webhook_on_fail:
+          webhook_url_env_var: SLACK_DEV_INFRA_CI_FAILURES_WEBHOOK_URL
+
+  test_aio:
+    executor: default-executor
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+        # Compile dependencies to ivy
+        # Running `ngcc` here (instead of implicitly via `ng build`) allows us to take advantage of
+        # the parallel, async mode speed-up (~20-25s on CI).
+      - run: yarn --cwd aio ngcc --properties es2015
+        # Build aio
+      - run: yarn --cwd aio build --progress=false
+        # Lint the code
+      - run: yarn --cwd aio lint
+        # Run unit tests
+      - run: yarn --cwd aio test --progress=false --watch=false
+        # Run e2e tests
+      - run: yarn --cwd aio e2e --configuration=ci
+        # Run PWA-score tests
+      - run: yarn --cwd aio test-pwa-score-localhost $CI_AIO_MIN_PWA_SCORE
+        # Run accessibility tests
+      - run: yarn --cwd aio test-a11y-score-localhost
+        # Check the bundle sizes.
+      - run: yarn --cwd aio payload-size
+        # Run unit tests for Firebase redirects
+      - run: yarn --cwd aio redirects-test
+
+  deploy_aio:
+    executor: default-executor
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+        # Deploy angular.io to production (if necessary)
+      - run: setPublicVar_CI_STABLE_BRANCH
+      - run: yarn --cwd aio deploy-production
+
+  test_aio_local:
+    parameters:
+      viewengine:
+        type: boolean
+        default: false
+    executor: default-executor
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+        # Build aio (with local Angular packages)
+      - run: yarn --cwd aio build-local<<# parameters.viewengine >>-with-viewengine<</ parameters.viewengine >>-ci
+        # Run unit tests
+      - run: yarn --cwd aio test --progress=false --watch=false
+        # Run e2e tests
+      - run: yarn --cwd aio e2e --configuration=ci
+        # Run PWA-score tests
+      - run: yarn --cwd aio test-pwa-score-localhost $CI_AIO_MIN_PWA_SCORE
+        # Check the bundle sizes.
+      - run: yarn --cwd aio payload-size aio-local<<# parameters.viewengine >>-viewengine<</ parameters.viewengine >>
+
+  test_aio_tools:
+    executor: default-executor
+    steps:
+      - custom_attach_workspace
+      - init_environment
+        # Install
+      - run: yarn --cwd aio install --frozen-lockfile --non-interactive
+      - run: yarn --cwd aio extract-cli-command-docs
+        # Run tools tests
+      - run: yarn --cwd aio tools-test
+      - run: ./aio/aio-builds-setup/scripts/test.sh
+
+  test_docs_examples:
+    parameters:
+      ivy:
+        type: boolean
+        default: false
+    executor:
+      name: default-executor
+      resource_class: xlarge
+    parallelism: 5
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+        # Install aio
+      - run: yarn --cwd aio install --frozen-lockfile --non-interactive
+        # Run examples tests. The "CIRCLE_NODE_INDEX" will be set if "parallelism" is enabled.
+        # Since the parallelism is set to "5", there will be five parallel CircleCI containers.
+        # with either "0", "1", etc as node index. This can be passed to the "--shard" argument.
+      - run: yarn --cwd aio example-e2e --setup --local <<# parameters.ivy >>--ivy<</ parameters.ivy >> --cliSpecsConcurrency=5 --shard=${CIRCLE_NODE_INDEX}/${CIRCLE_NODE_TOTAL} --retry 2
+
+  # This job should only be run on PR builds, where `CI_PULL_REQUEST` is not `false`.
+  aio_preview:
+    executor: default-executor
+    environment:
+       AIO_SNAPSHOT_ARTIFACT_PATH: &aio_preview_artifact_path 'aio/tmp/snapshot.tgz'
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - run: ./aio/scripts/build-artifacts.sh $AIO_SNAPSHOT_ARTIFACT_PATH $CI_PULL_REQUEST $CI_COMMIT
+      - store_artifacts:
+          path: *aio_preview_artifact_path
+          # The `destination` needs to be kept in synch with the value of
+          # `AIO_ARTIFACT_PATH` in `aio/aio-builds-setup/Dockerfile`
+          destination: aio/dist/aio-snapshot.tgz
+      - run: node ./aio/scripts/create-preview $CIRCLE_BUILD_NUM
+
+  # This job should only be run on PR builds, where `CI_PULL_REQUEST` is not `false`.
+  test_aio_preview:
+    executor: default-executor
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+      - run: yarn --cwd aio install --frozen-lockfile --non-interactive
+      - run:
+          name: Wait for preview and run tests
+          command: node aio/scripts/test-preview.js $CI_PULL_REQUEST $CI_COMMIT $CI_AIO_MIN_PWA_SCORE
+
+
+  # The `build-npm-packages` tasks exist for backwards-compatibility with old scripts and
+  # tests that rely on the pre-Bazel `dist/packages-dist` output structure (build.sh).
+  # Having multiple jobs that independently build in this manner duplicates some work; we build
+  # the bazel packages more than once. Even though we have a remote cache, these jobs will
+  # typically run in parallel so up-to-date outputs will not be available at the time the build
+  # starts.
+
+  # Build the view engine npm packages. No new jobs should depend on this.
+  build-npm-packages:
+    executor:
+      name: default-executor
+      resource_class: xlarge
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - run: node scripts/build/build-packages-dist.js
+
+      # Save the npm packages from //packages/... for other workflow jobs to read
+      - persist_to_workspace:
+          root: *workspace_location
+          paths:
+            - ng/dist/packages-dist
+            - ng/dist/zone.js-dist
+
+      # Save dependencies and bazel repository cache to use on subsequent runs.
+      - save_cache:
+          key: *cache_key
+          paths:
+            - "node_modules"
+            - "aio/node_modules"
+            - "~/bazel_repository_cache"
+            - "~/.cache/bazelisk"
+
+  # Build the ivy npm packages.
+  build-ivy-npm-packages:
+    executor:
+      name: default-executor
+      resource_class: xlarge
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - run: node scripts/build/build-ivy-npm-packages.js
+
+      # Save the npm packages from //packages/... for other workflow jobs to read
+      - persist_to_workspace:
+          root: *workspace_location
+          paths:
+            - ng/dist/packages-dist-ivy-aot
+            - ng/dist/zone.js-dist-ivy-aot
+
+  # This job creates compressed tarballs (`.tgz` files) for all Angular packages and stores them as
+  # build artifacts. This makes it easy to try out changes from a PR build for testing purposes.
+  # More info CircleCI build artifacts: https://circleci.com/docs/2.0/artifacts
+  #
+  # NOTE: Currently, this job only runs for PR builds. See `publish_snapshot` for non-PR builds.
+  publish_packages_as_artifacts:
+    executor: default-executor
+    environment:
+      NG_PACKAGES_DIR: &ng_packages_dir 'dist/packages-dist'
+      NG_PACKAGES_ARCHIVES_DIR: &ng_packages_archives_dir 'dist/packages-dist-archives'
+      ZONEJS_PACKAGES_DIR: &zonejs_packages_dir 'dist/zone.js-dist'
+      ZONEJS_PACKAGES_ARCHIVES_DIR: &zonejs_packages_archives_dir 'dist/zone.js-dist-archives'
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      # Publish `@angular/*` packages.
+      - run:
+          name: Create artifacts for @angular/* packages
+          command: ./scripts/ci/create-package-archives.sh $CI_BRANCH $CI_COMMIT $NG_PACKAGES_DIR $NG_PACKAGES_ARCHIVES_DIR
+      - store_artifacts:
+          path: *ng_packages_archives_dir
+          destination: angular
+      # Publish `zone.js` package.
+      - run:
+          name: Create artifacts for zone.js package
+          command: ./scripts/ci/create-package-archives.sh $CI_BRANCH $CI_COMMIT $ZONEJS_PACKAGES_DIR $ZONEJS_PACKAGES_ARCHIVES_DIR
+      - store_artifacts:
+          path: *zonejs_packages_archives_dir
+          destination: zone.js
+
+  # This job updates the content of repos like github.com/angular/core-builds
+  # for every green build on angular/angular.
+  publish_snapshot:
+    executor: default-executor
+    steps:
+      # See below - ideally this job should not trigger for non-upstream builds.
+      # But since it does, we have to check this condition.
+      - run:
+          name: Skip this job for Pull Requests and Fork builds
+          # Note: Using `CIRCLE_*` env variables (instead of those defined in `env.sh` so that this
+          #       step can be run before `init_environment`.
+          command: >
+            if [[ -n "${CIRCLE_PR_NUMBER}" ]] ||
+                [[ "$CIRCLE_PROJECT_USERNAME" != "angular" ]] ||
+                [[ "$CIRCLE_PROJECT_REPONAME" != "angular" ]]; then
+              circleci step halt
+            fi
+      - custom_attach_workspace
+      - init_environment
+      # CircleCI has a config setting to force SSH for all github connections
+      # This is not compatible with our mechanism of using a Personal Access Token
+      # Clear the global setting
+      - run: git config --global --unset "url.ssh://git@github.com.insteadof"
+      - run:
+          name: Decrypt github credentials
+          # We need ensure that the same default digest is used for encoding and decoding with
+          # openssl. Openssl versions might have different default digests which can cause
+          # decryption failures based on the installed openssl version. https://stackoverflow.com/a/39641378/4317734
+          command: 'openssl aes-256-cbc -d -in .circleci/github_token -md md5 -k "${KEY}" -out ~/.git_credentials'
+      - run: ./scripts/ci/publish-build-artifacts.sh
+
+  aio_monitoring_stable:
+    executor: default-executor
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+      - run: setPublicVar_CI_STABLE_BRANCH
+      - run:
+          name: Check out `aio/` and yarn from the stable branch
+          command: |
+            git fetch origin $CI_STABLE_BRANCH
+            git checkout --force origin/$CI_STABLE_BRANCH -- aio/ .yarn/ .yarnrc
+      # Ignore yarn's engines check, because we checked out `aio/package.json` from the stable
+      # branch and there could be a node version skew, which is acceptable in this monitoring job.
+      - run: yarn config set ignore-engines true
+      - run:
+          name: Run tests against https://angular.io/
+          command: ./aio/scripts/test-production.sh https://angular.io/ $CI_AIO_MIN_PWA_SCORE
+      - notify_webhook_on_fail:
+          webhook_url_env_var: SLACK_CARETAKER_WEBHOOK_URL
+      - notify_webhook_on_fail:
+          webhook_url_env_var: SLACK_DEV_INFRA_CI_FAILURES_WEBHOOK_URL
+
+  aio_monitoring_next:
+    executor: default-executor
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - install_chrome_libs
+      - run:
+          name: Run tests against https://next.angular.io/
+          command: ./aio/scripts/test-production.sh https://next.angular.io/ $CI_AIO_MIN_PWA_SCORE
+      - notify_webhook_on_fail:
+          webhook_url_env_var: SLACK_CARETAKER_WEBHOOK_URL
+      - notify_webhook_on_fail:
+          webhook_url_env_var: SLACK_DEV_INFRA_CI_FAILURES_WEBHOOK_URL
+
+  legacy-unit-tests-saucelabs:
+    executor:
+      name: default-executor
+      # In order to avoid the bottleneck of having a slow host machine, we acquire a better
+      # container for this job. This is necessary because we launch a lot of browsers concurrently
+      # and therefore the tunnel and Karma need to process a lot of file requests and tests.
+      resource_class: xlarge
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      - init_saucelabs_environment
+      - run:
+          name: Starting Saucelabs tunnel service
+          command: ./tools/saucelabs/sauce-service.sh run
+          background: true
+      - run: yarn tsc -p packages
+      - run: yarn tsc -p modules
+      - run: yarn bazel build //packages/zone.js:npm_package
+      - run:
+          # Waiting on ready ensures that we don't run tests too early without Saucelabs not being ready.
+          name: Waiting for Saucelabs tunnel to connect
+          command: ./tools/saucelabs/sauce-service.sh ready-wait
+      - run:
+          name: Running tests on Saucelabs.
+          command: |
+            browsers=$(node -e 'console.log(require("./browser-providers.conf").sauceAliases.CI_REQUIRED.join(","))')
+            yarn karma start ./karma-js.conf.js --single-run --browsers=${browsers}
+      - run:
+          name: Stop Saucelabs tunnel service
+          command: ./tools/saucelabs/sauce-service.sh stop
+
+  # Job that runs all unit tests of the `angular/components` repository.
+  components-repo-unit-tests:
+    executor:
+      name: default-executor
+      resource_class: xlarge
+    steps:
+      - custom_attach_workspace
+      - init_environment
+      # Restore the cache before cloning the repository because the clone script re-uses
+      # the restored repository if present. This reduces the amount of times the components
+      # repository needs to be cloned (this is slow and increases based on commits in the repo).
+      - restore_cache:
+          keys:
+            - *components_repo_unit_tests_cache_key
+            # Whenever the `angular/components` SHA is updated, the cache key will no longer
+            # match. The fallback cache will still match, and CircleCI will restore the most
+            # recently cached repository folder. Without the fallback cache, we'd need to download
+            # the repository from scratch and it would slow down the job. This is because we can't
+            # clone the repository with reduced `--depth`, but rather need to clone the whole
+            # repository to be able to support arbitrary SHAs.
+            - *components_repo_unit_tests_cache_key_fallback
+      - run:
+          name: "Fetching angular/components repository"
+          command: ./scripts/ci/clone_angular_components_repo.sh
+      - run:
+          # Run yarn install to fetch the Bazel binaries as used in the components repo.
+          name: Installing dependencies.
+          # TODO: remove this once the repo has been updated to use NodeJS v12 and Yarn 1.19.1.
+          # We temporarily ignore the "engines" because the Angular components repository has
+          # minimum dependency on NodeJS v12 and Yarn 1.19.1, but the framework repository uses
+          # older versions.
+          command: yarn --ignore-engines --cwd ${COMPONENTS_REPO_TMP_DIR} install --frozen-lockfile --non-interactive
+      - save_cache:
+          key: *components_repo_unit_tests_cache_key
+          paths:
+            # Temporary directory must be kept in sync with the `$COMPONENTS_REPO_TMP_DIR` env
+            # variable. It needs to be hardcoded here, because env variables interpolation is
+            # not supported.
+            - "/tmp/angular-components-repo"
+      - run:
+          # Updates the `angular/components` `package.json` file to refer to the release output
+          # inside the `packages-dist` directory. Note that it's not necessary to perform a yarn
+          # install as Bazel runs Yarn automatically when needed.
+          name: Setting up release packages.
+          command: node scripts/ci/update-deps-to-dist-packages.js ${COMPONENTS_REPO_TMP_DIR}/package.json dist/packages-dist/
+      - run:
+          name: "Running `angular/components` unit tests"
+          command: ./scripts/ci/run_angular_components_unit_tests.sh
+
+  test_zonejs:
+    executor:
+      name: default-executor
+      resource_class: xlarge
+    steps:
+      - custom_attach_workspace
+      - init_environment
+        # Install
+      - run: yarn --cwd packages/zone.js install --frozen-lockfile --non-interactive
+        # Run zone.js tools tests
+      - run: yarn --cwd packages/zone.js promisetest
+      - run: yarn --cwd packages/zone.js promisefinallytest
+      - run: yarn bazel build //packages/zone.js:npm_package &&
+             cp dist/bin/packages/zone.js/npm_package/dist/zone-mix.js ./packages/zone.js/test/extra/ &&
+             cp dist/bin/packages/zone.js/npm_package/dist/zone-patch-electron.js ./packages/zone.js/test/extra/ &&
+             yarn --cwd packages/zone.js electrontest
+      - run: yarn --cwd packages/zone.js jesttest
+
+  # Windows jobs
+  # Docs: https://circleci.com/docs/2.0/hello-world-windows/
+  test_win:
+    executor: windows-executor
+    steps:
+      - setup_win
+      - run:
+          # Ran into a command parsing problem where `-browser:chromium-local` was converted to
+          # `-browser: chromium-local` (a space was added) in https://circleci.com/gh/angular/angular/357511.
+          # Probably a powershell command parsing thing. There's no problem using a yarn script though.
+          command: yarn circleci-win-ve
+          no_output_timeout: 45m
+      # Save bazel repository cache to use on subsequent runs.
+      # We don't save node_modules because it's faster to use the linux workspace and reinstall.
+      - save_cache:
+          key: *cache_key_win
+          paths:
+            - "C:/Users/circleci/bazel_repository_cache"
+
+  test_ivy_aot_win:
+    executor: windows-executor
+    steps:
+      - setup_win
+      - run:
+          command: yarn circleci-win-ivy
+          no_output_timeout: 45m
+

 workflows:
  version: 2
  default_workflow:
    jobs:
-      - pass
+      - setup:
+          filters:
+            branches:
+              ignore: g3
+      - lint:
+          requires:
+            - setup
+      - test:
+          requires:
+            - setup
+      - test_ivy_aot:
+          requires:
+            - setup
+      - build-npm-packages:
+          requires:
+            - setup
+      - build-ivy-npm-packages:
+          requires:
+            - setup
+      - legacy-unit-tests-saucelabs:
+          requires:
+            - setup
+      - test_aio:
+          requires:
+            - setup
+      - deploy_aio:
+          requires:
+            - test_aio
+      - test_aio_local:
+          requires:
+            - build-npm-packages
+      - test_aio_local:
+          name: test_aio_local_viewengine
+          viewengine: true
+          requires:
+            - build-npm-packages
+      - test_aio_tools:
+          requires:
+            - build-npm-packages
+      - test_docs_examples:
+          requires:
+            - build-npm-packages
+      - test_docs_examples:
+          name: test_docs_examples_ivy
+          ivy: true
+          requires:
+            - build-npm-packages
+      - aio_preview:
+          # Only run on PR builds. (There can be no previews for non-PR builds.)
+          <<: *only_on_pull_requests
+          requires:
+            - setup
+      - test_aio_preview:
+          requires:
+            - aio_preview
+      - publish_packages_as_artifacts:
+          requires:
+            - build-npm-packages
+      - publish_snapshot:
+          # Note: no filters on this job because we want it to run for all upstream branches
+          # We'd really like to filter out pull requests here, but not yet available:
+          # https://discuss.circleci.com/t/workflows-pull-request-filter/14396/4
+          # Instead, the job just exits immediately at the first step.
+          requires:
+            # Only publish if tests and integration tests pass
+            - test
+            - test_ivy_aot
+            # Only publish if `aio`/`docs` tests using the locally built Angular packages pass
+            - test_aio_local
+            - test_aio_local_viewengine
+            - test_docs_examples
+            - test_docs_examples_ivy
+            # Get the artifacts to publish from the build-packages-dist job
+            # since the publishing script expects the legacy outputs layout.
+            - build-npm-packages
+            - build-ivy-npm-packages
+            - legacy-unit-tests-saucelabs
+      - components-repo-unit-tests:
+          requires:
+            - build-npm-packages
+      - test_zonejs:
+          requires:
+            - setup
+      # Windows Jobs
+      # These are very slow so we run them on non-PRs only for now.
+      # TODO: remove the filter when CircleCI makes Windows FS faster.
+      # The Windows jobs are only run after their non-windows counterparts finish successfully.
+      # This isn't strictly necessary as there is no artifact dependency, but helps economize
+      # CI resources by not attempting to build when we know should fail.
+      - test_win:
+          <<: *skip_on_pull_requests
+          requires:
+            - test
+      - test_ivy_aot_win:
+          <<: *skip_on_pull_requests
+          requires:
+            - test_ivy_aot
+
+  monitoring:
+    jobs:
+      - setup
+      - aio_monitoring_stable:
+          requires:
+            - setup
+      - aio_monitoring_next:
+          requires:
+            - setup
+      - saucelabs_ivy:
+          # Testing saucelabs via Bazel currently taking longer than the legacy saucelabs job as it
+          # each karma_web_test target is provisioning and tearing down browsers which is adding
+          # a lot of overhead. Running once daily on master only to avoid wasting resources and
+          # slowing down CI for PRs.
+          # TODO: Run this job on all branches (including PRs) once karma_web_test targets can
+          # share provisioned browsers and we can remove the legacy saucelabs job.
+          requires:
+            - setup
+      - saucelabs_view_engine:
+          # Testing saucelabs via Bazel currently taking longer than the legacy saucelabs job as it
+          # each karma_web_test target is provisioning and tearing down browsers which is adding
+          # a lot of overhead. Running once daily on master only to avoid wasting resources and
+          # slowing down CI for PRs.
+          # TODO: Run this job on all branches (including PRs) once karma_web_test targets can
+          # share provisioned browsers and we can remove the legacy saucelabs job.
+          requires:
+            - setup
+    triggers:
+      - schedule:
+          <<: *only_on_master
+          # Runs monitoring jobs at 10:00AM every day.
+          cron: "0 10 * * *"
@@ -31,10 +31,7 @@ function setSecretVar() {
  local -r originalShellOptions=$(set +o);
  set +x -eu -o pipefail;

-  local assignmentStatement="export $1=\"${2:-}\";"
-
-  echo "${assignmentStatement}" >> $BASH_ENV;
-  eval "${assignmentStatement}"
+  echo "export $1=\"${2:-}\";" >> $BASH_ENV;

  # Restore original shell options.
  eval "$originalShellOptions";
@@ -1,4 +0,0 @@
-####################################################################################################
-# Set bazel configuration for CircleCI runs.
-####################################################################################################
-cp "${PROJECT_ROOT}/.circleci/bazel.linux.rc" ".bazelrc.user";
@@ -14,7 +14,6 @@ echo "source $envHelpersPath;" >> $BASH_ENV;
 ####################################################################################################
 # See https://circleci.com/docs/2.0/env-vars/#built-in-environment-variables for more info.
 ####################################################################################################
-setPublicVar CI "$CI"
 setPublicVar PROJECT_ROOT "$projectDir";
 setPublicVar CI_AIO_MIN_PWA_SCORE "95";
 # This is the branch being built; e.g. `pull/12345` for PR builds.
@@ -23,14 +22,10 @@ setPublicVar CI_BUILD_URL "$CIRCLE_BUILD_URL";
 setPublicVar CI_COMMIT "$CIRCLE_SHA1";
 # `CI_COMMIT_RANGE` is only used on push builds (a.k.a. non-PR, non-scheduled builds and rerun
 # workflows of such builds).
-setPublicVar CI_GIT_BASE_REVISION "${CIRCLE_GIT_BASE_REVISION}";
-setPublicVar CI_GIT_REVISION "${CIRCLE_GIT_REVISION}";
 setPublicVar CI_COMMIT_RANGE "$CIRCLE_GIT_BASE_REVISION..$CIRCLE_GIT_REVISION";
 setPublicVar CI_PULL_REQUEST "${CIRCLE_PR_NUMBER:-false}";
 setPublicVar CI_REPO_NAME "$CIRCLE_PROJECT_REPONAME";
 setPublicVar CI_REPO_OWNER "$CIRCLE_PROJECT_USERNAME";
-setPublicVar CI_PR_REPONAME "$CIRCLE_PR_REPONAME";
-setPublicVar CI_PR_USERNAME "$CIRCLE_PR_USERNAME";


 ####################################################################################################
@@ -51,7 +46,7 @@ setSecretVar CI_SECRET_PAYLOAD_FIREBASE_TOKEN "$ANGULAR_PAYLOAD_TOKEN";
 # Define SauceLabs environment variables for CircleCI.
 ####################################################################################################
 setPublicVar SAUCE_USERNAME "angular-framework";
-setSecretVar SAUCE_ACCESS_KEY "f4bf7c639c5a-c6bb-d6a4-a4b5-800aa111";
+setSecretVar SAUCE_ACCESS_KEY "0c731274ed5f-cbc9-16f4-021a-9835e39f";
 # TODO(josephperrott): Remove environment variables once all saucelabs tests are via bazel method.
 setPublicVar SAUCE_LOG_FILE /tmp/angular/sauce-connect.log
 setPublicVar SAUCE_READY_FILE /tmp/angular/sauce-connect-ready-file.lock
@@ -61,6 +56,32 @@ setPublicVar SAUCE_TUNNEL_IDENTIFIER "angular-framework-${CIRCLE_BUILD_NUM}-${CI
 # acquire CircleCI instances for too long if sauceconnect failed, we need a connect timeout.
 setPublicVar SAUCE_READY_FILE_TIMEOUT 120

+
+####################################################################################################
+# Define environment variables for the `angular/components` repo unit tests job.
+####################################################################################################
+# We specifically use a directory within "/tmp" here because we want the cloned repo to be
+# completely isolated from angular/angular in order to avoid any bad interactions between
+# their separate build setups. **NOTE**: When updating the temporary directory, also update
+# the `save_cache` path configuration in `config.yml`
+setPublicVar COMPONENTS_REPO_TMP_DIR "/tmp/angular-components-repo"
+setPublicVar COMPONENTS_REPO_URL "https://github.com/angular/components.git"
+setPublicVar COMPONENTS_REPO_BRANCH "master"
+# **NOTE**: When updating the commit SHA, also update the cache key in the CircleCI `config.yml`.
+setPublicVar COMPONENTS_REPO_COMMIT "598db096e668aa7e9debd56eedfd127b7a55e371"
+
+
+####################################################################################################
+# Decrypt GCP Credentials and store them as the Google default credentials.
+####################################################################################################
+mkdir -p "$HOME/.config/gcloud";
+openssl aes-256-cbc -d -in "${projectDir}/.circleci/gcp_token" \
+        -md md5 -k "$CIRCLE_PROJECT_REPONAME" -out "$HOME/.config/gcloud/application_default_credentials.json"
+####################################################################################################
+# Set bazel configuration for CircleCI runs.
+####################################################################################################
+cp "${projectDir}/.circleci/bazel.linux.rc" "$HOME/.bazelrc";
+
 ####################################################################################################
 # Create shell script in /tmp for Bazel actions to access CI envs without
 # busting the cache. Used by payload-size.sh script in integration tests.
@@ -71,19 +92,16 @@ echo "export PROJECT_ROOT=\"${PROJECT_ROOT}\";" >> $bazelVarEnv
 echo "export CI_BRANCH=\"${CI_BRANCH}\";" >> $bazelVarEnv
 echo "export CI_BUILD_URL=\"${CI_BUILD_URL}\";" >> $bazelVarEnv
 echo "export CI_COMMIT=\"${CI_COMMIT}\";" >> $bazelVarEnv
+echo "export CI_COMMIT_RANGE=\"${CI_COMMIT_RANGE}\";" >> $bazelVarEnv
 echo "export CI_PULL_REQUEST=\"${CI_PULL_REQUEST}\";" >> $bazelVarEnv
 echo "export CI_REPO_NAME=\"${CI_REPO_NAME}\";" >> $bazelVarEnv
 echo "export CI_REPO_OWNER=\"${CI_REPO_OWNER}\";" >> $bazelVarEnv
 echo "export CI_SECRET_PAYLOAD_FIREBASE_TOKEN=\"${CI_SECRET_PAYLOAD_FIREBASE_TOKEN}\";" >> $bazelVarEnv

 ####################################################################################################
-# Platform-specific environment setup (which can leverage the base variables from here)
 ####################################################################################################
-
-# Conditionally, load additional environment settings based on the current VM
-# operating system running. We detect Windows by checking for `%AppData%`.
-if [[ -n "${APPDATA}" ]]; then
-  source ${projectDir}/.circleci/env.windows.sh
-else
-  source ${projectDir}/.circleci/env.linux.sh
-fi
+##                  Source `$BASH_ENV` to make the variables available immediately.               ##
+##                  ***NOTE: This must remain the the last action in this script***               ##
+####################################################################################################
+####################################################################################################
+source $BASH_ENV;
@@ -1,13 +0,0 @@
-####################################################################################################
-# Set bazel configuration for CircleCI runs.
-####################################################################################################
-cp "${PROJECT_ROOT}/.circleci/bazel.windows.rc" ".bazelrc.user";
-
-# Override the `PATH` environment variable so that the windows-nvm NodeJS version
-# always has precedence over potential existing NodeJS versions from the image.
-setPublicVar PATH "/c/Program Files/nodejs/:$PATH"
-
-# Expose the Bazelisk version. We need to run Bazelisk globally since Windows has problems launching
-# Bazel from a node modules directoy that might be modified by the Bazel Yarn install then.
-setPublicVar BAZELISK_VERSION \
-    "$(cd ${PROJECT_ROOT}; node -p 'require("./package.json").devDependencies["@bazel/bazelisk"]')"
@@ -0,0 +1,107 @@
+#!/usr/bin/env node
+
+/**
+ * Usage (cli):
+ * ```
+ * node create-preview <build-number> <job-name> <webhook-url>
+ * ```
+ *
+ * Usage (JS):
+ * ```js
+ * require('./trigger-webhook').
+ *   triggerWebhook(buildNumber, jobName, webhookUrl).
+ *   then(...);
+ * ```
+ *
+ * Triggers a notification webhook with CircleCI specific info.
+ *
+ * It can be used for notifying external servers and trigger operations based on CircleCI job status
+ * (e.g. triggering the creation of a preview based on previously stored build atrifacts).
+ *
+ * The body of the sent payload is of the form:
+ * ```json
+ * {
+ *   "payload": {
+ *     "build_num": ${buildNumber}
+ *     "build_parameters": {
+ *       "CIRCLE_JOB": "${jobName}"
+ *     }
+ *   }
+ * }
+ * ```
+ *
+ * When used from JS, it returns a promise which resolves to an object of the form:
+ * ```json
+ * {
+ *   "statucCode": ${statusCode},
+ *   "responseText": "${responseText}"
+ * }
+ * ```
+ *
+ * NOTE:
+ * - When used from the cli, the command will exit with an error code if the response's status code
+ *   is outside the [200, 400) range.
+ * - When used from JS, the returned promise will be resolved, even if the response's status code is
+ *   outside the [200, 400) range. It is up to the caller to decide how this should be handled.
+ */
+
+// Imports
+const {request} = require('https');
+
+// Exports
+module.exports = {
+  triggerWebhook,
+};
+
+// Run
+if (require.resolve === module) {
+  _main(process.argv.slice(2));
+}
+
+// Helpers
+function _main(args) {
+  triggerWebhook(...args).
+    then(({statusCode, responseText}) => (200 <= statusCode && statusCode < 400) ?
+      console.log(`Status: ${statusCode}\n${responseText}`) :
+      Promise.reject(new Error(`Request failed (status: ${statusCode}): ${responseText}`))).
+    catch(err => {
+      console.error(err);
+      process.exit(1);
+    });
+}
+
+function postJson(url, data) {
+  return new Promise((resolve, reject) => {
+    const opts = {method: 'post', headers: {'Content-Type': 'application/json'}};
+    const onResponse = res => {
+      const statusCode = res.statusCode || -1;
+      let responseText = '';
+
+      res.
+        on('error', reject).
+        on('data', d => responseText += d).
+        on('end', () => resolve({statusCode, responseText}));
+    };
+
+    request(url, opts, onResponse).
+      on('error', reject).
+      end(JSON.stringify(data));
+  });
+}
+
+async function triggerWebhook(buildNumber, jobName, webhookUrl) {
+  if (!buildNumber || !jobName || !webhookUrl || isNaN(buildNumber)) {
+    throw new Error(
+        'Missing or invalid arguments.\n' +
+        'Expected: buildNumber (number), jobName (string), webhookUrl (string)');
+  }
+
+  const data = {
+    payload: {
+      build_num: +buildNumber,
+      build_parameters: {CIRCLE_JOB: jobName},
+    },
+  };
+
+  return postJson(webhookUrl, data);
+}
@@ -0,0 +1,56 @@
+# Install Bazel pre-reqs on Windows
+# https://docs.bazel.build/versions/master/install-windows.html
+# https://docs.bazel.build/versions/master/windows.html
+# Install MSYS2 and packages
+choco install msys2 --version 20180531.0.0 --no-progress --package-parameters "/NoUpdate"
+C:\tools\msys64\usr\bin\bash.exe -l -c "pacman --needed --noconfirm -S zip unzip patch diffutils git"
+
+# Add PATH modifications to the Powershell profile. This is the win equivalent of .bash_profile.
+# https://docs.microsoft.com/en-us/previous-versions//bb613488(v=vs.85)
+new-item -path $profile -itemtype file -force
+# Paths for nodejs, npm, yarn, and msys2. Use single quotes to prevent interpolation.
+# Add before the original path to use msys2 instead of the installed gitbash.
+Add-Content $profile '$Env:path = "${Env:ProgramFiles}\nodejs\;C:\Users\circleci\AppData\Roaming\npm\;${Env:ProgramFiles(x86)}\Yarn\bin\;C:\Users\circleci\AppData\Local\Yarn\bin\;C:\tools\msys64\usr\bin\;" + $Env:path'
+# Environment variables for Bazel
+Add-Content $profile '$Env:BAZEL_SH = "C:\tools\msys64\usr\bin\bash.exe"'
+
+# Get the bazelisk version devdep and store it in a global var for use in the circleci job.
+$bazeliskVersion = & ${Env:ProgramFiles}\nodejs\node.exe -e "console.log(require('./package.json').devDependencies['@bazel/bazelisk'])"
+# This is a tricky situation: we want $bazeliskVersion to be evaluated but not $Env:BAZELISK_VERSION.
+# Formatting works https://stackoverflow.com/questions/32127583/expand-variable-inside-single-quotes
+$bazeliskVersionGlobalVar = '$Env:BAZELISK_VERSION = "{0}"' -f $bazeliskVersion
+Add-Content $profile $bazeliskVersionGlobalVar
+
+# Remove the CircleCI checkout SSH override, because it breaks cloning repositories through Bazel.
+# See https://circleci.com/gh/angular/angular/401454 for an example.
+# TODO: is this really needed? Maybe there's a better way. It doesn't happen on Linux or on Codefresh.
+git config --global --unset url.ssh://git@github.com.insteadOf
+
+
+####################################################################################################
+# Decrypt GCP Credentials and store them as the Google default credentials.
+####################################################################################################
+mkdir ${env:APPDATA}\gcloud
+openssl aes-256-cbc -d -in .circleci\gcp_token -md md5 -out "$env:APPDATA\gcloud\application_default_credentials.json" -k "$env:CIRCLE_PROJECT_REPONAME"
+
+####################################################################################################
+# Set bazel configuration for CircleCI runs.
+####################################################################################################
+copy .circleci\bazel.windows.rc ${Env:USERPROFILE}\.bazelrc
+
+####################################################################################################
+# Install specific version of node.
+####################################################################################################
+choco install nodejs --version 12.14.1 --no-progress
+
+# These Bazel prereqs aren't needed because the CircleCI image already includes them.
+# choco install yarn --version 1.16.0 --no-progress
+# choco install vcredist2015 --version 14.0.24215.20170201
+
+# We don't need VS Build Tools for the tested bazel targets.
+# If it's needed again, uncomment these lines.
+# VS Build Tools are needed for Bazel C++ targets (like com_google_protobuf)
+# choco install visualstudio2019buildtools --version 16.1.2.0 --no-progress --package-parameters "--add Microsoft.VisualStudio.Workload.VCTools --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 --add Microsoft.Component.VC.Runtime.UCRTSDK --add Microsoft.VisualStudio.Component.Windows10SDK.17763"
+# Add-Content $profile '$Env:BAZEL_VC = "${Env:ProgramFiles(x86)}\Microsoft Visual Studio\2019\BuildTools\VC\"'
+# Python is needed for Bazel Python targets
+# choco install python --version 3.5.1 --no-progress
@@ -0,0 +1,47 @@
+{
+  "commitMessage": {
+    "maxLength": 120,
+    "minBodyLength": 0,
+    "types": [
+      "build",
+      "ci",
+      "docs",
+      "feat",
+      "fix",
+      "perf",
+      "refactor",
+      "release",
+      "style",
+      "test"
+    ],
+    "scopes": [
+      "animations",
+      "bazel",
+      "benchpress",
+      "changelog",
+      "common",
+      "compiler",
+      "compiler-cli",
+      "core",
+      "dev-infra",
+      "docs-infra",
+      "elements",
+      "forms",
+      "http",
+      "language-service",
+      "localize",
+      "ngcc",
+      "packaging",
+      "platform-browser",
+      "platform-browser-dynamic",
+      "platform-server",
+      "platform-webworker",
+      "platform-webworker-dynamic",
+      "router",
+      "service-worker",
+      "upgrade",
+      "ve",
+      "zone.js"
+    ]
+  }
+}
@@ -1,4 +1,4 @@
-# VSCode Remote Development - Developing inside a Container
+# VSCode Remote Development - Developing inside a Containers

 This folder contains configuration files that can be used to opt into working on this repository in a [Docker container](https://www.docker.com/resources/what-container) via [VSCode](https://code.visualstudio.com/)'s Remote Development feature (see below).

@@ -12,7 +12,7 @@ Info on remote development and developing inside a container with VSCode:

 _Prerequisite: [Install Docker](https://docs.docker.com/install) on your local environment._

-To get started, read and follow the instructions in [Developing inside a Container](https://code.visualstudio.com/docs/remote/containers). The [.devcontainer/](.) directory contains pre-configured `devcontainer.json` and `Dockerfile` files, which you can use to set up remote development with a docker container.
+To get started, read and follow the instuctions in [Developing inside a Container](https://code.visualstudio.com/docs/remote/containers). The [.devcontainer/](.) directory contains pre-configured `devcontainer.json` and `Dockerfile` files, which you can use to set up remote development with a docker container.

 In a nutshell, you need to:
 - Install the [Remote - Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension.
@@ -1,8 +1,6 @@
 # Image metadata and config.
-# Ideally, the Node.js version should match what we use on CI.
-# See `executors > default-executor` in `.circleci/config.yml`.
-FROM cimg/node:18.13.0@sha256:45d0ee279f522c4562a464df71108104cc9b2187205333ffd0707d4f05589731
-
+FROM circleci/node:10-browsers  # Ideally, the image version should be what we use on CI.
+                                # See `executors > browsers-executor` in `.circleci/config.yml`.

 LABEL name="Angular dev environment" \
      description="This image can be used to create a dev environment for building Angular." \
@@ -16,8 +14,10 @@ EXPOSE 4000 4200 4433 5000 8080 9876
 USER root


-# Configure `Node.js`/`npm`.
+# Configure `Node.js`/`npm` and install utilities.
 RUN npm config --global set user root
+RUN npm install --global yarn@latest  # Ideally, the version should be what we use on CI.
+                                      # See `commands > overwrite_yarn` in `.circleci/config.yml`.


 # Go! (And keep going.)
@@ -4,3 +4,9 @@
 # JS and TS files must always use LF for tools to work
 *.js eol=lf
 *.ts eol=lf
+
+# API guardian patch must always use LF for tests to work
+*.patch eol=lf
+
+# Must keep Windows line ending to be parsed correctly
+scripts/windows/packages.txt eol=crlf
@@ -1,6 +1,10 @@
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
+
 Please help us process issues more efficiently by filing an
 issue using one of the following templates:

 https://github.com/angular/angular/issues/new/choose

 Thank you!
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
@@ -0,0 +1,69 @@
+---
+name: "\U0001F41EBug report"
+about: Report a bug in the Angular Framework
+---
+<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
+
+Oh hi there! 😄
+
+To expedite issue processing please search open and closed issues before submitting a new one.
+Existing issues often contain information about workarounds, resolution, or progress updates.
+
+🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
+
+
+# 🐞 bug report
+
+### Affected Package
+<!-- Can you pin-point one or more @angular/* packages as the source of the bug? -->
+<!-- ✍️edit: --> The issue is caused by package @angular/....
+
+
+### Is this a regression?
+
+<!-- Did this behavior use to work in the previous version? -->
+<!-- ✍️--> Yes, the previous version in which this bug was not present was: ....
+
+
+### Description
+
+<!-- ✍️--> A clear and concise description of the problem...
+
+
+## 🔬 Minimal Reproduction
+<!--
+Please create and share minimal reproduction of the issue starting with this template: https://stackblitz.com/fork/angular-issue-repro2
+-->
+<!-- ✍️--> https://stackblitz.com/...
+
+<!--
+If StackBlitz is not suitable for reproduction of your issue, please create a minimal GitHub repository with the reproduction of the issue.
+A good way to make a minimal reproduction is to create a new app via `ng new repro-app` and add the minimum possible code to show the problem. 
+Share the link to the repo below along with step-by-step instructions to reproduce the problem, as well as expected and actual behavior.
+
+Issues that don't have enough info and can't be reproduced will be closed.
+
+You can read more about issue submission guidelines here: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-submitting-an-issue
+-->
+
+## 🔥 Exception or Error
+<pre><code>
+<!-- If the issue is accompanied by an exception or an error, please share it below: -->
+<!-- ✍️-->
+
+</code></pre>
+
+
+## 🌍  Your Environment
+
+**Angular Version:**
+<pre><code>
+<!-- run `ng version` and paste output below -->
+<!-- ✍️-->
+
+</code></pre>
+
+**Anything else relevant?**
+<!-- ✍️Is this a browser specific issue? If so, please specify the browser and version. -->
+
+<!-- ✍️Do any of these matter: operating system, IDE, package manager, HTTP server, ...? If so, please mention it below. -->
@@ -1,86 +0,0 @@
-name: Bug Report
-description: Report a bug in the Angular Framework
-
-body:
-  - type: dropdown
-    id: affected-packages
-    attributes:
-      label: Which @angular/* package(s) are the source of the bug?
-      options:
-        - animations
-        - bazel
-        - common
-        - compiler-cli
-        - compiler
-        - core
-        - elements
-        - forms
-        - language-service
-        - localize
-        - platform-browser-dynamic
-        - platform-browser
-        - platform-server
-        - router
-        - service-worker
-        - upgrade
-        - zone.js
-        - Don't known / other
-      multiple: true
-    validations:
-      required: true
-
-  - type: dropdown
-    id: is-regression
-    attributes:
-      label: Is this a regression?
-      options:
-        - 'Yes'
-        - 'No'
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-    validations:
-      required: true
-
-  - type: input
-    id: reproduction
-    attributes:
-      label: Please provide a link to a minimal reproduction of the bug
-
-  - type: textarea
-    id: exception-or-error
-    attributes:
-      label: Please provide the exception or error you saw
-      render: true
-
-  - type: textarea
-    id: environment
-    attributes:
-      label: Please provide the environment you discovered this bug in (run `ng version`)
-      render: true
-      placeholder: |
-        Angular CLI: 12.0.5
-        Node: 14.17.0
-        Package Manager: yarn 1.22.10
-        OS: linux x64
-
-        Angular: 12.0.5
-        ... animations, cli, common, compiler, compiler-cli, core, forms
-        ... platform-browser, platform-browser-dynamic, router
-
-        Package                         Version
-        ---------------------------------------------------------
-        @angular-devkit/architect       0.1200.5
-        @angular-devkit/build-angular   12.0.5
-        @angular-devkit/core            12.0.5
-        rxjs                            6.6.7
-        typescript                      4.2.4
-
-  - type: textarea
-    id: other
-    attributes:
-      label: Anything else?
@@ -0,0 +1,32 @@
+---
+name: "\U0001F680Feature request"
+about: Suggest a feature for Angular Framework
+
+---
+<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
+
+Oh hi there! 😄 
+
+To expedite issue processing please search open and closed issues before submitting a new one.
+Existing issues often contain information about workarounds, resolution, or progress updates.
+
+🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
+
+
+# 🚀 feature request
+
+### Relevant Package
+<!-- Can you pin-point one or more @angular/* packages the are relevant for this feature request? -->
+<!-- ✍️edit: --> This feature request is for @angular/....
+
+
+### Description
+<!-- ✍️--> A clear and concise description of the problem or missing capability...
+
+
+### Describe the solution you'd like
+<!-- ✍️--> If you have a solution in mind, please describe it.
+
+
+### Describe alternatives you've considered
+<!-- ✍️--> Have you considered any alternative solutions or workarounds?
@@ -1,47 +0,0 @@
-name: 'Feature Request'
-description: Suggest a feature for Angular Framework
-
-body:
-  - type: dropdown
-    id: affected-packages
-    attributes:
-      label: Which @angular/* package(s) are relevant/related to the feature request?
-      options:
-        - animations
-        - bazel
-        - common
-        - compiler-cli
-        - compiler
-        - core
-        - elements
-        - forms
-        - language-service
-        - localize
-        - platform-browser-dynamic
-        - platform-browser
-        - platform-server
-        - router
-        - service-worker
-        - upgrade
-      multiple: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-    validations:
-      required: true
-
-  - type: textarea
-    id: proposed-solution
-    attributes:
-      label: Proposed solution
-    validations:
-      required: true
-
-  - type: textarea
-    id: alternatives-considered
-    attributes:
-      label: Alternatives considered
-    validations:
-      required: true
@@ -0,0 +1,55 @@
+---
+name: "📚 Docs or angular.io issue report"
+about: Report an issue in Angular's documentation or angular.io application
+
+---
+<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
+
+Oh hi there! 😄
+
+To expedite issue processing please search open and closed issues before submitting a new one.
+Existing issues often contain information about workarounds, resolution, or progress updates.
+
+🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
+
+# 📚 Docs or angular.io bug report
+
+### Description
+
+<!-- ✍️edit:--> A clear and concise description of the problem...
+
+
+## 🔬 Minimal Reproduction
+
+### What's the affected URL?**
+<!-- ✍️edit:--> https://angular.io/...
+
+### Reproduction Steps**
+<!-- If applicable please list the steps to take to reproduce the issue -->
+<!-- ✍️edit:-->
+
+### Expected vs Actual Behavior**
+<!-- If applicable please describe the difference between the expected and actual behavior after following the repro steps. -->
+<!-- ✍️edit:-->
+
+
+## 📷Screenshot
+<!-- Often a screenshot can help to capture the issue better than a long description. -->
+<!-- ✍️upload a screenshot:-->
+
+
+## 🔥 Exception or Error
+<pre><code>
+<!-- If the issue is accompanied by an exception or an error, please share it below: -->
+<!-- ✍️-->
+
+</code></pre>
+
+
+## 🌍  Your Environment
+
+### Browser info
+<!-- ✍️Is this a browser specific issue? If so, please specify the device, browser, and version. -->
+
+### Anything else relevant?
+<!-- ✍️Please provide additional info if necessary. -->
@@ -1,58 +0,0 @@
-name: 'Docs or angular.io Bug Report'
-description: Report an issue in Angular's documentation or angular.io application
-
-body:
-  - type: textarea
-    id: description
-    attributes:
-      label: Describe the problem that you experienced
-    validations:
-      required: true
-
-  - type: input
-    id: affected-url
-    attributes:
-      label: Enter the URL of the topic with the problem
-
-  - type: textarea
-    id: documentation-goal
-    attributes:
-      label: Describe what you were looking for in the documentation
-
-  - type: textarea
-    id: reproduction-steps
-    attributes:
-      label: Describe the actions that led you to experience the problem
-
-  - type: textarea
-    id: expected-vs-actual-behavior
-    attributes:
-      label: Describe what you want to experience that would fix the problem
-
-  - type: textarea
-    id: screenshot
-    attributes:
-      label: Add a screenshot if that helps illustrate the problem
-
-  - type: textarea
-    id: exception-or-error
-    attributes:
-      label: If this problem caused an exception or error, please paste it here
-      render: true
-      placeholder: |
-        ```
-        Paste the exception or error here inside a markdown code block,
-        which is annotated by three grave \(&grave;\) characters before and after the text block.
-        ```
-
-  - type: textarea
-    id: browser-info
-    attributes:
-      label: If the problem is browser-specific, please specify the device, OS, browser, and version
-      render: true
-
-  - type: textarea
-    id: additional-info
-    attributes:
-      label: Provide any additional information here in as much as detail as you can
-      render: true
@@ -1,54 +0,0 @@
-name: 'Angular DevTools'
-description: Report an issue or suggest a feature for Angular DevTools
-
-body:
-  - type: checkboxes
-    id: bug-report-or-feature-request
-    attributes:
-      label: Is this a bug report or a feature request?
-      description: Select one.
-      options:
-        - label: Bug Report
-        - label: Feature Request
-
-  - type: textarea
-    id: reproduction-steps
-    attributes:
-      label: Please provide the steps to reproduce the issue [Bug Report only]
-
-  - type: textarea
-    id: expected-vs-actual-behavior
-    attributes:
-      label: Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]
-
-  - type: textarea
-    id: screenshot
-    attributes:
-      label: Please provide a screenshot if possible [Bug Report only]
-
-  - type: textarea
-    id: exception-or-error
-    attributes:
-      label: Please provide the exception or error you saw [Bug Report only]
-      render: true
-
-  - type: textarea
-    id: browser-info
-    attributes:
-      label: Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]
-      render: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description [Feature Request only]
-
-  - type: textarea
-    id: proposed-solution
-    attributes:
-      label: Proposed solution [Feature Request only]
-
-  - type: textarea
-    id: alternatives-considered
-    attributes:
-      label: Alternatives considered [Feature Request only]
@@ -0,0 +1,11 @@
+---
+name: ⚠️ Security issue disclosure
+about: Report a security issue in Angular Framework, Material, or CLI
+
+---
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
+
+Please read https://angular.io/guide/security#report-issues on how to disclose security related issues.
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
@@ -0,0 +1,16 @@
+---
+name: "❓Support request"
+about: Questions and requests for support
+
+---
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
+
+Please do not file questions or support requests on the GitHub issues tracker.
+
+You can get your questions answered using other communication channels. Please see: 
+https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
+
+Thank you!
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
@@ -0,0 +1,13 @@
+---
+name: "\U0001F6E0️Angular CLI"
+about: Issues and feature requests for Angular CLI
+
+---
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
+
+Please file any Angular CLI issues at: https://github.com/angular/angular-cli/issues/new
+
+For the time being, we keep Angular CLI issues in a separate repository.
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
@@ -0,0 +1,13 @@
+---
+name: "\U0001F48EAngular Components"
+about: Issues and feature requests for Angular Components
+
+---
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
+
+Please file any Angular Components issues at: https://github.com/angular/components/issues/new
+
+For the time being, we keep Angular Components issues in a separate repository.
+
+🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
@@ -1,14 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Security issue disclosure
-    url: https://angular.io/guide/security#report-issues
-    about: Report a security issue in Angular Framework, CDK, Material, or CLI
-  - name: Angular CLI
-    url: https://github.com/angular/angular-cli/issues/new/choose
-    about: Issues and feature requests for Angular CLI
-  - name: Angular Material and Components Development Kit (CDK)
-    url: https://github.com/angular/components/issues/new/choose
-    about: Issues and feature requests for Angular Material
-  - name: Support Request
-    url: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#question
-    about: Questions and requests for support
@@ -1,7 +1,7 @@
 ## PR Checklist
 Please check if your PR fulfills the following requirements:

- [ ] The commit message follows our guidelines: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
+- [ ] The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
 - [ ] Tests for the changes have been added (for bug fixes / features)
 - [ ] Docs have been added / updated (for bug fixes / features)

@@ -1,17 +0,0 @@
-name: 'Installing Yarn dependencies'
-description: 'Installs the dependencies using Yarn'
-
-runs:
-  using: 'composite'
-  steps:
-    - uses: actions/cache@ab5e6d0c87105b4c9c2047343972218f562e4319 # v4
-      with:
-        path: |
-          ./node_modules/
-        # If just `WORKSPACE` or `yarn.lock` is changed, the most recent cache can be restored.
-        # See: https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows#example-using-the-cache-action.
-        key: v1-angular-main-deps-${{hashFiles('WORKSPACE')}}-${{hashFiles('yarn.lock')}}
-        restore-keys: v1-angular-main-deps-
-
-    - run: yarn install --frozen-lockfile --non-interactive
-      shell: bash
@@ -1,10 +1,10 @@
 # Configuration for angular-robot

-# options for the size plugin
+#options for the size plugin
 size:
-  disabled: true
+  disabled: false
  maxSizeIncrease: 2000
-  circleCiStatusName: 'ci/circleci: test'
+  circleCiStatusName: "ci/circleci: test_ivy_aot"

 # options for the merge plugin
 merge:
@@ -13,40 +13,79 @@ merge:
    # set to true to disable
    disabled: false
    # the name of the status
-    context: 'ci/angular: merge status'
+    context: "ci/angular: merge status"
    # text to show when all checks pass
-    successText: 'All checks passed!'
+    successText: "All checks passed!"
    # text to show when some checks are failing
-    failureText: 'The following checks are failing:'
+    failureText: "The following checks are failing:"

  # the g3 status will be added to your pull requests if they include files that match the patterns
  g3Status:
    # set to true to disable
-    disabled: true
+    disabled: false
    # the name of the status
-    context: 'google3'
+    context: "google3"
    # text to show when the status is pending, {{PRNumber}} will be replaced by the PR number
-    pendingDesc: 'Googler: run g3sync presubmit {{PRNumber}}'
+    pendingDesc: "Googler: run g3sync presubmit {{PRNumber}}"
    # text to show when the status is success
-    successDesc: 'Does not affect google3'
+    successDesc: "Does not affect google3"
    # link to use for the details
-    url: 'http://go/angular/g3sync'
+    url: "http://go/angular/g3sync"
    # list of patterns to check for the files changed by the PR
+    # this list must be manually kept in sync with google3/third_party/javascript/angular2/copy.bara.sky
    include:
+      - "LICENSE"
+      - "modules/benchmarks/**"
+      - "modules/system.d.ts"
+      - "packages/**"
+    # list of patterns to ignore for the files changed by the PR
    exclude:
+      - "packages/*"
+      - "packages/bazel/*"
+      - "packages/bazel/src/api-extractor/**"
+      - "packages/bazel/src/builders/**"
+      - "packages/bazel/src/ng_package/**"
+      - "packages/bazel/src/protractor/**"
+      - "packages/bazel/src/schematics/**"
+      - "packages/compiler-cli/ngcc/**"
+      - "packages/docs/**"
+      - "packages/elements/schematics/**"
+      - "packages/examples/**"
+      - "packages/language-service/**"
+      - "packages/localize/**"
+      - "packages/private/**"
+      - "packages/service-worker/**"
+      - "**/.gitignore"
+      - "**/.gitkeep"
+      - "**/yarn.lock"
+      - "**/package.json"
+      - "**/third_party/**"
+      - "**/tsconfig-build.json"
+      - "**/tsconfig.json"
+      - "**/rollup.config.js"
+      - "**/BUILD.bazel"
+      - "**/*.md"
+      - "packages/**/integrationtest/**"
+      - "packages/**/test/**"
+      - "packages/zone.js/*"
+      - "packages/zone.js/doc/**"
+      - "packages/zone.js/example/**"
+      - "packages/zone.js/scripts/**"

  # comment that will be added to a PR when there is a conflict, leave empty or set to false to disable
-  mergeConflictComment: "Hi @{{PRAuthor}}! This PR has merge conflicts due to recent upstream merges.\nPlease help to unblock it by resolving these conflicts. Thanks!"
+  mergeConflictComment: "Hi @{{PRAuthor}}! This PR has merge conflicts due to recent upstream merges.
+\nPlease help to unblock it by resolving these conflicts. Thanks!"

  # label to monitor
-  mergeLabel: 'action: merge'
+  mergeLabel: "PR action: merge"

  # adding any of these labels will also add the merge label
  mergeLinkedLabels:
-    - 'action: merge-assistance'
+    - "PR action: merge-assistance"

  # list of checks that will determine if the merge label can be added
  checks:
+
    # require that the PR has reviews from all requested reviewers
    #
    # This enables us to request reviews from both eng and tech writers, or multiple eng folks, and prevents accidental merges.
@@ -55,26 +94,39 @@ merge:

    # whether the PR shouldn't have a conflict with the base branch
    noConflict: true
-    # list of labels that a PR needs to have, checked with a regexp.
+    # list of labels that a PR needs to have, checked with a regexp (e.g. "PR target:" will work for the label "PR target: master")
    requiredLabels:
-      - 'target: *'
+      - "PR target: *"
+      - "cla: yes"

    # list of labels that a PR shouldn't have, checked after the required labels with a regexp
    forbiddenLabels:
-      - 'target: TBD'
-      - 'action: cleanup'
-      - 'action: review'
-      - 'state: blocked'
+      - "PR target: TBD"
+      - "PR action: cleanup"
+      - "PR action: review"
+      - "PR state: blocked"
+      - "cla: no"

    # list of PR statuses that need to be successful
    requiredStatuses:
-      - 'google-internal-tests'
-      - 'pullapprove'
+      - "ci/circleci: build"
+      - "ci/circleci: lint"
+      - "ci/circleci: publish_snapshot"
+      - "ci/angular: size"
+      - "cla/google"
+      - "google3"
+      - "pullapprove"
+

  # the comment that will be added when the merge label is added despite failing checks, leave empty or set to false to disable
  # {{MERGE_LABEL}} will be replaced by the value of the mergeLabel option
  # {{PLACEHOLDER}} will be replaced by the list of failing checks
-  mergeRemovedComment: "I see that you just added the `{{MERGE_LABEL}}` label, but the following checks are still failing:\n{{PLACEHOLDER}}\n\n**If you want your PR to be merged, it has to pass all the CI checks.**\n\nIf you can't get the PR to a green state due to flakes or broken `main`, please try rebasing to `main` and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help."
+  mergeRemovedComment: "I see that you just added the `{{MERGE_LABEL}}` label, but the following checks are still failing:
+\n{{PLACEHOLDER}}
+\n
+\n**If you want your PR to be merged, it has to pass all the CI checks.**
+\n
+\nIf you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help."

 # options for the triage plugin
 triage:
@@ -84,29 +136,24 @@ triage:
  defaultMilestone: 82,
  # arrays of labels that determine if an issue has been triaged by the caretaker
  l1TriageLabels:
-    - - 'area: *'
+    -
+      - "comp: *"
  # arrays of labels that determine if an issue has been fully triaged
  l2TriageLabels:
-    - - 'P0'
-      - 'area: *'
-    - - 'P1'
-      - 'area: *'
-    - - 'P2'
-      - 'area: *'
-    - - 'P3'
-      - 'area: *'
-    - - 'P4'
-      - 'area: *'
-    - - 'P5'
-      - 'area: *'
-    - - 'feature'
-      - 'area: *'
-    - - 'discussion'
-      - 'area: *'
-    - - 'needs clarification'
-      - 'area: *'
-    - - 'needs reproduction'
-      - 'area: *'
+    -
+      - "type: bug/fix"
+      - "severity*"
+      - "freq*"
+      - "comp: *"
+    -
+      - "type: feature"
+      - "comp: *"
+    -
+      - "type: refactor"
+      - "comp: *"
+    -
+      - "type: RFC / Discussion / question"
+      - "comp: *"

 # options for the triage PR plugin
 triagePR:
@@ -118,14 +165,19 @@ triagePR:
  defaultMilestone: 82,
  # arrays of labels that determine if a PR has been triaged by the caretaker
  l1TriageLabels:
-    - - 'area: *'
+    -
+      - "comp: *"
  # arrays of labels that determine if a PR has been fully triaged
  l2TriageLabels:
-    - - 'area: *'
+    -
+      - "type: *"
+      - "effort*"
+      - "risk*"
+      - "comp: *"

 # options for rerunning CI
 rerunCircleCI:
  # set to true to disable
  disabled: false
  # the label which when added triggers a rerun of the default CircleCI workflow
-  triggerRerunLabel: 'action: rerun CI at HEAD'
+  triggerRerunLabel: "PR action: rerun CI at HEAD"
@@ -1,38 +0,0 @@
-# This workflow builds the previews for pull requests when a certain label is applied.
-# The actual deployment happens as part of a dedicated second workflow to avoid security
-# issues where the building would otherwise occur in an authorized context where secrets
-# could be leaked. More details can be found here:
-
-# https://securitylab.github.com/research/github-actions-preventing-pwn-requests/.
-
-name: Build adev for preview deployment
-
-on:
-  pull_request:
-    types: [synchronize, labeled]
-
-permissions: read-all
-
-jobs:
-  adev-build:
-    runs-on: ubuntu-latest
-    if: |
-      (github.event.action == 'labeled' && github.event.label.name == 'adev: preview') ||
-      (github.event.action == 'synchronize' && contains(github.event.pull_request.labels.*.name, 'adev: preview'))
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Build adev to ensure it continues to work
-        run: yarn bazel build --config=aio_local_deps //adev:build
-      - uses: angular/dev-infra/github-actions/previews/pack-and-upload-artifact@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          workflow-artifact-name: 'adev-preview'
-          pull-number: '${{github.event.pull_request.number}}'
-          artifact-build-revision: '${{github.event.pull_request.head.sha}}'
-          deploy-directory: './dist/bin/adev/build/browser'
@@ -1,50 +0,0 @@
-# This workflow runs whenever the ADEV build workflow has completed. Deployment happens
-# as part of a dedicated second workflow to avoid security issues where the building would
-# otherwise occur in an authorized context where secrets could be leaked.
-#
-# More details can be found here:
-# https://securitylab.github.com/research/github-actions-preventing-pwn-requests/.
-
-name: Deploying adev preview to Firebase
-
-on:
-  workflow_run:
-    workflows: ['Build adev for preview deployment']
-    types: [completed]
-
-permissions:
-  # Needed in order to be able to comment on the pull request.
-  pull-requests: write
-  # Needed in order to checkout the repository
-  contents: read
-  # Needed in order to retrieve the artifacts from the previous job
-  actions: read
-
-env:
-  PREVIEW_PROJECT: ng-dev-previews
-  PREVIEW_SITE: ng-dev-previews-fw
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-    if: ${{ github.event.workflow_run.conclusion == 'success' }}
-    steps:
-      - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4
-        with:
-          token: '${{secrets.GITHUB_TOKEN}}'
-
-      - name: Configure Firebase deploy target
-        working-directory: ./
-        run: |
-          # We can use `npx` as the Firebase deploy actions uses it too.
-          npx -y firebase-tools@latest target:clear --config adev/firebase.json --project ${{env.PREVIEW_PROJECT}} hosting angular-docs
-          npx -y firebase-tools@latest target:apply --config adev/firebase.json --project ${{env.PREVIEW_PROJECT}} hosting angular-docs ${{env.PREVIEW_SITE}}
-
-      - uses: angular/dev-infra/github-actions/previews/upload-artifacts-to-firebase@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          github-token: '${{secrets.GITHUB_TOKEN}}'
-          workflow-artifact-name: 'adev-preview'
-          firebase-config-dir: './adev'
-          firebase-public-dir: './adev/build/browser'
-          firebase-project-id: '${{env.PREVIEW_PROJECT}}'
-          firebase-service-key: '${{secrets.FIREBASE_PREVIEW_SERVICE_TOKEN}}'
@@ -1,21 +0,0 @@
-name: DevInfra
-
-on:
-  push:
-  pull_request_target:
-    types: [opened, synchronize, reopened, ready_for_review, labeled]
-
-# Declare default permissions as read only.
-permissions:
-  contents: read
-
-jobs:
-  assistant_to_the_branch_manager:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
-        with:
-          persist-credentials: false
-      - uses: angular/dev-infra/github-actions/branch-manager@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}
@@ -1,68 +0,0 @@
-name: Run benchmark comparison
-
-on:
-  issue_comment:
-    types: [created]
-
-permissions: read-all
-
-jobs:
-  benchmark-compare:
-    runs-on: ubuntu-latest
-    if: ${{ github.event.issue.pull_request && startsWith(github.event.comment.body, '/benchmark-compare ')}}
-    steps:
-      - uses: TheModdingInquisition/actions-team-membership@a69636a92bc927f32c3910baac06bacc949c984c # v1.0
-        with:
-          team: 'team'
-          organization: angular
-          token: ${{secrets.BENCHMARK_COMPARE_MEMBERSHIP_GITHUB_TOKEN}}
-          exit: true
-
-      # Indicate that the benchmark command was received.
-      - uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043 # v4
-        with:
-          comment-id: ${{github.event.comment.id}}
-          token: '${{secrets.BENCHMARK_POST_RESULTS_GITHUB_TOKEN}}'
-          reactions: 'rocket'
-
-      - uses: alessbell/pull-request-comment-branch@aad01d65d6982b8eacabed5e9a684cd8ceb98da6 # v1.1
-        id: comment-branch
-
-      - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
-        with:
-          # Specify repository as the PR branch might be from a fork.
-          repository: ${{steps.comment-branch.outputs.head_owner}}/${{steps.comment-branch.outputs.head_repo}}
-          # Checkout the pull request and assume it being trusted given we've checked
-          # that the action was triggered by a team member.
-          ref: ${{steps.comment-branch.outputs.head_ref}}
-
-      - uses: ./.github/actions/yarn-install
-
-      - uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          bazelrc: ./.bazelrc.user
-
-      - name: Preparing benchmark for GitHub action
-        id: info
-        env:
-          # Untrusted input used in an executable code, must be wrapped as an env var to prevent injections
-          COMMENT_BODY: ${{ github.event.comment.body }}
-        run: yarn benchmarks prepare-for-github-action "$COMMENT_BODY"
-
-      - run: yarn benchmarks run-compare ${{steps.info.outputs.compareSha}} ${{steps.info.outputs.benchmarkTarget}}
-        id: benchmark
-        name: Running benchmark
-
-      - uses: peter-evans/create-or-update-comment@71345be0265236311c031f5c7866368bd1eff043 # v4
-        with:
-          issue-number: ${{github.event.issue.number}}
-          token: '${{secrets.BENCHMARK_POST_RESULTS_GITHUB_TOKEN}}'
-          body: |
-            ## Benchmark Test Results
-            **Test**: `${{steps.info.outputs.benchmarkTarget}}`
-
-            ### PR (${{steps.info.outputs.prHeadSha}})
-            ${{steps.benchmark.outputs.workingStageResultsText}}
-
-            ### Compare Ref (${{steps.info.outputs.compareSha}})
-            ${{steps.benchmark.outputs.comparisonResultsText}}
@@ -1,277 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches:
-      - main
-      - '[0-9]+.[0-9]+.x'
-  pull_request:
-    types: [opened, synchronize, reopened]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions: {}
-
-defaults:
-  run:
-    shell: bash
-
-jobs:
-  lint:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-          node-module-directories: |
-            ./node_modules
-            ./aio/node_modules
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Install node modules in aio
-        run: yarn install --frozen-lockfile --cwd aio
-      - name: Check code lint
-        run: yarn -s tslint
-      - name: Check for circular dependencies
-        run: yarn -s ts-circular-deps:check
-      - name: Validate pull approve configuration
-        run: yarn -s ng-dev pullapprove verify
-      - name: Validate angular robot configuration
-        run: yarn -s ng-dev ngbot verify
-      - name: Confirm code builds with typescript as expected
-        run: yarn -s check-tooling-setup
-      - name: Check commit message
-        # Commit message validation is only done on pull requests as its too late to validate once
-        # it has been merged.
-        if: github.event_name == 'pull_request'
-        run: yarn ng-dev commit-message validate-range ${{ github.event.pull_request.base.sha }} ${{ github.event.pull_request.head.sha }}
-      - name: Check code format
-        # Code formatting checks are only done on pull requests as its too late to validate once
-        # it has been merged.
-        if: github.event_name == 'pull_request'
-        run: yarn ng-dev format changed --check ${{ github.event.pull_request.base.sha }}
-
-  devtools:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Run unit tests
-        run: yarn devtools:test
-      - name: Test build
-        run: yarn devtools:build:chrome
-
-  test:
-    runs-on: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel Remote Caching
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Install node modules
-        run: yarn install --frozen-lockfile --network-timeout 100000
-      - name: Run CI tests for framework
-        run: yarn test:ci
-
-  adev:
-    runs-on:
-      labels: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Build adev to ensure it continues to work
-        run: yarn bazel test --config=aio_local_deps //adev:test
-
-  publish-snapshots:
-    if: github.event_name == 'push'
-    runs-on:
-      labels: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - run: echo "https://${{secrets.SNAPSHOT_BUILDS_GITHUB_TOKEN}}:@github.com" > ${HOME}/.git_credentials
-      - run: yarn build
-      - run: ./scripts/ci/publish-build-artifacts.sh
-
-  zone-js:
-    runs-on:
-      labels: ubuntu-latest-4core
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-          node-module-directories: |
-            ./node_modules
-            ./packages/zone.js/node_modules
-            ./packages/zone.js/test/typings/node_modules
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - run: |
-          yarn bazel build \
-          //packages/zone.js/bundles:zone.umd.js \
-          //packages/zone.js:npm_package \
-          //packages/zone.js/test/closure:closure_js \
-
-      - run: |
-          rm -Rf packages/zone.js/build
-          rm -Rf packages/zone.js/test/extra/*.umd.js
-
-          mkdir -p packages/zone.js/build/
-          mkdir -p packages/zone.js/build/test/
-
-          cp dist/bin/packages/zone.js/bundles/zone.umd.js packages/zone.js/build/zone.umd.js
-          cp dist/bin/packages/zone.js/npm_package/bundles/zone-mix.umd.js ./packages/zone.js/test/extra/
-          cp dist/bin/packages/zone.js/npm_package/bundles/zone-patch-electron.umd.js ./packages/zone.js/test/extra/
-          cp dist/bin/packages/zone.js/test/closure/zone.closure.mjs ./packages/zone.js/build/test/zone.closure.mjs
-
-        # Install
-      - run: yarn --cwd packages/zone.js install --frozen-lockfile --non-interactive
-        # Run zone.js tools tests
-      - run: yarn --cwd packages/zone.js promisefinallytest
-      - run: yarn --cwd packages/zone.js jest:test
-      - run: yarn --cwd packages/zone.js jest:nodetest
-      - run: yarn --cwd packages/zone.js electrontest
-      - run: yarn --cwd packages/zone.js/test/typings install --frozen-lockfile --non-interactive
-      - run: yarn --cwd packages/zone.js/test/typings test
-
-  bazel-saucelabs:
-    # TODO: Replace legacy job with Bazel saucelabs job.
-    if: github.event_name == 'push'
-    runs-on: ubuntu-latest-4core
-    env:
-      JOBS: 2
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-          # Checking out the pull request commit is intended here as we need to run the changed code tests.
-          ref: ${{ github.event.pull_request.head.sha }}
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel Remote Caching
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Saucelabs Variables
-        uses: angular/dev-infra/github-actions/saucelabs@50bb71e51d3372ca2e359adb9069f89beeac4ae7
-      - name: Set up Sauce Tunnel Daemon
-        run: yarn bazel run //tools/saucelabs-daemon/background-service -- $JOBS &
-        env:
-          SAUCE_TUNNEL_IDENTIFIER: angular-framework-${{ github.run_number }}
-      - name: Run all saucelabs bazel tests
-        run: |
-          TESTS=$(./node_modules/.bin/bazelisk query --output label '(kind(karma_web_test, ...) intersect attr("tags", "saucelabs", ...)) except attr("tags", "fixme-saucelabs", ...)')
-          yarn bazel test --config=saucelabs --jobs=$JOBS ${TESTS}
-
-  saucelabs:
-    runs-on: ubuntu-latest-4core
-    env:
-      SAUCE_TUNNEL_IDENTIFIER: angular-framework-${{ github.run_number }}
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Saucelabs Variables
-        uses: angular/dev-infra/github-actions/saucelabs@50bb71e51d3372ca2e359adb9069f89beeac4ae7
-      - name: Starting Saucelabs tunnel service
-        run: ./tools/saucelabs/sauce-service.sh run &
-      # Build test fixtures for a test that rely on Bazel-generated fixtures. Note that disabling
-      # specific tests which are reliant on such generated fixtures is not an option as SystemJS
-      # in the Saucelabs legacy job always fetches referenced files, even if the imports would be
-      # guarded by an check to skip in the Saucelabs legacy job. We should be good running such
-      # test in all supported browsers on Saucelabs anyway until this job can be removed.
-      - name: Preparing Bazel-generated fixtures required in legacy tests
-        run: |
-          yarn bazel build //packages/core/test:downleveled_es5_fixture //packages/common/locales
-          # Needed for the ES5 downlevel reflector test in `packages/core/test/reflection`.
-          mkdir -p dist/legacy-test-out/core/test/reflection/
-          cp dist/bin/packages/core/test/reflection/es5_downleveled_inheritance_fixture.js \
-            dist/legacy-test-out/core/test/reflection/es5_downleveled_inheritance_fixture.js
-          # Locale files are needed for i18n tests running within Saucelabs. These are added
-          # directly as sources so that the TypeScript compilation of `/packages/tsconfig.json`
-          # can succeed. Note that the base locale and currencies files are checked-in, so
-          # we do not need to re-generate those through Bazel.
-          mkdir -p packages/common/locales/extra
-          cp dist/bin/packages/common/locales/*.ts packages/common/locales
-          cp dist/bin/packages/common/locales/extra/*.ts packages/common/locales/extra
-      - name: Build bundle of tests to run on Saucelabs
-        run: node tools/legacy-saucelabs/build-saucelabs-test-bundle.mjs
-      - name: Wait and confirm Saucelabs tunnel has connected
-        run: ./tools/saucelabs/sauce-service.sh ready-wait
-        timeout-minutes: 3
-      - name: Running tests on Saucelabs.
-        run: KARMA_WEB_TEST_MODE=SL_REQUIRED yarn karma start ./karma-js.conf.js --single-run
-      - name: Stop Saucelabs tunnel service
-        run: ./tools/saucelabs/sauce-service.sh stop
-
-  adev-deploy:
-    needs: [adev]
-    if: needs.adev.result == 'success' && github.event_name == 'push' && github.ref_name == 'main'
-    env:
-      DEPLOY_PROJECT: angular-dev-site
-      DEPLOY_SITE: angular-dev-site
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Install node modules
-        run: yarn install --frozen-lockfile
-      - name: Build adev to ensure it continues to work
-        run: yarn bazel build --config=aio_local_deps //adev:build
-      - name: Move generated project files into deployment directory
-        run: cp -r dist/bin/adev/build adev/build
-      - name: Setup firebase context
-        run: |
-          npx -y firebase-tools@latest target:clear --config adev/firebase.json --project ${{ env.DEPLOY_PROJECT }} hosting angular-docs
-          npx -y firebase-tools@latest target:apply --config adev/firebase.json --project ${{ env.DEPLOY_PROJECT }} hosting angular-docs ${{ env.DEPLOY_SITE }}
-      - name: Deploy to firebase
-        uses: FirebaseExtended/action-hosting-deploy@120e124148ab7016bec2374e5050f15051255ba2 # v0.7.1
-        with:
-          entryPoint: './adev'
-          firebaseServiceAccount: ${{ secrets.ANGULAR_DEV_SITE_DEPLOY }}
-          projectId: ${{ env.DEPLOY_PROJECT }}
-          channelId: live
@@ -1,25 +0,0 @@
-name: DevInfra
-
-on:
-  pull_request_target:
-    types: [opened, synchronize, reopened]
-
-# Declare default permissions as read only.
-permissions:
-  contents: read
-
-jobs:
-  labels:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
-      - uses: angular/dev-infra/github-actions/commit-message-based-labels@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}
-  post_approval_changes:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
-      - uses: angular/dev-infra/github-actions/post-approval-changes@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}
@@ -1,21 +0,0 @@
-name: Google Internal Tests Enforcement
-
-on:
-  pull_request_target:
-    types: [opened, reopened, synchronize]
-
-permissions: {}
-
-jobs:
-  trigger:
-    permissions:
-      pull-requests: read
-      statuses: write
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
-      - uses: angular/dev-infra/github-actions/google-internal-tests@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          run-tests-guide-url: http://go/angular-g3sync-start
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          sync-config: ./.ng-dev/google-sync-config.json
@@ -0,0 +1,15 @@
+name: Lock closed inactive issues
+
+on:
+  schedule:
+    # Run at 16:00 every day
+    - cron: '0 16 * * *'
+
+jobs:
+  lock_closed:
+    if: github.repository == 'angular/angular'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: angular/dev-infra/github-actions/lock-closed@66462f6
+        with:
+          lock-bot-key: ${{ secrets.LOCK_BOT_PRIVATE_KEY }}
@@ -1,14 +0,0 @@
-name: Merge Ready
-
-on: pull_request_target
-
-# Declare default permissions as read only.
-permissions: {}
-
-jobs:
-  status:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: angular/dev-infra/github-actions/unified-status-check@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}
@@ -1,55 +0,0 @@
-name: Monitoring
-
-on:
-  schedule:
-    # Run at 10:00AM every day.
-    - cron: '0 10 * * *'
-
-permissions: {}
-
-defaults:
-  run:
-    shell: bash
-
-jobs:
-  check_aio:
-    runs-on: ubuntu-latest
-    env:
-      MINIMUM_PWA_SCORE: 95
-    strategy:
-      fail-fast: false
-      matrix:
-        version: ['https://next.angular.io/', 'https://angular.io/']
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-          node-module-directories: |
-            ./aio/node_modules
-      - name: Setup Bazel
-        uses: angular/dev-infra/github-actions/bazel/setup@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Setup Bazel RBE
-        uses: angular/dev-infra/github-actions/bazel/configure-remote@5774b71c01a55c4c998f858ee37d3b77ae704c31
-      - name: Install node modules in aio
-        run: yarn install --frozen-lockfile --cwd aio
-      - name: Run basic e2e and deployment config tests.
-        run: yarn --cwd aio test-production-url --test_env=TARGET_URL="${{ matrix.version }}"
-      - name: Run PWA-score tests.
-        run: yarn --cwd aio test-pwa-score "${{ matrix.version }}" "${{ env.MINIMUM_PWA_SCORE }}"
-      - name: Run a11y tests.
-        run: yarn --cwd aio test-a11y-score "${{ matrix.version }}"
-
-  check_contributor_links:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Initialize environment
-        uses: angular/dev-infra/github-actions/npm/checkout-and-setup-node@5774b71c01a55c4c998f858ee37d3b77ae704c31
-        with:
-          cache-node-modules: true
-          node-module-directories: |
-            ./aio/node_modules
-      - name: Install node modules in aio
-        run: yarn install --frozen-lockfile --cwd aio
-      - name: Check website provided in contributors.json file
-        run: node aio/scripts/test-external-urls.js
@@ -1,52 +0,0 @@
-name: OpenSSF Scorecard
-on:
-  branch_protection_rule:
-  schedule:
-    - cron: '0 0 * * 0'
-  push:
-    branches: [main]
-  workflow_dispatch:
-
-# Declare default permissions as read only.
-permissions:
-  contents: read
-
-jobs:
-  analysis:
-    name: Scorecards analysis
-    runs-on: ubuntu-latest
-    permissions:
-      # Needed to upload the results to code-scanning dashboard.
-      security-events: write
-      # Needed to publish results
-      id-token: write
-      actions: read
-      contents: read
-
-    steps:
-      - name: 'Checkout code'
-        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
-        with:
-          persist-credentials: false
-
-      - name: 'Run analysis'
-        uses: ossf/scorecard-action@0864cf19026789058feabb7e87baa5f140aac736 # v2.3.1
-        with:
-          results_file: results.sarif
-          results_format: sarif
-          repo_token: ${{ secrets.GITHUB_TOKEN }}
-          publish_results: true
-
-      # Upload the results as artifacts.
-      - name: 'Upload artifact'
-        uses: actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3 # v4.3.1
-        with:
-          name: SARIF file
-          path: results.sarif
-          retention-days: 5
-
-      # Upload the results to GitHub's code scanning dashboard.
-      - name: 'Upload to code-scanning'
-        uses: github/codeql-action/upload-sarif@05963f47d870e2cb19a537396c1f668a348c7d8f # v3.24.8
-        with:
-          sarif_file: results.sarif
@@ -1,44 +0,0 @@
-name: Update AIO Angular CLI help
-
-on:
-  workflow_dispatch:
-    inputs: {}
-  push:
-    branches:
-      - 'main'
-      - '[0-9]+.[0-9]+.x'
-
-# Declare default permissions as read only.
-permissions:
-  contents: read
-
-jobs:
-  update_cli_help:
-    name: Update Angular CLI help (if necessary)
-    if: github.repository == 'angular/angular'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout the repository
-        uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
-        with:
-          # Setting `persist-credentials: false` prevents the github-action account from being the
-          # account that is attempted to be used for authentication, instead the remote is set to
-          # an authenticated URL.
-          persist-credentials: false
-          # This is needed as otherwise the PR creation will fail with `shallow update not allowed` when the forked branch is not in sync.
-          fetch-depth: 0
-      - name: Generate CLI help
-        run: node aio/scripts/update-cli-help/index.mjs
-        env:
-          ANGULAR_CLI_BUILDS_READONLY_GITHUB_TOKEN: ${{ secrets.ANGULAR_CLI_BUILDS_READONLY_GITHUB_TOKEN }}
-      - name: Create a PR (if necessary)
-        uses: angular/dev-infra/github-actions/create-pr-for-changes@1421ff04811ecb45812930c5d1f61d912880e75f
-        with:
-          branch-prefix: update-cli-help
-          pr-title: 'docs: update Angular CLI help [${{github.ref_name}}]'
-          pr-description: |
-            Updated Angular CLI help contents.
-          pr-labels: |
-            action: review
-            area: docs
-          angular-robot-token: ${{ secrets.ANGULAR_ROBOT_ACCESS_TOKEN }}
@@ -4,11 +4,7 @@
 /bazel-out
 /integration/bazel/bazel-*
 *.log
-/node_modules/
-
-# CircleCI temporary file for cache key computation.
-# See `save_month_to_file` in `.circleci/config.yml`.
-month.txt
+node_modules

 # Include when developing application packages.
 pubspec.lock
@@ -23,7 +19,6 @@ pubspec.lock
 .vscode/settings.json
 .vscode/tasks.json
 *.swo
-*.swp
 modules/.settings
 modules/.vscode
 .vimrc
@@ -45,19 +40,5 @@ yarn-error.log
 # User specific bazel settings
 .bazelrc.user

-# User specific ng-dev settings
-.ng-dev.user*
-
 .notes.md
 baseline.json
-
-# Ignore .history for the xyz.local-history VSCode extension
-.history
-
-# Husky
-.husky/_
-aio/content/examples/.DS_Store
-
-
-# Ignore cache created with the Angular CLI.
-.angular/
@@ -1,145 +0,0 @@
-<type>(<scope>): <summary>
-
-<Describe the motivation behind this change - explain WHY you are making this change. Wrap all lines
-at 100 characters.>
-
-Fixes #<issue number>
-
-# ────────────────────────────────────────── 100 chars ────────────────────────────────────────────┤
-
-
-# Example Commit Messages
-# =======================
-
-
-# ─── Example: Simple refactor ────────────────────────────────────────────────────────────────────┤
-# refactor(core): rename refreshDynamicEmbeddedViews to refreshEmbeddedViews
-#
-# Improve code readability. The original name no longer matches how the function is used.
-# ─────────────────────────────────────────────────────────────────────────────────────────────────┤
-
-
-# ─── Example: Simple docs change ─────────────────────────────────────────────────────────────────┤
-# docs: clarify the service limitation in providers.md guide
-#
-# Fixes #36332
-# ─────────────────────────────────────────────────────────────────────────────────────────────────┤
-
-
-# ─── Example: A bug fix ──────────────────────────────────────────────────────────────────────────┤
-# fix(ngcc): ensure lockfile is removed when `analyzeFn` fails
-#
-# Previously an error thrown in the `analyzeFn` would cause the ngcc process to exit immediately
-# without removing the lockfile, and potentially before the unlocker process had been successfully
-# spawned resulting in the lockfile being orphaned and left behind.
-#
-# Now we catch these errors and remove the lockfile as needed.
-# ─────────────────────────────────────────────────────────────────────────────────────────────────┤
-
-
-# ─── Example: Breaking change ────────────────────────────────────────────────────────────────────┤
-# feat(bazel): simplify ng_package by dropping esm5 and fesm5
-#
-# esm5 and fesm5 distributions are no longer needed and have been deprecated in the past.
-#
-# https://v9.angular.io/guide/deprecations#esm5-and-fesm5-code-formats-in-angular-npm-packages
-#
-# This commit modifies ng_package to no longer distribute these two formats in npm packages built by
-# ng_package (e.g. @angular/core).
-#
-# This commit intentionally doesn't fully clean up the ng_package rule to remove all traces of esm5
-# and fems5 build artifacts as that is a bigger cleanup and currently we are narrowing down the
-# scope of this change to the MVP needed for v10, which in this case is 'do not put esm5 and fesm5'
-# into the npm packages.
-#
-# More cleanup to follow: https://angular-team.atlassian.net/browse/FW-2143
-#
-# BREAKING CHANGE: esm5 and fesm5 format is no longer distributed in Angular's npm packages e.g.
-# @angular/core
-#
-# Angular CLI will automatically downlevel the code to es5 if differential loading is enabled in the
-# Angular project, so no action is required from Angular CLI users.
-#
-# If you are not using Angular CLI to build your application or library, and you need to be able to
-# build es5 artifacts, then you will need to downlevel the distributed Angular code to es5 on your
-# own.
-#
-#
-# Fixes #1234
-# ─────────────────────────────────────────────────────────────────────────────────────────────────┤
-
-
-
-# Angular Commit Message Format
-# =============================
-#
-# The full specification of the Angular Commit Message Format can be found at
-# https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
-#
-# The following is an excerpt of the specification with the most commonly needed info.
-#
-# Each commit message consists of a *header*, a *body*, and a *footer*.
-#
-# <header>
-# <BLANK LINE>
-# <body>
-# <BLANK LINE>
-# <footer>
-#
-# The header is mandatory.
-#
-# The body is mandatory for all commits except for those of scope "docs". When the body is required
-# it must be at least 20 characters long.
-#
-# The footer is optional.
-#
-# Any line of the commit message cannot be longer than 100 characters.
-#
-#
-# Commit Message Header
-# ---------------------
-#
-# <type>(<scope>): <short summary>
-#   │       │             │
-#   │       │             └─⫸ Summary in present tense. Not capitalized. No period at the end.
-#   │       │
-#   │       └─⫸ Commit Scope: animations|bazel|benchpress|common|compiler|compiler-cli|core|
-#   │                          elements|forms|http|language-service|localize|platform-browser|
-#   │                          platform-browser-dynamic|platform-server|router|service-worker|
-#   │                          upgrade|zone.js|packaging|changelog|docs-infra|migrations|ngcc|ve|
-#   │                          devtools
-#   │                          https://github.com/angular/angular/blob/main/CONTRIBUTING.md#scope
-#   │
-#   └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|style|test
-#                     https://github.com/angular/angular/blob/main/CONTRIBUTING.md#type
-#
-#
-# Commit Message Body
-# ---------------------
-#
-# Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor "fixes".
-#
-# Explain the motivation for the change in the commit message body. This commit message should
-# explain WHY you are making the change. You can include a comparison of the previous behavior with
-# the new behavior in order to illustrate the impact of the change.
-#
-#
-# Commit Message Footer
-# ---------------------
-#
-# The footer can contain information about breaking changes and is also the place to reference
-# GitHub issues, Jira tickets, and other PRs that this commit closes or is related to.
-#
-# ```
-# BREAKING CHANGE: <breaking change summary>
-# <BLANK LINE>
-# <breaking change description + migration instructions>
-# <BLANK LINE>
-# <BLANK LINE>
-# Fixes #<issue number>
-# ```
-#
-# Breaking Change section should start with the phrase "BREAKING CHANGE: " followed by a summary of
-# the breaking change, a blank line, and a detailed description of the breaking change that also
-# includes migration instructions.
-#
@@ -1,8 +0,0 @@
-set +e
-
-yarn -s ng-dev commit-message pre-commit-validate --file $1 2>/dev/null
-if [ $? -ne 0 ]; then
-  echo "WARNING: failed to run commit message validation (ng-dev commit-mesage pre-commit-validate)"
-fi
-
-exit 0;
@@ -1,8 +0,0 @@
-set +e
-
-yarn -s ng-dev format staged 2>/dev/null
-if [ $? -ne 0 ]; then
-  echo "WARNING: failed to run file formatting (ng-dev format staged)"
-fi
-
-exit 0;
@@ -1,8 +0,0 @@
-set +e
-
-yarn -s ng-dev commit-message restore-commit-message-draft $1 $2 2>/dev/null
-if [ $? -ne 0 ]; then
-  echo "WARNING: failed to attempt to restore commit message draft (ng-dev commit-message restore-commit-message-draft)"
-fi
-
-exit 0;
@@ -1,21 +0,0 @@
-import {CaretakerConfig} from '@angular/ng-dev';
-
-/** The configuration for `ng-dev caretaker` commands. */
-export const caretaker: CaretakerConfig = {
-  g3SyncConfigPath: './.ng-dev/google-sync-config.json',
-  githubQueries: [
-    {
-      name: 'Merge Queue',
-      query: `is:pr is:open status:success label:"action: merge"`,
-    },
-    {
-      name: 'Merge Assistance Queue',
-      query: `is:pr is:open label:"merge: caretaker note" label:"action: merge"`,
-    },
-    {
-      name: 'Initial Triage Queue',
-      query: `is:open no:milestone -draft:true`,
-    },
-  ],
-  caretakerGroup: 'angular-caretaker',
-};
@@ -1,38 +0,0 @@
-import {CommitMessageConfig} from '@angular/ng-dev';
-
-/**
- * The configuration for `ng-dev commit-message` commands.
- */
-export const commitMessage: CommitMessageConfig = {
-  maxLineLength: Infinity,
-  minBodyLength: 20,
-  minBodyLengthTypeExcludes: ['docs'],
-  scopes: [
-    'animations',
-    'bazel',
-    'benchpress',
-    'changelog',
-    'common',
-    'compiler',
-    'compiler-cli',
-    'core',
-    'dev-infra',
-    'devtools',
-    'docs-infra',
-    'elements',
-    'forms',
-    'http',
-    'language-service',
-    'localize',
-    'migrations',
-    'packaging',
-    'platform-browser',
-    'platform-browser-dynamic',
-    'platform-server',
-    'router',
-    'service-worker',
-    'upgrade',
-    've',
-    'zone.js',
-  ],
-};
@@ -1,15 +0,0 @@
-import {caretaker} from './caretaker.mjs';
-import {commitMessage} from './commit-message.mjs';
-import {format} from './format.mjs';
-import {github} from './github.mjs';
-import {pullRequest} from './pull-request.mjs';
-import {release} from './release.mjs';
-
-export {
-  commitMessage,
-  format,
-  github,
-  pullRequest,
-  caretaker,
-  release,
-};
@@ -1,81 +0,0 @@
-import {FormatConfig} from '@angular/ng-dev';
-
-/**
- * Configuration for the `ng-dev format` command.
- */
-export const format: FormatConfig = {
-  'prettier': {
-    'matchers': [
-      '**/*.{yaml,yml}',
-      'adev/**/*.{js,ts}',
-      'devtools/**/*.{js,ts}',
-      'tools/**/*.{js,ts}',
-      'modules/**/*.{js,ts}',
-      'scripts/**/*.{js,ts}',
-      'packages/animations/**/*.{js,ts}',
-      'packages/bazel/**/*.{js,ts}',
-      'packages/benchpress/**/*.{js,ts}',
-      'packages/common/**/*.{js,ts}',
-      'packages/docs/**/*.{js,ts}',
-      'packages/elements/**/*.{js,ts}',
-      'packages/examples/**/*.{js,ts}',
-      'packages/misc/**/*.{js,ts}',
-      'packages/private/**/*.{js,ts}',
-      'packages/router/**/*.{js,ts}',
-      'packages/service-worker/**/*.{js,ts}',
-      'packages/upgrade/**/*.{js,ts}',
-
-      // Do not format d.ts files as they are generated
-      '!**/*.d.ts',
-      // Both third_party and .yarn are directories containing copied code which should
-      // not be modified.
-      '!third_party/**',
-      '!.yarn/**',
-    ],
-  },
-  'clang-format': {
-    'matchers': [
-      '**/*.{js,ts}',
-      // TODO: burn down format failures and remove aio and integration exceptions.
-      '!aio/**',
-      '!integration/**',
-      // Both third_party and .yarn are directories containing copied code which should
-      // not be modified.
-      '!third_party/**',
-      '!.yarn/**',
-      // Do not format d.ts files as they are generated
-      '!**/*.d.ts',
-      // Do not format generated ng-dev script
-      '!dev-infra/ng-dev.js',
-      '!dev-infra/build-worker.js',
-      // Do not format compliance test-cases since they must match generated code
-      '!packages/compiler-cli/test/compliance/test_cases/**/*.js',
-      // Do not format the locale files which are checked-in for Google3, but generated using
-      // the `generate-locales-tool` from `packages/common/locales`.
-      '!packages/core/src/i18n/locale_en.ts',
-      '!packages/common/locales/closure-locale.ts',
-      '!packages/common/src/i18n/currencies.ts',
-      // Temporarily disable formatting for adev
-      '!adev/**',
-
-      // Migrated to prettier
-      '!devtools/**/*.{js,ts}',
-      '!tools/**/*.{js,ts}',
-      '!modules/**/*.{js,ts}',
-      '!scripts/**/*.{js,ts}',
-      '!packages/animations/**/*.{js,ts}',
-      '!packages/bazel/**/*.{js,ts}',
-      '!packages/benchpress/**/*.{js,ts}',
-      '!packages/common/**/*.{js,ts}',
-      '!packages/docs/**/*.{js,ts}',
-      '!packages/elements/**/*.{js,ts}',
-      '!packages/examples/**/*.{js,ts}',
-      '!packages/misc/**/*.{js,ts}',
-      '!packages/private/**/*.{js,ts}',
-      '!packages/router/**/*.{js,ts}',
-      '!packages/service-worker/**/*.{js,ts}',
-      '!packages/upgrade/**/*.{js,ts}',
-    ],
-  },
-  'buildifier': true,
-};
@@ -1,15 +0,0 @@
-# The file is inert unless it's explicitly included into the local git config via:
-#
-# ```
-# git config --add include.path '../.ng-dev/gitconfig'
-# ```
-#
-# Calling that command will append the following into `.git/config` of the current git workspace
-# (i.e. $GIT_DIR, typically `angular/.git/config`):
-#
-# ```
-# [include]
-#     path = ../.ng-dev/gitconfig
-# ```
-[commit]
-  template = .gitmessage
@@ -1,12 +0,0 @@
-import {GithubConfig} from '@angular/ng-dev';
-
-/**
- * Github configuration for the `ng-dev` command. This repository is used as
- * remote for the merge script and other utilities like `ng-dev pr rebase`.
- */
-export const github: GithubConfig = {
-  owner: 'angular',
-  name: 'angular',
-  mainBranchName: 'main',
-  useNgDevAuthService: true,
-};
@@ -1,55 +0,0 @@
-{
-  "syncedFilePatterns": [
-    "LICENSE",
-    "modules/benchmarks/**",
-    "packages/**"
-  ],
-  "separateFilePatterns": [
-    "packages/core/primitives/**"
-  ],
-  "alwaysExternalFilePatterns": [
-    "packages/*",
-    "packages/bazel/*",
-    "packages/bazel/src/*",
-    "packages/bazel/src/api-extractor/**",
-    "packages/bazel/src/builders/**",
-    "packages/bazel/src/ng_module/**",
-    "packages/bazel/src/ng_package/**",
-    "packages/bazel/src/protractor/**",
-    "packages/bazel/src/schematics/**",
-    "packages/bazel/src/types_bundle/**",
-    "packages/compiler-cli/linker/**",
-    "packages/compiler-cli/src/ngtsc/sourcemaps/**",
-    "packages/compiler-cli/src/ngtsc/testing/**",
-    "packages/compiler-cli/private/bazel.ts",
-    "packages/compiler-cli/private/localize.ts",
-    "packages/compiler-cli/private/tooling.ts",
-    "packages/compiler-cli/private/babel.d.ts",
-    "packages/compiler-cli/src/bin/**",
-    "packages/docs/**",
-    "packages/elements/schematics/**",
-    "packages/examples/**",
-    "packages/localize/**",
-    "packages/private/**",
-    "packages/service-worker/**",
-    "packages/common/locales/generate-locales-tool/**",
-    "packages/common/locales/index.bzl",
-    "packages/http/**",
-    "**/.gitignore",
-    "**/.gitkeep",
-    "**/third_party/**",
-    "**/tsconfig-build.json",
-    "**/tsconfig-tsec.json",
-    "**/tsconfig.json",
-    "**/rollup.config.js",
-    "**/BUILD.bazel",
-    "**/*.md",
-    "packages/**/integrationtest/**",
-    "packages/**/test/**",
-    "packages/zone.js/*",
-    "packages/zone.js/dist/**",
-    "packages/zone.js/doc/**",
-    "packages/zone.js/example/**",
-    "packages/zone.js/scripts/**"
-  ]
-}
@@ -1,25 +0,0 @@
-import {PullRequestConfig} from '@angular/ng-dev';
-
-/**
- * Configuration for the merge tool in `ng-dev`. This sets up the labels which
- * are respected by the merge script (e.g. the target labels).
- */
-export const pullRequest: PullRequestConfig = {
-  githubApiMerge: false,
-  requiredBaseCommits: {
-    // PRs that target either `main` or the patch branch, need to be rebased
-    // on top of the latest commit message validation fix.
-    // These SHAs are the commits that update the required license text in the header.
-    'main': '5aeb9a4124922d8ac08eb73b8f322905a32b0b3a',
-    '10.0.x': '27b95ba64a5d99757f4042073fd1860e20e3ed24',
-  },
-  // `dev-infra` and `docs-infra` are not affecting the public NPM packages. Similarly,
-  // the `bazel` package is not considered part of the public API so that features
-  // can land in patch branches.
-  targetLabelExemptScopes: ['dev-infra', 'docs-infra', 'bazel'],
-  // enables specific validations during the pull request merge process
-  validators: {
-    assertEnforceTested: true,
-    assertIsolatedSeparateFiles: true,
-  },
-};
@@ -1,34 +0,0 @@
-import {ReleaseConfig} from '@angular/ng-dev';
-
-/** Configuration for the `ng-dev release` command. */
-export const release: ReleaseConfig = {
-  publishRegistry: 'https://wombat-dressing-room.appspot.com',
-  representativeNpmPackage: '@angular/core',
-  npmPackages: [
-    {name: '@angular/animations'},
-    {name: '@angular/common'},
-    {name: '@angular/compiler'},
-    {name: '@angular/compiler-cli'},
-    {name: '@angular/core'},
-    {name: '@angular/elements'},
-    {name: '@angular/forms'},
-    {name: '@angular/language-service'},
-    {name: '@angular/localize'},
-    {name: '@angular/platform-browser'},
-    {name: '@angular/platform-browser-dynamic'},
-    {name: '@angular/platform-server'},
-    {name: '@angular/router'},
-    {name: '@angular/service-worker'},
-    {name: '@angular/upgrade'},
-  ],
-  buildPackages: async () => {
-    // The buildTargetPackages function is loaded at runtime as the loading the script
-    // causes an invocation of Bazel.
-    const {performNpmReleaseBuild} = await import('../scripts/build/package-builder.mjs');
-    return performNpmReleaseBuild();
-  },
-  releaseNotes: {
-    hiddenScopes: ['aio', 'bazel', 'dev-infra', 'docs-infra', 'zone.js', 'devtools'],
-  },
-  releasePrLabels: ['area: build & ci', 'action: merge', 'PullApprove: disable'],
-};
@@ -1,10 +0,0 @@
-{
-  "compilerOptions": {
-    "strict": true,
-    "target": "es2020",
-    "module": "Node16",
-    "noEmit": true,
-    "skipLibCheck": true,
-    "types": []
-  }
-}
@@ -1 +0,0 @@
-engine-strict = true
@@ -1 +1 @@
-18.18.2
+12.14.1
@@ -1,10 +0,0 @@
-{
-  "printWidth": 100,
-  "tabWidth": 2,
-  "tabs": false,
-  "embeddedLanguageFormatting": "off",
-  "singleQuote": true,
-  "semicolon": true,
-  "quoteProps": "preserve",
-  "bracketSpacing": false
-}
@@ -6,15 +6,15 @@ This folder contains opt-in [Workspace Settings](https://code.visualstudio.com/d

 To use the recommended configurations follow the steps below:

- install the recommended extensions in `.vscode/extensions.json`
+- install the recommneded extensions in `.vscode/extensions.json`
 - copy (or link) `.vscode/recommended-settings.json` to `.vscode/settings.json`
 - copy (or link) `.vscode/recommended-launch.json` to `.vscode/launch.json`
 - copy (or link) `.vscode/recommended-tasks.json` to `.vscode/tasks.json`
 - restart the editor

-If you already have your custom workspace settings, you should instead manually merge the file contents.
+If you already have your custom workspace settings you should instead manually merge the file contents.

-This isn't an automatic process, so you will need to repeat it when settings are updated.
+This isn't an automatic process so you will need to repeat it when settings are updated.

 To see the recommended extensions select "Extensions: Show Recommended Extensions" in the [Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette).

@@ -22,4 +22,4 @@ To see the recommended extensions select "Extensions: Show Recommended Extension

 If you wish to add extra configuration items please keep in mind any modifications you make here will be used by many users.

-Try to keep these settings/configurations to things that help facilitate the development process and avoid altering the user workflow whenever possible.
+Try to keep these settings/configuations to things that help facilitate the development process and avoid altering the user workflow whenever possible.
@@ -1,11 +1,15 @@
 {
-  // See https://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
+  // See http://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
  // Extension identifier format: ${publisher}.${name}. Example: vscode.csharp

  // List of extensions which should be recommended for users of this workspace.
  "recommendations": [
-    "BazelBuild.vscode-bazel",
+    "devondcarew.bazel-code",
+    "gkalpak.aio-docs-utils",
    "ms-vscode.vscode-typescript-tslint-plugin",
    "xaver.clang-format",
+    // The following extensions are useful when working on angular.io (i.e. inside the `aio/` directory).
+    //"angular.ng-template",
+    //"dbaeumer.vscode-eslint",
  ],
 }
@@ -16,7 +16,6 @@
      "remoteRoot": "${workspaceRoot}",
      "stopOnEntry": false,
      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
    },
    {
      "name": "Attach to bazel test ... --config=debug (no source maps)",
@@ -30,46 +29,57 @@
      "remoteRoot": "${workspaceRoot}",
      "stopOnEntry": false,
      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
    },
    {
      "name": "IVY:packages/core/test/acceptance",
      "type": "node",
      "request": "launch",
      "program": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": ["test", "packages/core/test/acceptance", "--config=debug"],
+      "args": [
+        "test",
+        "--config=ivy",
+        "packages/core/test/acceptance",
+        "--config=debug"
+      ],
      "port": 9229,
      "address": "localhost",
      "restart": true,
      "sourceMaps": true,
      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
    },
    {
      "name": "IVY:packages/core/test/render3",
      "type": "node",
      "request": "launch",
      "program": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": ["test", "packages/core/test/render3", "--config=debug"],
+      "args": [
+        "test",
+        "--config=ivy",
+        "packages/core/test/render3",
+        "--config=debug"
+      ],
      "port": 9229,
      "address": "localhost",
      "restart": true,
      "sourceMaps": true,
      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
    },
    {
      "name": "IVY:packages/core/test",
      "type": "node",
      "request": "launch",
      "program": "${workspaceFolder}/node_modules/.bin/bazelisk",
-      "args": ["test", "packages/core/test", "--config=debug"],
+      "args": [
+        "test",
+        "--config=ivy",
+        "packages/core/test",
+        "--config=debug"
+      ],
      "port": 9229,
      "address": "localhost",
      "restart": true,
      "sourceMaps": true,
      "timeout": 600000,
-      "outFiles": ["${workspaceFolder}/dist/out/**/packages/**/*.js"]
-    }
+    },
  ]
 }
@@ -26,7 +26,6 @@
    "**/bazel-out": true,
    "**/dist": true,
    "**/aio/src/generated": true,
-    ".history": true,
  },
  "git.ignoreLimitWarning": true,
-}
+}
@@ -9,6 +9,7 @@
      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
      "args": [
        "test",
+        "--config=ivy",
        "packages/core/test",
        "packages/core/test/acceptance",
        "packages/core/test/render3",
@@ -41,6 +42,7 @@
      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
      "args": [
        "test",
+        "--config=ivy",
        "packages/core/test/acceptance",
      ],
      "group": "test",
@@ -69,6 +71,7 @@
      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
      "args": [
        "test",
+        "--config=ivy",
        "packages/core/test",
      ],
      "group": "test",
@@ -97,6 +100,7 @@
      "command": "${workspaceFolder}/node_modules/.bin/bazelisk",
      "args": [
        "test",
+        "--config=ivy",
        "packages/core/test/render3",
      ],
      "group": "test",
@@ -2,4 +2,4 @@
 # yarn lockfile v1


-yarn-path ".yarn/releases/yarn-1.22.19.cjs"
+yarn-path ".yarn/releases/yarn-1.21.1.js"
@@ -1,82 +1,50 @@
-load("//tools:defaults.bzl", "nodejs_binary")
-load("@build_bazel_rules_nodejs//:index.bzl", "js_library")
-load("//:yarn.bzl", "YARN_PATH")
-
 package(default_visibility = ["//visibility:public"])

 exports_files([
    "LICENSE",
+    "protractor-perf.conf.js",
    "karma-js.conf.js",
    "browser-providers.conf.js",
-    YARN_PATH,
-    "scripts/ci/bazel-payload-size.sh",
+    "scripts/ci/track-payload-size.sh",
    "scripts/ci/payload-size.sh",
    "scripts/ci/payload-size.js",
    "package.json",
-    "angular.json",
 ])

-filegroup(
-    # filegroup is needed so that this package.json file can be a dep
-    # in a js_library target, which doesn't allow source file deps
-    name = "package_json",
-    srcs = ["package.json"],
-)
-
 alias(
    name = "tsconfig.json",
    actual = "//packages:tsconfig-build.json",
 )

-js_library(
-    name = "browser-providers",
+filegroup(
+    name = "web_test_bootstrap_scripts",
+    # do not sort
    srcs = [
-        "browser-providers.conf.d.ts",
-        "browser-providers.conf.js",
+        "@npm//:node_modules/core-js/client/core.js",
+        "//packages/zone.js/dist:zone.js",
+        "//packages/zone.js/dist:zone-testing.js",
+        "//packages/zone.js/dist:task-tracking.js",
+        "//:test-events.js",
+        "//:shims_for_IE.js",
+        # Including systemjs because it defines `__eval`, which produces correct stack traces.
+        "@npm//:node_modules/systemjs/dist/system.src.js",
+        "@npm//:node_modules/reflect-metadata/Reflect.js",
    ],
 )

 filegroup(
    name = "angularjs_scripts",
    srcs = [
-        # We also declare the unminified AngularJS files since these can be used for
+        # We also declare the unminfied AngularJS files since these can be used for
        # local debugging (e.g. see: packages/upgrade/test/common/test_helpers.ts)
+        "@npm//:node_modules/angular/angular.js",
+        "@npm//:node_modules/angular/angular.min.js",
        "@npm//:node_modules/angular-1.5/angular.js",
        "@npm//:node_modules/angular-1.5/angular.min.js",
        "@npm//:node_modules/angular-1.6/angular.js",
        "@npm//:node_modules/angular-1.6/angular.min.js",
-        "@npm//:node_modules/angular-1.7/angular.js",
-        "@npm//:node_modules/angular-1.7/angular.min.js",
+        "@npm//:node_modules/angular-mocks/angular-mocks.js",
        "@npm//:node_modules/angular-mocks-1.5/angular-mocks.js",
        "@npm//:node_modules/angular-mocks-1.6/angular-mocks.js",
-        "@npm//:node_modules/angular-mocks-1.7/angular-mocks.js",
-        "@npm//:node_modules/angular-mocks-1.8/angular-mocks.js",
-        "@npm//:node_modules/angular-1.8/angular.js",
-        "@npm//:node_modules/angular-1.8/angular.min.js",
    ],
 )
-
-# Detect if the build is running under --stamp
-config_setting(
-    name = "stamp",
-    values = {"stamp": "true"},
-)
-
-nodejs_binary(
-    name = "yarn_vendored",
-    data = [".yarn/releases/yarn-1.22.19.cjs"],
-    entry_point = ".yarn/releases/yarn-1.22.19.cjs",
-    visibility = [
-        "//aio/tools/examples/shared:__pkg__",
-        "//integration:__subpackages__",
-    ],
-)
-
-alias(
-    name = "sauce_connect",
-    actual = select({
-        "@npm//@angular/build-tooling/bazel/constraints:linux_x64": "@sauce_connect_linux_amd64//:bin/sc",
-        "@npm//@angular/build-tooling/bazel/constraints:macos_x64": "@sauce_connect_mac//:bin/sc",
-        "@npm//@angular/build-tooling/bazel/constraints:macos_arm64": "@sauce_connect_mac//:bin/sc",
-    }),
-)
@@ -1,79 +1,12 @@
-# Contributor Covenant Code of Conduct
+# Contributor Code of Conduct
+## Version 0.3b-angular

-## Our Pledge
+As contributors and maintainers of the Angular project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.

-In the interest of fostering a safe and welcoming environment, we as
-the Angular team pledge to make participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity, gender expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+Communication through any of Angular's channels (GitHub, Gitter, IRC, mailing lists, Google+, Twitter, etc.) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.

-## Our Standards
+We promise to extend courtesy and respect to everyone involved in this project regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to the Angular project to do the same.

-Examples of behavior that contributes to creating a positive environment
-include:
+If any member of the community violates this code of conduct, the maintainers of the Angular project may take action, removing issues, comments, and PRs or blocking accounts as deemed appropriate.

-* Use welcoming and inclusive language
-* Respect each other
-* Provide and gracefully accept constructive criticism
-* Show empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* The use of sexualized language or imagery
-* Unwelcome sexual attention or advances
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Angular team are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Angular team have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, and to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies to all Angular communication channels - online or in person,
-and it also applies when an individual is representing the project or its community in
-public spaces. Examples of representing a project or community include using an official
-project e-mail address, posting via an official social media account, or acting
-as an appointed representative at an online or offline event. Representation of
-a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the Angular team at conduct@angular.io. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The Angular team
-will maintain confidentiality with regard to the reporter of an incident.
-Enforcement may result in an indefinite ban from all official Angular communication
-channels, or other actions as deemed appropriate by the Angular team.
-
-Angular maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-### Appeal
-
-If you are banned you may contest the decision. To do so email conduct@angular.io with the subject line "Repeal Ban for {{your name here}}" and body with the responses to the following:
-
-* Why do you believe you did not violate the Code of Conduct?
-* Were other factors involved in this situation the leadership team may have been unaware of?
-* Why do you wish to be a part of the Angular community?
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+If you are subject to or witness unacceptable behavior, or have any other concerns, please email us at [conduct@angular.io](mailto:conduct@angular.io).
@@ -1,7 +1,7 @@
 # Contributing to Angular

-We would love for you to contribute to Angular and help make it even better than it is today!
-As a contributor, here are the guidelines we would like you to follow:
+We would love for you to contribute to Angular and help make it even better than it is
+today! As a contributor, here are the guidelines we would like you to follow:

 - [Code of Conduct](#coc)
 - [Question or Problem?](#question)
@@ -12,63 +12,50 @@ As a contributor, here are the guidelines we would like you to follow:
 - [Commit Message Guidelines](#commit)
 - [Signing the CLA](#cla)

-
 ## <a name="coc"></a> Code of Conduct
-
-Help us keep Angular open and inclusive.
-Please read and follow our [Code of Conduct][coc].
-
+Help us keep Angular open and inclusive. Please read and follow our [Code of Conduct][coc].

 ## <a name="question"></a> Got a Question or Problem?

-Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests.
-Instead, we recommend using [Stack Overflow](https://stackoverflow.com/questions/tagged/angular) to ask support-related questions. When creating a new question on Stack Overflow, make sure to add the `angular` tag.
+Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests. You've got much better chances of getting your question answered on [Stack Overflow](https://stackoverflow.com/questions/tagged/angular) where the questions should be tagged with tag `angular`.

 Stack Overflow is a much better place to ask questions since:

 - there are thousands of people willing to help on Stack Overflow
- questions and answers stay available for public viewing so your question/answer might help someone else
+- questions and answers stay available for public viewing so your question / answer might help someone else
 - Stack Overflow's voting system assures that the best answers are prominently visible.

 To save your and our time, we will systematically close all issues that are requests for general support and redirect people to Stack Overflow.

-If you would like to chat about the question in real-time, you can reach out via [our Discord server][discord].
-
+If you would like to chat about the question in real-time, you can reach out via [our gitter channel][gitter].

 ## <a name="issue"></a> Found a Bug?
-
-If you find a bug in the source code, you can help us by [submitting an issue](#submit-issue) to our [GitHub Repository][github].
-Even better, you can [submit a Pull Request](#submit-pr) with a fix.
-
+If you find a bug in the source code, you can help us by
+[submitting an issue](#submit-issue) to our [GitHub Repository][github]. Even better, you can
+[submit a Pull Request](#submit-pr) with a fix.

 ## <a name="feature"></a> Missing a Feature?
-You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub Repository.
-If you would like to *implement* a new feature, please consider the size of the change in order to determine the right steps to proceed:
-
-* For a **Major Feature**, first open an issue and outline your proposal so that it can be discussed.
-  This process allows us to better coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully accepted into the project.
-
-  **Note**: Adding a new topic to the documentation, or significantly re-writing a topic, counts as a major feature.
+You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub
+Repository. If you would like to *implement* a new feature, please submit an issue with
+a proposal for your work first, to be sure that we can use it.
+Please consider what kind of change it is:

+* For a **Major Feature**, first open an issue and outline your proposal so that it can be
+discussed. This will also allow us to better coordinate our efforts, prevent duplication of work,
+and help you to craft the change so that it is successfully accepted into the project.
 * **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).

-
 ## <a name="submit"></a> Submission Guidelines

-
 ### <a name="submit-issue"></a> Submitting an Issue

-Before you submit an issue, please search the issue tracker. An issue for your problem might already exist and the discussion might inform you of workarounds readily available.
+Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.

-We want to fix all the issues as soon as possible, but before fixing a bug, we need to reproduce and confirm it.
-In order to reproduce bugs, we require that you provide a minimal reproduction.
-Having a minimal reproducible scenario gives us a wealth of important information without going back and forth to you with additional questions.
+We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, we will systematically ask you to provide a minimal reproduction. Having a minimal reproducible scenario gives us a wealth of important information without going back & forth to you with additional questions.

 A minimal reproduction allows us to quickly confirm a bug (or point out a coding problem) as well as confirm that we are fixing the right problem.

-We require a minimal reproduction to save maintainers' time and ultimately be able to fix more bugs.
-Often, developers find coding problems themselves while preparing a minimal reproduction.
-We understand that sometimes it might be hard to extract essential bits of code from a larger codebase, but we really need to isolate the problem before we can fix it.
+We will be insisting on a minimal reproduction scenario in order to save maintainers time and ultimately be able to fix more bugs. Interestingly, from our experience, users often find coding problems themselves while preparing a minimal reproduction. We understand that sometimes it might be hard to extract essential bits of code from a larger codebase but we really need to isolate the problem before we can fix it.

 Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you, we are going to close an issue that doesn't have enough info to be reproduced.

@@ -76,104 +63,57 @@ You can file new issues by selecting from our [new issue templates](https://gith


 ### <a name="submit-pr"></a> Submitting a Pull Request (PR)
-
 Before you submit your Pull Request (PR) consider the following guidelines:

-1. Search [GitHub](https://github.com/angular/angular/pulls) for an open or closed PR that relates to your submission.
-   You don't want to duplicate existing efforts.
-
-2. Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add.
-   Discussing the design upfront helps to ensure that we're ready to accept your work.
-
-3. Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs.
-   We cannot accept code without a signed CLA.
-   Make sure you author all contributed Git commits with email address associated with your CLA signature.
-
-4. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the angular/angular repo.
-
-5. In your forked repository, make your changes in a new git branch:
+1. Search [GitHub](https://github.com/angular/angular/pulls) for an open or closed PR
+  that relates to your submission. You don't want to duplicate effort.
+1. Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add.
+  Discussing the design up front helps to ensure that we're ready to accept your work.
+1. Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs.
+  We cannot accept code without this. Make sure you sign with the primary email address of the Git identity that has been granted access to the Angular repository.
+1. Fork the angular/angular repo.
+1. Make your changes in a new git branch:

     ```shell
-     git checkout -b my-fix-branch main
+     git checkout -b my-fix-branch master
     ```

-6. Create your patch, **including appropriate test cases**.
-
-7. Follow our [Coding Rules](#rules).
-
-8. Run the full Angular test suite, as described in the [developer documentation][dev-doc], and ensure that all tests pass.
-
-9. Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit).
-   Adherence to these conventions is necessary because release notes are automatically generated from these messages.
+1. Create your patch, **including appropriate test cases**.
+1. Follow our [Coding Rules](#rules).
+1. Run the full Angular test suite, as described in the [developer documentation][dev-doc],
+  and ensure that all tests pass.
+1. Commit your changes using a descriptive commit message that follows our
+  [commit message conventions](#commit). Adherence to these conventions
+  is necessary because release notes are automatically generated from these messages.

     ```shell
-     git commit --all
+     git commit -a
     ```
-    Note: the optional commit `--all` command line option will automatically "add" and "rm" edited files.
+    Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.

-10. Push your branch to GitHub:
+1. Push your branch to GitHub:

    ```shell
    git push origin my-fix-branch
    ```

-11. In GitHub, send a pull request to `angular:main`.
-
-### Reviewing a Pull Request
-
-The Angular team reserves the right not to accept pull requests from community members who haven't been good citizens of the community. Such behavior includes not following the [Angular code of conduct](https://github.com/angular/code-of-conduct) and applies within or outside of Angular managed channels.
-
-#### Addressing review feedback
-
-If we ask for changes via code reviews then:
-
-1. Make the required updates to the code.
-
-2. Re-run the Angular test suites to ensure tests are still passing.
-
-3. Create a fixup commit and push to your GitHub repository (this will update your Pull Request):
+1. In GitHub, send a pull request to `angular:master`.
+* If we suggest changes then:
+  * Make the required updates.
+  * Re-run the Angular test suites to ensure tests are still passing.
+  * Rebase your branch and force push to your GitHub repository (this will update your Pull Request):

    ```shell
-    git commit --all --fixup HEAD
-    git push
+    git rebase master -i
+    git push -f
    ```

-    For more info on working with fixup commits see [here](docs/FIXUP_COMMITS.md).
-
 That's it! Thank you for your contribution!

-
-##### Updating the commit message
-
-A reviewer might often suggest changes to a commit message (for example, to add more context for a change or adhere to our [commit message guidelines](#commit)).
-In order to update the commit message of the last commit on your branch:
-
-1. Check out your branch:
-
-    ```shell
-    git checkout my-fix-branch
-    ```
-
-2. Amend the last commit and modify the commit message:
-
-    ```shell
-    git commit --amend
-    ```
-
-3. Push to your GitHub repository:
-
-    ```shell
-    git push --force-with-lease
-    ```
-
-> NOTE:<br />
-> If you need to update the commit message of an earlier commit, you can use `git rebase` in interactive mode.
-> See the [git docs](https://git-scm.com/docs/git-rebase#_interactive_mode) for more details.
-
-
 #### After your pull request is merged

-After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository:
+After your pull request is merged, you can safely delete your branch and pull the changes
+from the main (upstream) repository:

 * Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:

@@ -181,10 +121,10 @@ After your pull request is merged, you can safely delete your branch and pull th
    git push origin --delete my-fix-branch
    ```

-* Check out the main branch:
+* Check out the master branch:

    ```shell
-    git checkout main -f
+    git checkout master -f
    ```

 * Delete the local branch:
@@ -193,180 +133,133 @@ After your pull request is merged, you can safely delete your branch and pull th
    git branch -D my-fix-branch
    ```

-* Update your local `main` with the latest upstream version:
+* Update your master with the latest upstream version:

    ```shell
-    git pull --ff upstream main
+    git pull --ff upstream master
    ```

-
 ## <a name="rules"></a> Coding Rules
 To ensure consistency throughout the source code, keep these rules in mind as you are working:

 * All features or bug fixes **must be tested** by one or more specs (unit-tests).
-* All public API methods **must be documented**.
-* We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at **100 characters**.
+* All public API methods **must be documented**. (Details TBC).
+* We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at
+  **100 characters**. An automated formatter is available, see
+  [DEVELOPER.md](docs/DEVELOPER.md#clang-format).

-   An automated formatter is available, see [DEVELOPER.md](docs/DEVELOPER.md#clang-format).
+## <a name="commit"></a> Commit Message Guidelines

+We have very precise rules over how our git commit messages can be formatted.  This leads to **more
+readable messages** that are easy to follow when looking through the **project history**.  But also,
+we use the git commit messages to **generate the Angular change log**.

-## <a name="commit"></a> Commit Message Format
-
-*This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].*
-
-We have very precise rules over how our Git commit messages must be formatted.
-This format leads to **easier to read commit history**.
-
-Each commit message consists of a **header**, a **body**, and a **footer**.
-
+### Commit Message Format
+Each commit message consists of a **header**, a **body** and a **footer**.  The header has a special
+format that includes a **type**, a **scope** and a **subject**:

 ```
-<header>
+<type>(<scope>): <subject>
 <BLANK LINE>
 <body>
 <BLANK LINE>
 <footer>
 ```

-The `header` is mandatory and must conform to the [Commit Message Header](#commit-header) format.
+The **header** is mandatory and the **scope** of the header is optional.

-The `body` is mandatory for all commits except for those of type "docs".
-When the body is present it must be at least 20 characters long and must conform to the [Commit Message Body](#commit-body) format.
+Any line of the commit message cannot be longer than 100 characters! This allows the message to be easier
+to read on GitHub as well as in various git tools.

-The `footer` is optional. The [Commit Message Footer](#commit-footer) format describes what the footer is used for and the structure it must have.
+The footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.

-
-#### <a name="commit-header"></a>Commit Message Header
+Samples: (even more [samples](https://github.com/angular/angular/commits/master))

 ```
-<type>(<scope>): <short summary>
-  │       │             │
-  │       │             └─⫸ Summary in present tense. Not capitalized. No period at the end.
-  │       │
-  │       └─⫸ Commit Scope: animations|bazel|benchpress|common|compiler|compiler-cli|core|
-  │                          elements|forms|http|language-service|localize|platform-browser|
-  │                          platform-browser-dynamic|platform-server|router|service-worker|
-  │                          upgrade|zone.js|packaging|changelog|docs-infra|migrations|
-  │                          devtools
-  │
-  └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
+docs(changelog): update changelog to beta.5
+```
+```
+fix(release): need to depend on latest rxjs and zone.js
+
+The version in our package.json gets copied to the one we publish, and users need the latest of these.
 ```

-The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` field is optional.
-
-
-##### Type
+### Revert
+If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.

+### Type
 Must be one of the following:

 * **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
-* **ci**: Changes to our CI configuration files and scripts (examples: CircleCi, SauceLabs)
+* **ci**: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
 * **docs**: Documentation only changes
 * **feat**: A new feature
 * **fix**: A bug fix
 * **perf**: A code change that improves performance
 * **refactor**: A code change that neither fixes a bug nor adds a feature
+* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 * **test**: Adding missing tests or correcting existing tests

-
-##### Scope
+### Scope
 The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages).

 The following is the list of supported scopes:

-* `animations`
-* `bazel`
-* `benchpress`
-* `common`
-* `compiler`
-* `compiler-cli`
-* `core`
-* `elements`
-* `forms`
-* `http`
-* `language-service`
-* `localize`
-* `platform-browser`
-* `platform-browser-dynamic`
-* `platform-server`
-* `router`
-* `service-worker`
-* `upgrade`
-* `zone.js`
+* **animations**
+* **bazel**
+* **benchpress**
+* **common**
+* **compiler**
+* **compiler-cli**
+* **core**
+* **elements**
+* **forms**
+* **http**
+* **language-service**
+* **localize**
+* **platform-browser**
+* **platform-browser-dynamic**
+* **platform-server**
+* **platform-webworker**
+* **platform-webworker-dynamic**
+* **router**
+* **service-worker**
+* **upgrade**
+* **zone.js**

 There are currently a few exceptions to the "use package name" rule:

-* `packaging`: used for changes that change the npm package layout in all of our packages, e.g. public path changes, package.json changes done to all packages, d.ts file/format changes, changes to bundles, etc.
+* **packaging**: used for changes that change the npm package layout in all of our packages, e.g.
+  public path changes, package.json changes done to all packages, d.ts file/format changes, changes
+  to bundles, etc.
+* **changelog**: used for updating the release notes in CHANGELOG.md
+* **docs-infra**: used for docs-app (angular.io) related changes within the /aio directory of the
+  repo
+* **dev-infra**: used for dev-infra related changes within the directories /scripts, /tools and /dev-infra
+* **ngcc**: used for changes to the [Angular Compatibility Compiler](./packages/compiler-cli/ngcc/README.md)
+* **ve**: used for changes specific to ViewEngine (legacy compiler/renderer).
+* none/empty string: useful for `style`, `test` and `refactor` changes that are done across all
+  packages (e.g. `style: add missing semicolons`) and for docs changes that are not related to a
+  specific package (e.g. `docs: fix typo in tutorial`).

-* `changelog`: used for updating the release notes in CHANGELOG.md
-
-* `dev-infra`: used for dev-infra related changes within the directories /scripts and /tools
-
-* `docs-infra`: used for docs-app (angular.io) related changes within the /aio directory of the repo
-
-* `migrations`: used for changes to the `ng update` migrations.
-
-* `devtools`: used for changes in the [browser extension](./devtools/README.md).
-
-* none/empty string: useful for `test` and `refactor` changes that are done across all packages (e.g. `test: add missing unit tests`) and for docs changes that are not related to a specific package (e.g. `docs: fix typo in tutorial`).
-
-
-##### Summary
-
-Use the summary field to provide a succinct description of the change:
+### Subject
+The subject contains a succinct description of the change:

 * use the imperative, present tense: "change" not "changed" nor "changes"
 * don't capitalize the first letter
 * no dot (.) at the end

+### Body
+Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
+The body should include the motivation for the change and contrast this with previous behavior.

-#### <a name="commit-body"></a>Commit Message Body
+### Footer
+The footer should contain any information about **Breaking Changes** and is also the place to
+reference GitHub issues that this commit **Closes**.

-Just as in the summary, use the imperative, present tense: "fix" not "fixed" nor "fixes".
-
-Explain the motivation for the change in the commit message body. This commit message should explain _why_ you are making the change.
-You can include a comparison of the previous behavior with the new behavior in order to illustrate the impact of the change.
-
-
-#### <a name="commit-footer"></a>Commit Message Footer
-
-The footer can contain information about breaking changes and deprecations and is also the place to reference GitHub issues, Jira tickets, and other PRs that this commit closes or is related to.
-For example:
-
-```
-BREAKING CHANGE: <breaking change summary>
-<BLANK LINE>
-<breaking change description + migration instructions>
-<BLANK LINE>
-<BLANK LINE>
-Fixes #<issue number>
-```
-
-or
-
-```
-DEPRECATED: <what is deprecated>
-<BLANK LINE>
-<deprecation description + recommended update path>
-<BLANK LINE>
-<BLANK LINE>
-Closes #<pr number>
-```
-
-Breaking Change section should start with the phrase "BREAKING CHANGE: " followed by a summary of the breaking change, a blank line, and a detailed description of the breaking change that also includes migration instructions.
-
-Similarly, a Deprecation section should start with "DEPRECATED: " followed by a short description of what is deprecated, a blank line, and a detailed description of the deprecation that also mentions the recommended update path.
-
-
-### Revert commits
-
-If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
-
-The content of the commit message body should contain:
-
- information about the SHA of the commit being reverted in the following format: `This reverts commit <SHA>`,
- a clear description of the reason for reverting the commit message.
+**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.

+A detailed explanation can be found in this [document][commit-message-format].

 ## <a name="cla"></a> Signing the CLA

@@ -377,28 +270,29 @@ changes to be accepted, the CLA must be signed. It's a quick process, we promise
 * For corporations, we'll need you to
  [print, sign and one of scan+email, fax or mail the form][corporate-cla].

-If you have more than one GitHub accounts, or multiple email addresses associated with a single GitHub account, you must sign the CLA using the primary email address of the GitHub account used to author Git commits and send pull requests.
+<hr>

-The following documents can help you sort out issues with GitHub accounts and multiple email addresses:
+  If you have more than one Git identity, you must make sure that you sign the CLA using the primary email address associated with the ID that has been granted access to the Angular repository. Git identities can be associated with more than one email address, and only one is primary. Here are some links to help you sort out multiple Git identities and email addresses:

  * https://help.github.com/articles/setting-your-commit-email-address-in-git/
  * https://stackoverflow.com/questions/37245303/what-does-usera-committed-with-userb-13-days-ago-on-github-mean
  * https://help.github.com/articles/about-commit-email-addresses/
  * https://help.github.com/articles/blocking-command-line-pushes-that-expose-your-personal-email-address/

+  Note that if you have more than one Git identity, it is important to verify that you are logged in with the same ID with which you signed the CLA, before you commit changes. If not, your PR will fail the CLA check.

-
+<hr>

 [angular-group]: https://groups.google.com/forum/#!forum/angular
-[coc]: https://github.com/angular/code-of-conduct/blob/main/CODE_OF_CONDUCT.md
+[coc]: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
 [commit-message-format]: https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#
-[corporate-cla]: https://cla.developers.google.com/about/google-corporate
-[dev-doc]: https://github.com/angular/angular/blob/main/docs/DEVELOPER.md
+[corporate-cla]: http://code.google.com/legal/corporate-cla-v1.0.html
+[dev-doc]: https://github.com/angular/angular/blob/master/docs/DEVELOPER.md
 [github]: https://github.com/angular/angular
-[discord]: https://discord.gg/angular
-[individual-cla]: https://cla.developers.google.com/about/google-individual
+[gitter]: https://gitter.im/angular/angular
+[individual-cla]: http://code.google.com/legal/individual-cla-v1.0.html
 [js-style-guide]: https://google.github.io/styleguide/jsguide.html
-[jsfiddle]: https://jsfiddle.net/
-[plunker]: https://plnkr.co/edit
-[runnable]: https://runnable.com/
-[stackoverflow]: https://stackoverflow.com/questions/tagged/angular
+[jsfiddle]: http://jsfiddle.net
+[plunker]: http://plnkr.co/edit
+[runnable]: http://runnable.com
+[stackoverflow]: http://stackoverflow.com/questions/tagged/angular
@@ -1,6 +1,6 @@
 The MIT License

-Copyright (c) 2010-2024 Google LLC. https://angular.io/license
+Copyright (c) 2010-2020 Google LLC. http://angular.io/license

 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -1,186 +1,26 @@
-<h1 align="center">Angular - The modern web developer's platform</h1>
+[![CircleCI](https://circleci.com/gh/angular/angular/tree/master.svg?style=shield)](https://circleci.com/gh/angular/workflows/angular/tree/master)
+[![Join the chat at https://gitter.im/angular/angular](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/angular/angular?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+[![npm version](https://badge.fury.io/js/%40angular%2Fcore.svg)](https://www.npmjs.com/@angular/core)

-<p align="center">
-  <img src="aio/src/assets/images/logos/angular/angular_renaissance.png" alt="angular-logo" width="120px" height="120px"/>
-  <br>
-  <em>Angular is a development platform for building mobile and desktop web applications
-    <br> using TypeScript/JavaScript and other languages.</em>
-  <br>
-</p>

-<p align="center">
-  <a href="https://angular.dev/"><strong>angular.dev</strong></a>
-  <br>
-</p>
+# Angular

-<p align="center">
-  <a href="CONTRIBUTING.md">Contributing Guidelines</a>
-  ·
-  <a href="https://github.com/angular/angular/issues">Submit an Issue</a>
-  ·
-  <a href="https://blog.angular.io/">Blog</a>
-  <br>
-  <br>
-</p>
-
-<p align="center">
-  <a href="https://circleci.com/gh/angular/workflows/angular/tree/main">
-    <img src="https://img.shields.io/circleci/build/github/angular/angular/main.svg?logo=circleci&logoColor=fff&label=CircleCI" alt="CI status" />
-  </a>&nbsp;
-  <a href="https://www.npmjs.com/@angular/core">
-    <img src="https://img.shields.io/npm/v/@angular/core.svg?logo=npm&logoColor=fff&label=NPM+package&color=limegreen" alt="Angular on npm" />
-  </a>&nbsp;
-  <a href="https://discord.gg/angular">
-    <img src="https://img.shields.io/discord/463752820026376202.svg?logo=discord&logoColor=fff&label=Discord&color=7389d8" alt="Discord conversation" />
-  </a>
-</p>
-
-<p align="center">
-  <a href="https://app.circleci.com/insights/github/angular/angular/workflows/default_workflow?branch=main">
-    <img src="https://dl.circleci.com/insights-snapshot/gh/angular/angular/main/default_workflow/badge.svg" alt="InsightsSnapshot" />
-  </a>
-</p>
-
-<hr>
-
-## Documentation
-
-Get started with Angular, learn the fundamentals and explore advanced topics on our documentation website.
-
- [Getting Started][quickstart]
- [Architecture][architecture]
- [Components and Templates][componentstemplates]
- [Forms][forms]
- [API][api]
-
-### Advanced
-
- [Angular Elements][angularelements]
- [Server Side Rendering][ssr]
- [Schematics][schematics]
- [Lazy Loading][lazyloading]
- [Animations][animations]
-
-### Local Development
-
-To contribute to Angular docs, you can setup a local environment with the following commands:
-
-```bash
-# Clone Angular repo
-git clone https://github.com/angular/angular.git
-
-# Navigate to project directory
-cd angular
-
-# Install dependencies
-yarn
-
-# Build and run local dev server
-# Note: Initial build will take some time
-yarn docs
-```
-
-## Development Setup
-
-### Prerequisites
-
- Install [Node.js] which includes [Node Package Manager][npm]
-
-### Setting Up a Project
-
-Install the Angular CLI globally:
-
-```
-npm install -g @angular/cli
-```
-
-Create workspace:
-
-```
-ng new [PROJECT NAME]
-```
-
-Run the application:
-
-```
-cd [PROJECT NAME]
-ng serve
-```
-
-Angular is cross-platform, fast, scalable, has incredible tooling, and is loved by millions.
+Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages.

 ## Quickstart

 [Get started in 5 minutes][quickstart].

-## Ecosystem
-
-<p>
-  <img src="/docs/images/angular-ecosystem-logos.png" alt="angular ecosystem logos" width="500px" height="auto">
-</p>
-
- [Angular Command Line (CLI)][cli]
- [Angular Material][angularmaterial]
-
 ## Changelog

 [Learn about the latest improvements][changelog].

-## Upgrading
+## Want to help?

-Check out our [upgrade guide](https://update.angular.io/) to find out the best way to upgrade your project.
+Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our
+guidelines for [contributing][contributing] and then check out one of our issues in the [hotlist: community-help](https://github.com/angular/angular/labels/hotlist%3A%20community-help).

-## Contributing
-
-### Contributing Guidelines
-
-Read through our [contributing guidelines][contributing] to learn about our submission process, coding rules, and more.
-
-### Want to Help?
-
-Want to report a bug, contribute some code, or improve the documentation? Excellent! Read up on our guidelines for [contributing][contributing] and then check out one of our issues labeled as <kbd>[help wanted](https://github.com/angular/angular/labels/help%20wanted)</kbd> or <kbd>[good first issue](https://github.com/angular/angular/labels/good%20first%20issue)</kbd>.
-
-### Code of Conduct
-
-Help us keep Angular open and inclusive. Please read and follow our [Code of Conduct][codeofconduct].
-
-## Community
-
-Join the conversation and help the community.
-
- [X (formerly Twitter)][X (formerly Twitter)]
- [Discord][discord]
- [Gitter][gitter]
- [YouTube][youtube]
- [StackOverflow][stackoverflow]
- Find a Local [Meetup][meetup]
-
-[![Love Angular badge](https://img.shields.io/badge/angular-love-blue?logo=angular&angular=love)](https://www.github.com/angular/angular)
-
-**Love Angular? Give our repo a star :star: :arrow_up:.**
-
-[contributing]: CONTRIBUTING.md
-[quickstart]: https://angular.dev/tutorials/learn-angular
-[changelog]: CHANGELOG.md
-[ng]: https://angular.dev
-[documentation]: https://angular.dev/overview
-[angularmaterial]: https://material.angular.io/
-[cli]: https://angular.dev/tools/cli
-[architecture]: https://angular.dev/essentials
-[componentstemplates]: https://angular.dev/tutorials/learn-angular/components-in-angular
-[forms]: https://angular.dev/tutorials/learn-angular/forms
-[api]: https://angular.dev/api
-[angularelements]: https://angular.dev/guide/elements
-[ssr]: https://angular.dev/guide/ssr
-[schematics]: https://angular.dev/tools/cli/schematics
-[lazyloading]: https://angular.dev/guide/ngmodules/lazy-loading
-[node.js]: https://nodejs.org/
-[npm]: https://www.npmjs.com/get-npm
-[codeofconduct]: CODE_OF_CONDUCT.md
-[X (formerly Twitter)]: https://www.twitter.com/angular
-[discord]: https://discord.gg/angular
-[gitter]: https://gitter.im/angular/angular
-[stackoverflow]: https://stackoverflow.com/questions/tagged/angular
-[youtube]: https://youtube.com/angular
-[meetup]: https://www.meetup.com/find/?keywords=angular
-[animations]: https://angular.dev/guide/animations
+[contributing]: https://github.com/angular/angular/blob/master/CONTRIBUTING.md
+[quickstart]: https://angular.io/start
+[changelog]: https://github.com/angular/angular/blob/master/CHANGELOG.md
+[ng]: https://angular.io
@@ -1,3 +0,0 @@
-Angular is part of Google [Open Source Software Vulnerability Reward Program](https://bughunters.google.com/about/rules/6521337925468160/google-open-source-software-vulnerability-reward-program-rules). For vulnerabilities in Angular, please submit your report [here](https://bughunters.google.com/report).
-
-For more information, check out [Angular's security policy](https://angular.io/guide/security).
@@ -1,246 +1,107 @@
 workspace(
    name = "angular",
-    managed_directories = {
-        "@npm": ["node_modules"],
-        "@aio_npm": ["aio/node_modules"],
-    },
+    managed_directories = {"@npm": ["node_modules"]},
 )

 load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
-load("//:yarn.bzl", "YARN_LABEL")
-
-# Add a patch fix for rules_webtesting v0.3.5 required for enabling runfiles on Windows.
-# TODO: Remove the http_archive for this transitive dependency when a release is cut
-# for https://github.com/bazelbuild/rules_webtesting/commit/581b1557e382f93419da6a03b91a45c2ac9a9ec8
-# and the version is updated in rules_nodejs.
-http_archive(
-    name = "io_bazel_rules_webtesting",
-    patch_args = ["-p1"],
-    patches = [
-        "//:tools/bazel-repo-patches/rules_webtesting__windows_runfiles_fix.patch",
-    ],
-    sha256 = "e9abb7658b6a129740c0b3ef6f5a2370864e102a5ba5ffca2cea565829ed825a",
-    urls = ["https://github.com/bazelbuild/rules_webtesting/releases/download/0.3.5/rules_webtesting.tar.gz"],
-)

+# Fetch rules_nodejs so we can install our npm dependencies
 http_archive(
    name = "build_bazel_rules_nodejs",
-    patches = [
-        "//tools/esm-interop:patches/bazel/nodejs_binary_esm_support.patch",
-    ],
-    sha256 = "5dd1e5dea1322174c57d3ca7b899da381d516220793d0adef3ba03b9d23baa8e",
-    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/5.8.3/rules_nodejs-5.8.3.tar.gz"],
+    sha256 = "2eca5b934dee47b5ff304f502ae187c40ec4e33e12bcbce872a2eeb786e23269",
+    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/1.4.1/rules_nodejs-1.4.1.tar.gz"],
 )

-load("@build_bazel_rules_nodejs//:repositories.bzl", "build_bazel_rules_nodejs_dependencies")
+# Check the rules_nodejs version and download npm dependencies
+# Note: bazel (version 2 and after) will check the .bazelversion file so we don't need to
+# assert on that.
+load("@build_bazel_rules_nodejs//:index.bzl", "check_rules_nodejs_version", "node_repositories", "yarn_install")

-build_bazel_rules_nodejs_dependencies()
+check_rules_nodejs_version(minimum_version_string = "1.4.1")

-# The PKG rules are needed to build tar packages for integration tests. The builtin
-# rule in `@bazel_tools` is not Windows compatible and outdated.
-# NOTE: We cannot move past version 0.6.0 as pkg_tar no longer works on directories, which rules_nodejs
-#       relies on for node_modules setup.
-http_archive(
-    name = "rules_pkg",
-    sha256 = "62eeb544ff1ef41d786e329e1536c1d541bb9bcad27ae984d57f18f314018e66",
-    urls = [
-        "https://mirror.bazel.build/github.com/bazelbuild/rules_pkg/releases/download/0.6.0/rules_pkg-0.6.0.tar.gz",
-        "https://github.com/bazelbuild/rules_pkg/releases/download/0.6.0/rules_pkg-0.6.0.tar.gz",
-    ],
-)
-
-# Fetch Aspect lib for utilities like write_source_files
-# NOTE: We cannot move past version 1.23.2 of aspect_bazel_lib because it requires us to move to bazel 6.0.0 which
-#       breaks our usage of managed_directories
-http_archive(
-    name = "aspect_bazel_lib",
-    sha256 = "4b2e774387bae6242879820086b7b738d49bf3d0659522ea5d9363be01a27582",
-    strip_prefix = "bazel-lib-1.23.2",
-    url = "https://github.com/aspect-build/bazel-lib/archive/refs/tags/v1.23.2.tar.gz",
-)
-
-# Setup the Node.js toolchain.
-load("@rules_nodejs//nodejs:repositories.bzl", "nodejs_register_toolchains")
-
-nodejs_register_toolchains(
-    name = "nodejs",
+# Setup the Node.js toolchain
+node_repositories(
    node_repositories = {
-        "18.18.2-darwin_arm64": ("node-v18.18.2-darwin-arm64.tar.gz", "node-v18.18.2-darwin-arm64", "9f982cc91b28778dd8638e4f94563b0c2a1da7aba62beb72bd427721035ab553"),
-        "18.18.2-darwin_amd64": ("node-v18.18.2-darwin-x64.tar.gz", "node-v18.18.2-darwin-x64", "5bb8da908ed590e256a69bf2862238c8a67bc4600119f2f7721ca18a7c810c0f"),
-        "18.18.2-linux_arm64": ("node-v18.18.2-linux-arm64.tar.xz", "node-v18.18.2-linux-arm64", "2e630e18548627f61eaf573233da7949dc0a1df5eef3f486fa9820c5f6c121aa"),
-        "18.18.2-linux_ppc64le": ("node-v18.18.2-linux-ppc64le.tar.xz", "node-v18.18.2-linux-ppc64le", "b0adff5cf5938266b711d6c724fb134d802e0dee40b3a3f73d162de1b3d11880"),
-        "18.18.2-linux_s390x": ("node-v18.18.2-linux-s390x.tar.xz", "node-v18.18.2-linux-s390x", "c70ec2074b5e2b42c55bb4b8105418b67bf8a61c500d9376a07430dfcc341fdb"),
-        "18.18.2-linux_amd64": ("node-v18.18.2-linux-x64.tar.xz", "node-v18.18.2-linux-x64", "75aba25ae76999309fc6c598efe56ce53fbfc221381a44a840864276264ab8ac"),
-        "18.18.2-windows_amd64": ("node-v18.18.2-win-x64.zip", "node-v18.18.2-win-x64", "3bb0e51e579a41a22b3bf6cb2f3e79c03801aa17acbe0ca00fc555d1282e7acd"),
+        "12.14.1-darwin_amd64": ("node-v12.14.1-darwin-x64.tar.gz", "node-v12.14.1-darwin-x64", "0be10a28737527a1e5e3784d3ad844d742fe8b0718acd701fd48f718fd3af78f"),
+        "12.14.1-linux_amd64": ("node-v12.14.1-linux-x64.tar.xz", "node-v12.14.1-linux-x64", "07cfcaa0aa9d0fcb6e99725408d9e0b07be03b844701588e3ab5dbc395b98e1b"),
+        "12.14.1-windows_amd64": ("node-v12.14.1-win-x64.zip", "node-v12.14.1-win-x64", "1f96ccce3ba045ecea3f458e189500adb90b8bc1a34de5d82fc10a5bf66ce7e3"),
    },
-    # We need at least Node 18.17 due to some transitive dependencies.
-    node_version = "18.18.2",
+    node_version = "12.14.1",
+    package_json = ["//:package.json"],
 )

-# Download npm dependencies.
-load("@build_bazel_rules_nodejs//:index.bzl", "yarn_install")
-load("//integration:npm_package_archives.bzl", "npm_package_archives")
+load("//integration:angular_integration_test.bzl", "npm_package_archives")

 yarn_install(
    name = "npm",
-    # Note that we add the postinstall scripts here so that the dependencies are re-installed
-    # when the postinstall patches are modified.
-    data = [
-        YARN_LABEL,
-        "//:.yarnrc",
-        "//:tools/npm-patches/@bazel+jasmine+5.8.1.patch",
-        "//tools:postinstall-patches.js",
-        "//tools/esm-interop:patches/npm/@angular+build-tooling+0.0.0-e0ec7b60641d7f6369be45d8d02663fd50f320be.patch",
-        "//tools/esm-interop:patches/npm/@bazel+concatjs+5.8.1.patch",
-        "//tools/esm-interop:patches/npm/@bazel+esbuild+5.7.1.patch",
-        "//tools/esm-interop:patches/npm/@bazel+protractor+5.7.1.patch",
-        "//tools/esm-interop:patches/npm/rxjs+6.6.7.patch",
-    ],
-    # Currently disabled due to:
-    #  1. Missing Windows support currently.
-    #  2. Incompatibilites with the `ts_library` rule.
-    exports_directories_only = False,
    manual_build_file_contents = npm_package_archives(),
    package_json = "//:package.json",
-    # We prefer to symlink the `node_modules` to only maintain a single install.
-    # See https://github.com/angular/dev-infra/pull/446#issuecomment-1059820287 for details.
-    symlink_node_modules = True,
-    yarn = YARN_LABEL,
    yarn_lock = "//:yarn.lock",
 )

-yarn_install(
-    name = "aio_npm",
-    # Note that we add the postinstall scripts here so that the dependencies are re-installed
-    # when the postinstall patches are modified.
-    data = [
-        YARN_LABEL,
-        "//:.yarnrc",
-        "//:tools/npm-patches/@bazel+jasmine+5.8.1.patch",
-        "//aio:tools/cli-patches/bazel-architect-output.patch",
-        "//aio:tools/cli-patches/patch.js",
-    ],
-    # Currently disabled due to:
-    #  1. Missing Windows support currently.
-    #  2. Incompatibilites with the `ts_library` rule.
-    exports_directories_only = False,
-    manual_build_file_contents = npm_package_archives(),
-    package_json = "//aio:package.json",
-    # We prefer to symlink the `node_modules` to only maintain a single install.
-    # See https://github.com/angular/dev-infra/pull/446#issuecomment-1059820287 for details.
-    symlink_node_modules = True,
-    yarn = YARN_LABEL,
-    yarn_lock = "//aio:yarn.lock",
-)
+# Install all bazel dependencies of the @npm npm packages
+load("@npm//:install_bazel_dependencies.bzl", "install_bazel_dependencies")

-yarn_install(
-    name = "aio_example_deps",
-    # Rename the default js_library target from "node_modules" as this obscures the
-    # the source directory stamped as a filegroup in the manual BUILD contents below.
-    all_node_modules_target_name = "node_modules_all",
-    data = [
-        YARN_LABEL,
-        "//:.yarnrc",
-    ],
-    # Disabled because, when False, yarn_install preserves the node_modules folder
-    # with bin symlinks in the external repository. This is needed to link the shared
-    # set of deps for example e2es.
-    exports_directories_only = False,
-    manual_build_file_contents = """\
-filegroup(
-    name = "node_modules_files",
-    srcs = ["node_modules"],
-)
-""",
-    package_json = "//aio/tools/examples/shared:package.json",
-    yarn = YARN_LABEL,
-    yarn_lock = "//aio/tools/examples/shared:yarn.lock",
-)
+install_bazel_dependencies()

-load("@aspect_bazel_lib//lib:repositories.bzl", "aspect_bazel_lib_dependencies")
+# Load angular dependencies
+load("//packages/bazel:package.bzl", "rules_angular_dev_dependencies")

-aspect_bazel_lib_dependencies()
+rules_angular_dev_dependencies()

 # Load protractor dependencies
-load("@npm//@bazel/protractor:package.bzl", "npm_bazel_protractor_dependencies")
+load("@npm_bazel_protractor//:package.bzl", "npm_bazel_protractor_dependencies")

 npm_bazel_protractor_dependencies()

+# Load karma dependencies
+load("@npm_bazel_karma//:package.bzl", "npm_bazel_karma_dependencies")
+
+npm_bazel_karma_dependencies()
+
 # Setup the rules_webtesting toolchain
 load("@io_bazel_rules_webtesting//web:repositories.bzl", "web_test_repositories")

 web_test_repositories()

-load("@npm//@angular/build-tooling/bazel/browsers:browser_repositories.bzl", "browser_repositories")
+load("//tools/browsers:browser_repositories.bzl", "browser_repositories")

 browser_repositories()

-load("@build_bazel_rules_nodejs//toolchains/esbuild:esbuild_repositories.bzl", "esbuild_repositories")
+# Setup the rules_typescript tooolchain
+load("@npm_bazel_typescript//:index.bzl", "ts_setup_workspace")

-esbuild_repositories(
-    npm_repository = "npm",
-)
-
-load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
-
-rules_pkg_dependencies()
-
-load("//packages/common/locales/generate-locales-tool:cldr-data.bzl", "cldr_json_data_repository", "cldr_xml_data_repository")
-
-cldr_major_version = "41"
-
-cldr_json_data_repository(
-    name = "cldr_json_data",
-    urls = {
-        "https://github.com/unicode-org/cldr-json/releases/download/%s.0.0/cldr-%s.0.0-json-full.zip" % (cldr_major_version, cldr_major_version): "649b76647269e32b1b0a5f7b6eed52e9e63a1581f1afdcf4f6771e49c9713614",
-    },
-)
-
-cldr_xml_data_repository(
-    name = "cldr_xml_data",
-    urls = {
-        "https://github.com/unicode-org/cldr/releases/download/release-%s/cldr-common-%s.0.zip" % (cldr_major_version, cldr_major_version): "823c6170c41e2de2c229574e8a436332d25f1c9723409867fe721e00bc92d853",
-    },
-)
-
-# sass rules
-http_archive(
-    name = "io_bazel_rules_sass",
-    sha256 = "5633816e996a79c77f44306f6228b9ef18fc2ecb412d63b4e314a132225facba",
-    strip_prefix = "rules_sass-79bd239ce77c101ea1aed575678020bd2999f17d",
-    urls = [
-        "https://github.com/bazelbuild/rules_sass/archive/79bd239ce77c101ea1aed575678020bd2999f17d.zip",
-    ],
-)
+ts_setup_workspace()

 # Setup the rules_sass toolchain
 load("@io_bazel_rules_sass//sass:sass_repositories.bzl", "sass_repositories")

-sass_repositories(
-    yarn_script = YARN_LABEL,
-)
+sass_repositories()

-# Register git toolchains
-register_toolchains(
-    "@npm//@angular/build-tooling/bazel/git-toolchain:git_linux_toolchain",
-    "@npm//@angular/build-tooling/bazel/git-toolchain:git_macos_x86_toolchain",
-    "@npm//@angular/build-tooling/bazel/git-toolchain:git_macos_arm64_toolchain",
-    "@npm//@angular/build-tooling/bazel/git-toolchain:git_windows_toolchain",
-)
+# Setup the skydoc toolchain
+load("@io_bazel_skydoc//skylark:skylark.bzl", "skydoc_repositories")

-# Fetch sauce connect (tool to open Saucelabs tunnel for Saucelabs browser tests)
-http_archive(
-    name = "sauce_connect_linux_amd64",
-    build_file_content = """exports_files(["bin/sc"], visibility = ["//visibility:public"])""",
-    sha256 = "26b9c3630f441b47854b6032f7eca6f1d88d3f62e50ee44c27015d71a5155c36",
-    strip_prefix = "sc-4.8.2-linux",
-    url = "https://saucelabs.com/downloads/sc-4.8.2-linux.tar.gz",
-)
+skydoc_repositories()

-http_archive(
-    name = "sauce_connect_mac",
-    build_file_content = """exports_files(["bin/sc"], visibility = ["//visibility:public"])""",
-    sha256 = "28277ce81ef9ab84f5b87b526258920a8ead44789a5034346e872629bbf38089",
-    strip_prefix = "sc-4.8.2-osx",
-    url = "https://saucelabs.com/downloads/sc-4.8.2-osx.zip",
+load("@bazel_toolchains//rules:environments.bzl", "clang_env")
+load("@bazel_toolchains//rules:rbe_repo.bzl", "rbe_autoconfig")
+
+rbe_autoconfig(
+    name = "rbe_ubuntu1604_angular",
+    # Need to specify a base container digest in order to ensure that we can use the checked-in
+    # platform configurations for the "ubuntu16_04" image. Otherwise the autoconfig rule would
+    # need to pull the image and run it in order determine the toolchain configuration. See:
+    # https://github.com/bazelbuild/bazel-toolchains/blob/1.1.2/configs/ubuntu16_04_clang/versions.bzl
+    base_container_digest = "sha256:1ab40405810effefa0b2f45824d6d608634ccddbf06366760c341ef6fbead011",
+    # Note that if you change the `digest`, you might also need to update the
+    # `base_container_digest` to make sure marketplace.gcr.io/google/rbe-ubuntu16-04-webtest:<digest>
+    # and marketplace.gcr.io/google/rbe-ubuntu16-04:<base_container_digest> have
+    # the same Clang and JDK installed. Clang is needed because of the dependency on
+    # @com_google_protobuf. Java is needed for the Bazel's test executor Java tool.
+    digest = "sha256:0b8fa87db4b8e5366717a7164342a029d1348d2feea7ecc4b18c780bc2507059",
+    env = clang_env(),
+    registry = "marketplace.gcr.io",
+    # We can't use the default "ubuntu16_04" RBE image provided by the autoconfig because we need
+    # a specific Linux kernel that comes with "libx11" in order to run headless browser tests.
+    repository = "google/rbe-ubuntu16-04-webtest",
 )
@@ -1,174 +0,0 @@
-load("//:packages.bzl", "link_packages")
-load("@npm//@angular/build-tooling/bazel/remote-execution:index.bzl", "ENABLE_NETWORK")
-load("@bazel_skylib//rules:common_settings.bzl", "bool_flag")
-load("@build_bazel_rules_nodejs//:index.bzl", "copy_to_bin")
-load("@npm//@angular-devkit/architect-cli:index.bzl", "architect", "architect_test")
-
-package(default_visibility = ["//visibility:public"])
-
-# All source and configuration files required to build the docs app
-APPLICATION_FILES = [
-    "angular.json",
-    "tsconfig.app.json",
-    "tsconfig.json",
-    "tsconfig.worker.json",
-] + glob(
-    ["src/**/*"],
-    exclude = [
-        "src/**/*.spec.ts",
-        # Temporarily exclude generated sources produced by the non-bazel
-        # build until the whole project is built by bazel and this directory
-        # isn't needed.
-        "src/generated/**/*",
-    ],
-)
-
-TEST_FILES = APPLICATION_FILES + [
-    "karma.conf.js",
-    "tsconfig.spec.json",
-] + glob(
-    ["**/*.spec.ts"],
-)
-
-APPLICATION_DEPS = link_packages([
-    "@npm//@angular-devkit/build-angular",
-    "@npm//@angular/animations",
-    "@npm//@angular/cdk",
-    "@npm//@angular/common",
-    "@npm//@angular/compiler",
-    "@npm//@angular/compiler-cli",
-    "@npm//@angular/core",
-    "@npm//@angular/docs",
-    "@npm//@angular/forms",
-    "@npm//@angular/material",
-    "@npm//@angular/platform-browser",
-    "@npm//@angular/platform-server",
-    "@npm//@angular/router",
-    "@npm//gsap",
-    "@npm//marked",
-    "@npm//ngx-progressbar",
-    "@npm//ogl",
-    "@npm//rxjs",
-    "@npm//typescript",
-    "//adev/src/assets/images",
-    "//adev/src/assets/textures",
-    "//adev/src/assets/previews",
-    "//adev/src/assets:tutorials",
-    "//adev/src/assets/icons",
-    "//adev/src/assets:api",
-    "//adev/src/assets:content",
-    "@npm//@typescript/vfs",
-    "@npm//@codemirror/state",
-    "@npm//@codemirror/view",
-    "@npm//@codemirror/language",
-    "@npm//@codemirror/commands",
-    "@npm//@codemirror/search",
-    "@npm//@codemirror/autocomplete",
-    "@npm//@codemirror/lint",
-    "@npm//@codemirror/lang-html",
-    "@npm//@codemirror/lang-angular",
-    "@npm//@codemirror/lang-css",
-    "@npm//@codemirror/lang-sass",
-    "@npm//@codemirror/lang-javascript",
-    "@npm//@lezer/highlight",
-    "@npm//@lezer/javascript",
-    "@npm//@lezer/common",
-    "@npm//@xterm/xterm",
-    "@npm//xterm-addon-fit",
-    "@npm//angular-split",
-])
-
-TEST_DEPS = APPLICATION_DEPS + link_packages([
-    "@npm//@angular/platform-browser-dynamic",
-    "@npm//@angular/build-tooling/bazel/browsers/chromium",
-    "@npm//@types/jasmine",
-    "@npm//@types/node",
-    "@npm//assert",
-    "@npm//jasmine",
-    "@npm//jasmine-core",
-    "@npm//karma-chrome-launcher",
-    "@npm//karma-coverage",
-    "@npm//karma-jasmine",
-    "@npm//karma-jasmine-html-reporter",
-    "//aio/tools:windows-chromium-path",
-])
-
-copy_to_bin(
-    name = "application_files_bin",
-    srcs = APPLICATION_FILES,
-)
-
-bool_flag(
-    name = "fast_build_mode",
-    build_setting_default = False,
-)
-
-config_setting(
-    name = "fast",
-    flag_values = {
-        ":fast_build_mode": "true",
-    },
-)
-
-config_setting(
-    name = "full",
-    flag_values = {
-        ":fast_build_mode": "false",
-    },
-)
-
-config_based_architect_flags = select({
-    ":fast": ["--no-prerender"],
-    ":full": ["--prerender"],
-})
-
-architect(
-    name = "build",
-    args = [
-        "angular-dev:build",
-        "--output-path=build",
-    ] + config_based_architect_flags,
-    chdir = "$(RULEDIR)",
-    data = APPLICATION_DEPS + [
-        ":application_files_bin",
-    ],
-    # Network is required to inline fonts.
-    exec_properties = ENABLE_NETWORK,
-    output_dir = True,
-    tags = [
-        "no-remote-exec",
-    ],
-)
-
-architect(
-    name = "serve",
-    args = [
-        "angular-dev:serve",
-        "--poll=1000",
-        "--live-reload",
-        "--watch",
-    ],
-    chdir = package_name(),
-    data = APPLICATION_DEPS + [
-        ":application_files_bin",
-    ],
-    tags = [
-        "no-remote-exec",
-    ],
-)
-
-architect_test(
-    name = "test",
-    args = [
-        "angular-dev:test",
-        "--no-watch",
-    ],
-    chdir = package_name(),
-    data = TEST_DEPS + TEST_FILES,
-    env = {
-        "CHROME_BIN": "../$(CHROMIUM)",
-    },
-    toolchains = [
-        "@npm//@angular/build-tooling/bazel/browsers/chromium:toolchain_alias",
-    ],
-)
@@ -1,104 +0,0 @@
-{
-  "$schema": "../node_modules/@angular/cli/lib/config/schema.json",
-  "version": 1,
-  "newProjectRoot": ".",
-  "projects": {
-    "angular-dev": {
-      "projectType": "application",
-      "schematics": {
-        "@schematics/angular:component": {
-          "style": "scss",
-          "standalone": true,
-          "changeDetection": "OnPush"
-        }
-      },
-      "root": ".",
-      "sourceRoot": "src",
-      "prefix": "adev",
-      "architect": {
-        "build": {
-          "builder": "@angular-devkit/build-angular:application",
-          "options": {
-            "externalDependencies": [
-              "path"
-            ],
-            "outputPath": "dist/angular-dev",
-            "index": "src/index.html",
-            "browser": "src/main.ts",
-            "server": "src/main.server.ts",
-            "polyfills": ["src/polyfills.ts", "zone.js"],
-            "tsConfig": "tsconfig.app.json",
-            "inlineStyleLanguage": "scss",
-            "assets": [
-              "src/favicon.ico",
-              "src/robots.txt",
-              "src/assets"
-            ],
-            "styles": ["@angular/docs/styles/global-styles.scss"],
-            "scripts": [],
-            "webWorkerTsConfig": "tsconfig.worker.json",
-            "optimization": {
-              "fonts": {
-                // TODO(josephperrott): enabled inline scripts
-                "inline": false
-              }
-            }
-          },
-          "configurations": {
-            "production": {
-              "outputHashing": "all"
-            },
-            "development": {
-              "optimization": false,
-              "extractLicenses": false,
-              "sourceMap": true
-            }
-          },
-          "defaultConfiguration": "production"
-        },
-        "serve": {
-          "builder": "@angular-devkit/build-angular:dev-server",
-          "configurations": {
-            "production": {
-              "buildTarget": "angular-dev:build:production"
-            },
-            "development": {
-              "buildTarget": "angular-dev:build:development"
-            }
-          },
-          "defaultConfiguration": "development",
-          "options": {
-            "buildTarget": "web-ui:build",
-            "headers": {
-              "Cross-Origin-Opener-Policy": "same-origin",
-              "Cross-Origin-Embedder-Policy": "require-corp"
-            }
-          }
-        },
-        "extract-i18n": {
-          "builder": "@angular-devkit/build-angular:extract-i18n",
-          "options": {
-            "buildTarget": "angular-dev:build"
-          }
-        },
-        "test": {
-          "builder": "@angular-devkit/build-angular:karma",
-          "options": {
-            "polyfills": ["zone.js", "zone.js/testing"],
-            "tsConfig": "tsconfig.spec.json",
-            "include": ["src/app"],
-            "karmaConfig": "karma.conf.js",
-            "inlineStyleLanguage": "scss",
-            "assets": ["src/favicon.ico", "src/assets"],
-            "styles": ["@angular/docs/styles/global-styles.scss"],
-            "scripts": [],
-            "webWorkerTsConfig": "tsconfig.worker.json"
-          }
-        }
-      }
-    }
-  },
-  "cli": {
-    "analytics": "dca119a9-da31-47f7-a6cb-b60541037021"
-  }
-}
@@ -1,73 +0,0 @@
-{
-  "hosting": {
-    "target": "angular-docs",
-    "public": "./build/browser",
-    "ignore": ["**/.*"],
-    "headers": [
-      {
-        "source": "assets/tutorials/common/*.jpg",
-        "headers": [
-          {
-            "key": "Cross-Origin-Resource-Policy",
-            "value": "cross-origin"
-          },
-          {
-            "key": "Access-Control-Allow-Origin",
-            "value": "*"
-          }
-        ]
-      },
-      {
-        "source": "*.[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f].+(css|js)",
-        "headers": [
-          {
-            "key": "Cache-Control",
-            "value": "public,max-age=31536000,immutable"
-          },
-          {
-            "key": "Access-Control-Allow-Origin",
-            "value": "*"
-          }
-        ]
-      },
-      {
-        "source": "/[0-9a-f][0-9a-f][0-9a-f].[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f].js",
-        "headers": [
-          {
-            "key": "Cross-Origin-Embedder-Policy",
-            "value": "require-corp"
-          }
-        ]
-      },
-      {
-        "source": "/@(ngsw-worker.js|ngsw.json)",
-        "headers": [
-          {
-            "key": "Cache-Control",
-            "value": "no-cache"
-          }
-        ]
-      },
-      {
-        "source": "/**",
-        "headers": [
-          {
-            "key": "Cross-Origin-Opener-Policy",
-            "value": "same-origin"
-          },
-
-          {
-            "key": "Cross-Origin-Embedder-Policy",
-            "value": "require-corp"
-          }
-        ]
-      }
-    ],
-    "rewrites": [
-      {
-        "source": "**",
-        "destination": "/index.html"
-      }
-    ]
-  }
-}
@@ -1,78 +0,0 @@
-// Karma configuration file, see link for more information
-// https://karma-runner.github.io/1.0/config/configuration-file.html
-
-const {getAdjustedChromeBinPathForWindows} = require('../aio/tools/windows-chromium-path');
-
-process.env.CHROME_BIN = getAdjustedChromeBinPathForWindows();
-
-module.exports = function (config) {
-  config.set({
-    basePath: '',
-    frameworks: ['jasmine', '@angular-devkit/build-angular'],
-    plugins: [
-      require('karma-jasmine'),
-      require('karma-chrome-launcher'),
-      require('karma-jasmine-html-reporter'),
-      require('karma-coverage'),
-      require('@angular-devkit/build-angular/plugins/karma'),
-      {'reporter:jasmine-seed': ['type', JasmineSeedReporter]},
-    ],
-    proxies: {
-      '/dummy/image': 'src/assets/images/logos/angular/angular.png',
-    },
-    client: {
-      clearContext: false, // leave Jasmine Spec Runner output visible in browser
-      jasmine: {
-        // you can add configuration options for Jasmine here
-        // the possible options are listed at https://jasmine.github.io/api/edge/Configuration.html
-        // for example, you can disable the random execution with `random: false`
-        // or set a specific seed with `seed: 4321`
-        random: true,
-        seed: '',
-      },
-    },
-    jasmineHtmlReporter: {
-      suppressAll: true, // removes the duplicated traces
-    },
-    coverageReporter: {
-      dir: require('path').join(__dirname, './coverage/site'),
-      subdir: '.',
-      reporters: [{type: 'html'}, {type: 'text-summary'}],
-    },
-    reporters: ['progress', 'kjhtml', 'jasmine-seed'],
-    port: 9876,
-    colors: true,
-    logLevel: config.LOG_INFO,
-    autoWatch: true,
-    customLaunchers: {
-      ChromeHeadlessNoSandbox: {
-        base: 'ChromeHeadless',
-        // See /integration/README.md#browser-tests for more info on these args
-        flags: [
-          '--no-sandbox',
-          '--headless',
-          '--disable-gpu',
-          '--disable-dev-shm-usage',
-          '--hide-scrollbars',
-          '--mute-audio',
-        ],
-      },
-    },
-    browsers: ['ChromeHeadlessNoSandbox'],
-    browserNoActivityTimeout: 60000,
-    singleRun: false,
-    restartOnFileChange: true,
-  });
-};
-
-// Helpers
-function JasmineSeedReporter(baseReporterDecorator) {
-  baseReporterDecorator(this);
-
-  this.onBrowserComplete = (browser, result) => {
-    const seed = result.order && result.order.random && result.order.seed;
-    if (seed) this.write(`${browser}: Randomized with seed ${seed}.\n`);
-  };
-
-  this.onRunComplete = () => undefined;
-}
@@ -1,30 +0,0 @@
-@defer (when isBrowser) {
-<adev-progress-bar />
-}
-<button (click)="focusFirstHeading()" class="adev-skip">Skip to main content</button>
-
-<div class="adev-nav"></div>
-@if (displaySecondaryNav()) {
-<adev-secondary-navigation />
-}
-<div class="docs-app-main-content">
-  <!--
-    Avoid rendering cookies popup on the server,
-    since there is no benefit of doing this and
-    it requires additional state management.
-  -->
-  @defer (when isBrowser) {
-    <docs-cookie-popup />
-
-    @defer (when displaySearchDialog(); prefetch on idle) {
-      @if (displaySearchDialog()) {
-        <docs-search-dialog (onClose)="displaySearchDialog.set(false)" />
-      }
-    }
-  }
-    <router-outlet />
-
-  @if (displayFooter()) {
-  <footer adev-footer></footer>
-  }
-</div>
@@ -1,86 +0,0 @@
-@use '@angular/docs/styles/media-queries' as mq;
-
-:host {
-  max-width: 2560px;
-  margin-inline: auto;
-  display: flex;
-  flex-direction: row;
-  align-items: flex-start;
-  min-height: 100vh;
-
-  @include mq.for-tablet-landscape-down {
-    flex-direction: column;
-  }
-  // If navs are open, render a blurry background over content
-  &:has(.docs-nav-secondary--open),
-  &:has(.adev-nav-primary--open) {
-    .docs-app-main-content {
-      &::after {
-        visibility: visible;
-        opacity: 1;
-      }
-    }
-  }
-
-  &:has(.adev-home) {
-    .adev-nav {
-      width: 0;
-      height: 0;
-    }
-
-    @include mq.for-tablet-landscape-up {
-      footer {
-        margin-left: var(--primary-nav-width);
-      }
-    }
-  }
-}
-
-.adev-skip {
-  position: absolute;
-  top: 0.5rem;
-  left: 0.5rem;
-  z-index: 1000;
-  background: var(--primary-contrast);
-  color: var(--page-background);
-  border: 1px solid var(--vivid-pink);
-  border-radius: 0.25rem;
-  padding: 0.5rem;
-  font-size: 0.875rem;
-  transform: translateY(-150%);
-  transition: transform 0.3s ease-out;
-  &:focus {
-    transform: translateY(0);
-  }
-}
-
-.docs-app-main-content {
-  display: flex;
-  flex-direction: column;
-  min-height: 100vh;
-  width: 100%;
-
-  // If navs are open, render a blurry background over content
-  ::after {
-    content: '';
-    position: fixed;
-    top: 0;
-    left: 0;
-    width: 100vw;
-    height: 100vh;
-    backdrop-filter: blur(2px);
-    background-color: color-mix(in srgb, var(--gray-1000) 5%, transparent);
-    z-index: 50;
-    visibility: hidden;
-    opacity: 0;
-    transition: opacity 0.3s ease;
-  }
-
-  @include mq.for-tablet {
-    width: 100%;
-  }
-}
-
-footer {
-  margin-top: auto;
-}
@@ -1,37 +0,0 @@
-/*!
- * @license
- * Copyright Google LLC All Rights Reserved.
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://angular.dev/license
- */
-
-import {TestBed} from '@angular/core/testing';
-import {AppComponent} from './app.component';
-import {provideRouter} from '@angular/router';
-import {routes} from './routes';
-import {Search, WINDOW} from '@angular/docs';
-
-describe('AppComponent', () => {
-  const fakeSearch = {};
-  const fakeWindow = {};
-
-  it('should create the app', () => {
-    TestBed.configureTestingModule({
-      providers: [
-        provideRouter(routes),
-        {
-          provide: WINDOW,
-          useValue: fakeWindow,
-        },
-        {
-          provide: Search,
-          useValue: fakeSearch,
-        },
-      ],
-    });
-    const fixture = TestBed.createComponent(AppComponent);
-    const app = fixture.componentInstance;
-    expect(app).toBeTruthy();
-  });
-});
@@ -1,133 +0,0 @@
-/*!
- * @license
- * Copyright Google LLC All Rights Reserved.
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://angular.dev/license
- */
-
-import {DOCUMENT, isPlatformBrowser} from '@angular/common';
-import {
-  Component,
-  inject,
-  NgZone,
-  OnInit,
-  PLATFORM_ID,
-  signal,
-  WritableSignal,
-} from '@angular/core';
-import {NavigationEnd, NavigationSkipped, Router, RouterLink, RouterOutlet} from '@angular/router';
-import {filter, map, skip} from 'rxjs/operators';
-import {
-  CookiePopup,
-  getActivatedRouteSnapshotFromRouter,
-  IS_SEARCH_DIALOG_OPEN,
-  SearchDialog,
-  WINDOW,
-} from '@angular/docs';
-import {Footer} from './core/layout/footer/footer.component';
-import {Navigation} from './core/layout/navigation/navigation.component';
-import {SecondaryNavigation} from './core/layout/secondary-navigation/secondary-navigation.component';
-import {ProgressBarComponent} from './core/layout/progress-bar/progress-bar.component';
-import {ESCAPE, SEARCH_TRIGGER_KEY} from './core/constants/keys';
-
-@Component({
-  standalone: true,
-  selector: 'adev-root',
-  imports: [
-    CookiePopup,
-    Navigation,
-    Footer,
-    SecondaryNavigation,
-    RouterOutlet,
-    RouterLink,
-    SearchDialog,
-    ProgressBarComponent,
-  ],
-  templateUrl: './app.component.html',
-  styleUrls: ['./app.component.scss'],
-})
-export class AppComponent implements OnInit {
-  private readonly document = inject(DOCUMENT);
-  private readonly ngZone = inject(NgZone);
-  private readonly router = inject(Router);
-  private readonly window = inject(WINDOW);
-
-  currentUrl = signal('');
-  displayFooter = signal(false);
-  displaySecondaryNav = signal(false);
-  displaySearchDialog: WritableSignal<boolean> = inject(IS_SEARCH_DIALOG_OPEN);
-
-  isBrowser = isPlatformBrowser(inject(PLATFORM_ID));
-
-  ngOnInit(): void {
-    this.setSearchDialogVisibilityOnKeyPress();
-    this.closeSearchDialogOnNavigationSkipped();
-    this.router.events
-      .pipe(
-        filter((e): e is NavigationEnd => e instanceof NavigationEnd),
-        map((event) => event.urlAfterRedirects),
-      )
-      .subscribe((url) => {
-        this.currentUrl.set(url);
-        this.setComponentsVisibility();
-        this.displaySearchDialog.set(false);
-      });
-
-    this.focusFirstHeadingOnRouteChange();
-  }
-
-  focusFirstHeading(): void {
-    if (!this.isBrowser) {
-      return;
-    }
-
-    const h1 = this.document.querySelector<HTMLHeadingElement>('h1');
-    h1?.focus();
-  }
-
-  private setComponentsVisibility(): void {
-    const activatedRoute = getActivatedRouteSnapshotFromRouter(this.router as any);
-
-    this.displaySecondaryNav.set(activatedRoute.data['displaySecondaryNav']);
-    this.displayFooter.set(!activatedRoute.data['hideFooter']);
-  }
-
-  private focusFirstHeadingOnRouteChange(): void {
-    this.router.events
-      .pipe(
-        filter((e): e is NavigationEnd => e instanceof NavigationEnd),
-        // Skip first emission, cause on the initial load we would like to `Skip to main content` popup when it's focused
-        skip(1),
-      )
-      .subscribe(() => {
-        this.focusFirstHeading();
-      });
-  }
-
-  private setSearchDialogVisibilityOnKeyPress(): void {
-    this.ngZone.runOutsideAngular(() => {
-      this.window.addEventListener('keydown', (event: KeyboardEvent) => {
-        if (event.key === SEARCH_TRIGGER_KEY && (event.metaKey || event.ctrlKey)) {
-          this.ngZone.run(() => {
-            event.preventDefault();
-            this.displaySearchDialog.update((display) => !display);
-          });
-        }
-
-        if (event.key === ESCAPE && this.displaySearchDialog()) {
-          this.ngZone.run(() => {
-            event.preventDefault();
-            this.displaySearchDialog.set(false);
-          });
-        }
-      });
-    });
-  }
-
-  private closeSearchDialogOnNavigationSkipped(): void {
-    this.router.events.pipe(filter((event) => event instanceof NavigationSkipped)).subscribe(() => {
-      this.displaySearchDialog.set(false);
-    });
-  }
-}
@@ -1,24 +0,0 @@
-/*!
- * @license
- * Copyright Google LLC All Rights Reserved.
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://angular.dev/license
- */
-
-import {mergeApplicationConfig, ApplicationConfig} from '@angular/core';
-import {provideServerRendering} from '@angular/platform-server';
-import {appConfig} from './app.config';
-import {
-  ReferenceScrollHandler,
-  ReferenceScrollHandlerNoop,
-} from './features/references/services/reference-scroll-handler.service';
-
-const serverConfig: ApplicationConfig = {
-  providers: [
-    provideServerRendering(),
-    {provide: ReferenceScrollHandler, useClass: ReferenceScrollHandlerNoop},
-  ],
-};
-
-export const config = mergeApplicationConfig(appConfig, serverConfig);
@@ -1,97 +0,0 @@
-/*!
- * @license
- * Copyright Google LLC All Rights Reserved.
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://angular.dev/license
- */
-
-import {DOCUMENT} from '@angular/common';
-import {provideHttpClient, withFetch} from '@angular/common/http';
-import {
-  ApplicationConfig,
-  ENVIRONMENT_INITIALIZER,
-  ErrorHandler,
-  inject,
-  provideZoneChangeDetection,
-} from '@angular/core';
-import {
-  DOCS_CONTENT_LOADER,
-  ENVIRONMENT,
-  EXAMPLE_VIEWER_CONTENT_LOADER,
-  PREVIEWS_COMPONENTS,
-  WINDOW,
-  windowProvider,
-} from '@angular/docs';
-import {provideClientHydration} from '@angular/platform-browser';
-import {provideAnimationsAsync} from '@angular/platform-browser/animations/async';
-import {
-  RouteReuseStrategy,
-  Router,
-  TitleStrategy,
-  createUrlTreeFromSnapshot,
-  provideRouter,
-  withInMemoryScrolling,
-  withViewTransitions,
-} from '@angular/router';
-import environment from './environment';
-import {PREVIEWS_COMPONENTS_MAP} from './../assets/previews/previews';
-import {ADevTitleStrategy} from './core/services/a-dev-title-strategy';
-import {AnalyticsService} from './core/services/analytics/analytics.service';
-import {ContentLoader} from './core/services/content-loader.service';
-import {CustomErrorHandler} from './core/services/errors-handling/error-handler';
-import {ExampleContentLoader} from './core/services/example-content-loader.service';
-import {ReuseTutorialsRouteStrategy} from './features/tutorial/tutorials-route-reuse-strategy';
-import {routes} from './routes';
-import {ReferenceScrollHandler} from './features/references/services/reference-scroll-handler.service';
-
-export const appConfig: ApplicationConfig = {
-  providers: [
-    provideRouter(
-      routes,
-      withInMemoryScrolling({anchorScrolling: 'enabled', scrollPositionRestoration: 'enabled'}),
-      withViewTransitions({
-        onViewTransitionCreated: ({transition, to}) => {
-          const router = inject(Router);
-          const toTree = createUrlTreeFromSnapshot(to, []);
-          // Skip the transition if the only thing changing is the fragment and queryParams
-          if (
-            router.isActive(toTree, {
-              paths: 'exact',
-              matrixParams: 'exact',
-              fragment: 'ignored',
-              queryParams: 'ignored',
-            })
-          ) {
-            transition.skipTransition();
-          }
-        },
-      }),
-    ),
-    provideClientHydration(),
-    provideHttpClient(withFetch()),
-    provideAnimationsAsync(),
-    {provide: ENVIRONMENT, useValue: environment},
-    {
-      provide: ENVIRONMENT_INITIALIZER,
-      multi: true,
-      useValue: () => inject(AnalyticsService),
-    },
-    {provide: ErrorHandler, useClass: CustomErrorHandler},
-    {provide: PREVIEWS_COMPONENTS, useValue: PREVIEWS_COMPONENTS_MAP},
-    {provide: DOCS_CONTENT_LOADER, useClass: ContentLoader},
-    {provide: EXAMPLE_VIEWER_CONTENT_LOADER, useClass: ExampleContentLoader},
-    {
-      provide: RouteReuseStrategy,
-      useClass: ReuseTutorialsRouteStrategy,
-    },
-    {
-      provide: WINDOW,
-      useFactory: (document: Document) => windowProvider(document),
-      deps: [DOCUMENT],
-    },
-    {provide: TitleStrategy, useClass: ADevTitleStrategy},
-    provideZoneChangeDetection({eventCoalescing: true}),
-    ReferenceScrollHandler,
-  ],
-};
@@ -1,10 +0,0 @@
-/*!
- * @license
- * Copyright Google LLC All Rights Reserved.
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://angular.dev/license
- */
-
-export const PRIMARY_NAV_ID = 'primaryNav';
-export const SECONDARY_NAV_ID = 'secondaryNav';
@@ -1,12 +0,0 @@
-/*!
- * @license
- * Copyright Google LLC All Rights Reserved.
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://angular.dev/license
- */
-
-export const COMMAND = 'Command';
-export const CONTROL = 'Control';
-export const ESCAPE = 'Escape';
-export const SEARCH_TRIGGER_KEY = 'k';
@@ -1,12 +0,0 @@
-/*!
- * @license
- * Copyright Google LLC All Rights Reserved.
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://angular.dev/license
- */
-
-export const GITHUB = 'https://github.com/angular/angular';
-export const X = 'https://x.com/angular';
-export const MEDIUM = 'https://blog.angular.io';
-export const YOUTUBE = 'https://www.youtube.com/channel/UCbn1OgGei-DV7aSRo_HaAiw';
@@ -1,28 +0,0 @@
-/*!
- * @license
- * Copyright Google LLC All Rights Reserved.
- *
- * Use of this source code is governed by an MIT-style license that can be
- * found in the LICENSE file at https://angular.dev/license
- */
-
-// File contains the enums used across whole application.
-
-// The enum with the prefixes of the main routes
-export enum PagePrefix {
-  API = 'api',
-  CLI = 'cli',
-  DOCS = 'docs',
-  HOME = '',
-  PLAYGROUND = 'playground',
-  REFERENCE = 'reference',
-  TUTORIALS = 'tutorials',
-}
-
-// The enum with the default pages for each main tab
-export enum DefaultPage {
-  DOCS = 'overview',
-  REFERENCE = 'api',
-  TUTORIALS = 'tutorials',
-  PLAYGROUND = 'playground',
-}
@@ -1,125 +0,0 @@
-<div class="adev-footer-container">
-  <div class="adev-footer-columns">
-    <div>
-      <h2>Social Media</h2>
-      <ul>
-        <li>
-          <a [href]="MEDIUM" title="Angular blog">Blog</a>
-        </li>
-        <li>
-          <a [href]="X" title="X (formerly Twitter)">X (formerly Twitter)</a>
-        </li>
-        <li>
-          <a [href]="YOUTUBE" title="YouTube">YouTube</a>
-        </li>
-        <li>
-          <a
-            href="https://discord.gg/angular"
-            title="Join the discussions at Angular Community Discord server."
-          >
-            Discord
-          </a>
-        </li>
-        <li>
-          <a [href]="GITHUB" title="GitHub">GitHub</a>
-        </li>
-        <li>
-          <a
-            href="https://stackoverflow.com/questions/tagged/angular"
-            title="Stack Overflow: where the community answers your technical Angular questions."
-          >
-            Stack Overflow
-          </a>
-        </li>
-      </ul>
-    </div>
-    <div>
-      <h2>Community</h2>
-      <ul>
-        <li>
-          <a
-            href="https://github.com/angular/angular/blob/main/CONTRIBUTING.md"
-            title="Contribute to Angular"
-          >
-            Contribute
-          </a>
-        </li>
-        <li>
-          <a
-            href="https://github.com/angular/code-of-conduct/blob/main/CODE_OF_CONDUCT.md"
-            title="Treating each other with respect."
-          >
-            Code of Conduct
-          </a>
-        </li>
-        <li>
-          <a
-            href="https://github.com/angular/angular/issues"
-            title="Post issues and suggestions on github."
-          >
-            Report Issues
-          </a>
-        </li>
-        <li>
-          <a
-            href="https://devlibrary.withgoogle.com/products/angular?sort=updated"
-            title="Google's DevLibrary"
-          >
-            Google's DevLibrary
-          </a>
-        </li>
-        <li>
-          <a
-            href="https://developers.google.com/community/experts/directory?specialization=angular"
-            title="Angular Google Developer Experts"
-          >
-            Angular Google Developer Experts
-          </a>
-        </li>
-      </ul>
-    </div>
-    <div>
-      <h2>Resources</h2>
-      <ul>
-        <li>
-          <a routerLink="/press-kit" title="Press contacts, logos, and branding.">Press Kit</a>
-        </li>
-        <li>
-          <a routerLink="/roadmap" title="Roadmap">Roadmap</a>
-        </li>
-      </ul>
-    </div>
-    <div>
-      <h2>Languages</h2>
-      <ul>
-        <li>
-          <a href="https://angular.cn/" title="简体中文版">简体中文版</a>
-        </li>
-        <li>
-          <a href="https://angular.tw/" title="正體中文版">正體中文版</a>
-        </li>
-        <li>
-          <a href="https://angular.jp/" title="日本語版">日本語版</a>
-        </li>
-        <li>
-          <a href="https://angular.kr/" title="한국어">한국어</a>
-        </li>
-        <li>
-          <a
-            href="https://angular-gr.web.app"
-            title="&Epsilon;&lambda;&lambda;&eta;&nu;&iota;&kappa;ά"
-          >
-            &Epsilon;&lambda;&lambda;&eta;&nu;&iota;&kappa;ά
-          </a>
-        </li>
-      </ul>
-    </div>
-  </div>
-  <p class="docs-license">
-    Super-powered by Google ©2010-2024. Code licensed under an
-    <a routerLink="/license" title="License text">MIT-style License</a>
-    . Documentation licensed under
-    <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>
-    .
-  </p>
-</div>
@@ -1,59 +0,0 @@
-.adev-footer-columns {
-  display: grid;
-  grid-template-columns: repeat(4, 1fr);
-  gap: 2rem;
-
-  @container footer (max-width: 600px) {
-    grid-template-columns: repeat(2, 1fr) !important;
-  }
-}
-
-.adev-footer-container {
-  container: footer / inline-size;
-  position: relative;
-  justify-content: center;
-  padding: var(--layout-padding);
-  padding-inline-end: 1rem;
-  background-color: var(--page-background);
-  transition: background-color 0.3s ease;
-
-  // this accounts for absolutely positioned TOC on the right
-  @media only screen and (min-width: 1430px) {
-    width: calc(100% - 195px - var(--layout-padding) * 3);
-  }
-
-  h2 {
-    font-size: 0.875rem;
-    font-weight: 600;
-    margin-block-end: 1.75rem;
-    letter-spacing: -0.00875rem;
-  }
-
-  ul {
-    list-style: none;
-    padding: 0;
-    display: flex;
-    flex-direction: column;
-    gap: 0.95rem;
-    li {
-      font-size: 0.8125rem;
-    }
-  }
-
-  a {
-    color: var(--quaternary-contrast);
-    font-weight: 300;
-    transition: color 0.3s ease;
-    &:hover {
-      color: var(--primary-contrast);
-    }
-  }
-  p.docs-license {
-    transition: color 0.3s ease;
-    color: var(--quaternary-contrast);
-    font-weight: 300;
-    grid-column: span 4;
-    font-size: 0.75rem;
-    margin-block-start: 2rem;
-  }
-}
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Misko Hevery	b6bd8d7572	release: cut the v9.1.0 release	2020-03-25 09:23:48 -07:00
Misko Hevery	b08168bb90	release: cut the v9.1.0-rc.2 release	2020-03-24 15:50:38 -07:00
JoostK	407fa42679	fix(common): let `KeyValuePipe` accept type unions with `null` (#36093 ) `KeyValuePipe` currently accepts `null` values as well as `Map`s and a few others. However, due to the way in which TS overloads work, a type of `T\|null` will not be accepted by `KeyValuePipe`'s signatures, even though both `T` and `null` individually would be. To make this work, each signature that accepts some type `T` has been duplicated with a second one below it that accepts a `T\|null` and includes `null` in its return type. Fixes #35743 PR Close #36093	2020-03-24 14:41:42 -07:00
Pete Bacon Darwin	aef432384a	fix(ngcc): use preserve whitespaces from tsconfig if provided (#36189 ) Previously ngcc never preserved whitespaces but this is at odds with how the ViewEngine compiler works. In ViewEngine, library templates are recompiled with the current application's tsconfig settings, which meant that whitespace preservation could be set in the application tsconfig file. This commit allows ngcc to use the `preserveWhitespaces` setting from tsconfig when compiling library templates. One should be aware that this disallows different projects with different tsconfig settings to share the same node_modules folder, with regard to whitespace preservation. But this is already the case in the current ngcc since this configuration is hard coded right now. Fixes #35871 PR Close #36189	2020-03-24 14:25:06 -07:00
JoostK	fb70083339	feat(compiler): add dependency info and ng-content selectors to metadata (#35695 ) This commit augments the `FactoryDef` declaration of Angular decorated classes to contain information about the parameter decorators used in the constructor. If no constructor is present, or none of the parameters have any Angular decorators, then this will be represented using the `null` type. Otherwise, a tuple type is used where the entry at index `i` corresponds with parameter `i`. Each tuple entry can be one of two types: 1. If the associated parameter does not have any Angular decorators, the tuple entry will be the `null` type. 2. Otherwise, a type literal is used that may declare at least one of the following properties: - "attribute": if `@Attribute` is present. The injected attribute's name is used as string literal type, or the `unknown` type if the attribute name is not a string literal. - "self": if `@Self` is present, always of type `true`. - "skipSelf": if `@SkipSelf` is present, always of type `true`. - "host": if `@Host` is present, always of type `true`. - "optional": if `@Optional` is present, always of type `true`. A property is only present if the corresponding decorator is used. Note that the `@Inject` decorator is currently not included, as it's non-trivial to properly convert the token's value expression to a type that is valid in a declaration file. Additionally, the `ComponentDefWithMeta` declaration that is created for Angular components has been extended to include all selectors on `ng-content` elements within the component's template. This additional metadata is useful for tooling such as the Angular Language Service, as it provides the ability to offer suggestions for directives/components defined in libraries. At the moment, such tooling extracts the necessary information from the _metadata.json_ manifest file as generated by ngc, however this metadata representation is being replaced by the information emitted into the declaration files. Resolves FW-1870 PR Close #35695	2020-03-24 14:21:42 -07:00
Judy Bogart	c9c2408176	docs(elements): correct typo in custom elements image (#36090 ) Fixes #36050 PR Close #36090	2020-03-24 10:36:11 -07:00
George Kalpakas	e066bddfe9	fix(elements): correctly handle setting inputs to `undefined` (#36140 ) Previously, when an input property was initially set to `undefined` it would not be correctly recognized as a change (and trigger `ngOnChanges()`). This commit ensures that explicitly setting an input to `undefined` is correctly handled the same as setting the property to any other value. This aligns the behavior of Angular custom elements with that of the corresponding components when used directly (not as custom elements). PR Close #36140	2020-03-24 10:29:33 -07:00
George Kalpakas	447a600477	fix(elements): correctly set `SimpleChange#firstChange` for pre-existing inputs (#36140 ) Previously, when an input property was set on an `NgElement` before instantiating the underlying component, the `SimpleChange` object passed to `ngOnChanges()` would have `firstChange` set to false, even if this was the first change (as far as the component instance was concerned). This commit fixes this by ensuring `SimpleChange#firstChange` is set to true on first change, regardless if the property was set before or after instantiating the component. This alignthe behavior of Angular custom elements with that of the corresponding components when used directly (not as custom elements). Jira issue: [FW-2007](https://angular-team.atlassian.net/browse/FW-2007) Fixes #36130 PR Close #36140	2020-03-24 10:29:33 -07:00
Faouzi Medebbeb	70f9bfff43	docs: fix typo in testing component with dependencies (#36219 ) Fixes #36210 PR Close #36219	2020-03-24 10:19:48 -07:00
George Kalpakas	57c02b044c	build(docs-infra): upgrade cli command docs sources to 526c3cc37 (#36225 ) Updating [angular#9.1.x](https://github.com/angular/angular/tree/9.1.x) from [cli-builds#9.1.x](https://github.com/angular/cli-builds/tree/9.1.x). ## Relevant changes in [commit range](https://github.com/angular/cli-builds/compare/1bc653bac...526c3cc37): Modified - help/deploy.json - help/doc.json - help/e2e.json - help/generate.json - help/test.json - help/update.json PR Close #36225	2020-03-24 10:18:14 -07:00
Pete Bacon Darwin	6defe962c8	fix(ngcc): use path-mappings from tsconfig in dependency resolution (#36180 ) When computing the dependencies between packages which are not in node_modules, we may need to rely upon path-mappings to find the path to the imported entry-point. This commit allows ngcc to use the path-mappings from a tsconfig file to find dependencies. By default any tsconfig.json file in the directory above the `basePath` is loaded but it is possible to use a path to a specific file by providing the `tsConfigPath` property to mainNgcc, or to turn off loading any tsconfig file by setting `tsConfigPath` to `null`. At the command line this is controlled via the `--tsconfig` option. Fixes #36119 PR Close #36180	2020-03-24 10:16:13 -07:00
Keen Yee Liau	267bcb3e9c	test(common): Add test for NgForOfContext.count (#36046 ) `NgForOfContext.count` is the length of the iterable. PR Close #36046	2020-03-24 10:15:12 -07:00
Keen Yee Liau	b0b66881b4	docs(common): Add missing entry for NgForOfContext.count (#36046 ) `count` is available in `NgForOfContext` but it's missing in the docs. PR Close #36046	2020-03-24 10:15:12 -07:00
Pawel Kozlowski	9ff8d78bcd	test(core): re-enable IE 10/11 test on SauceLabs (#35962 ) I was not able to reproduce IE 10/11 failrue of the disabled tests on SauceLabs any more. I did some cleanup of the test in question but I doubt it was the root cause of the problem. PR Close #35962	2020-03-24 10:14:48 -07:00
Joey Perrott	563b707497	fix(dev-infra): use @angular/dev-infra-private package for pullapprove verification (#35996 ) Adds devDependency on @angular/dev-infra-private and removes the verify script from tools, relying instead on the script from ng-dev. PR Close #35996	2020-03-24 10:14:06 -07:00
Misko Hevery	5357e643b3	release: cut the v9.1.0-rc.1 release	2020-03-23 13:01:11 -07:00
Filipe Silva	f71d132f7c	fix(core): workaround Terser inlining bug (#36200 ) This variable name change works around https://github.com/terser/terser/issues/615, which was causing the JIT production tests to fail in the Angular CLI repository (https://github.com/angular/angular-cli/issues/17264). PR Close #36200	2020-03-23 12:24:03 -07:00
Sonu Kapoor	ba3edda230	fix(docs-infra): change `app-list-item` to `app-item-list` (#35601 ) The `app-list-item` component sounds like it is used for a single item, however it renders a list of items. There were also several changes in the documentation, where it was becoming confusing if the `app-list-item` is using a single item or multiple items. This commit fixes this issue. It renames the component and its respective properties to make sure that the intention is very clear. Closes #35598 PR Close #35601	2020-03-23 11:40:16 -07:00
Sonu Kapoor	0767d37c07	fix(localize): allow ICU expansion case to start with any character except `}` (#36123 ) Previously, an expansion case could only start with an alpha numeric character. This commit fixes this by allowing an expansion case to start with any character except `}`. The [ICU spec](http://userguide.icu-project.org/formatparse/messages) is pretty vague: > Use a "select" argument to select sub-messages via a fixed set of keywords. It does not specify what can be a "keyword" but from looking at the surrounding syntax it appears that it can indeed be any string that does not contain a `}` character. Closes #31586 PR Close #36123	2020-03-23 11:37:12 -07:00
Joey Perrott	8ba24578bc	fix(dev-infra): change circular deps positional params to camelCase (#36165 ) Changes the positional params for the circular deps tooling to use camelCase as it requires being defined in camelCase while in strict mode. Additionally, remove the `version()` call as the boolean arguement does not exist in current versions and throws errors on execution. PR Close #36165	2020-03-23 11:36:28 -07:00
Joey Perrott	133a97ad67	fix(dev-infra): prep ts-circular-deps to load via node_modules (#36165 ) to run ts-circular-deps via installed node_modules, we needed to set the hashbang of the script to be a node environment, and discover the project directory based on where the script is run rather than the scripts file location. PR Close #36165	2020-03-23 11:36:28 -07:00
Aristeidis Bampakos	4e67a3ab3f	docs: Add asterisk info in template syntax guide (#36176 ) Add helpful alert for asterisk syntax in the `ngFor` section of template syntax guide PR Close #36176	2020-03-23 11:36:09 -07:00
Aristeidis Bampakos	377f0010fc	docs: Change important alert of ngFor (#36176 ) Update the important alert of ngFor so that it has a unique format with that of ngIf PR Close #36176	2020-03-23 11:36:09 -07:00
Abraham Williams	6e09129e4c	docs(elements): Edge supports Web Components (#36182 ) PR Close #36182	2020-03-23 11:35:49 -07:00
George Kalpakas	d80e51a6b1	build(docs-infra): upgrade cli command docs sources to 1bc653bac (#36160 ) Updating [angular#9.1.x](https://github.com/angular/angular/tree/9.1.x) from [cli-builds#9.0.x](https://github.com/angular/cli-builds/tree/9.0.x). ## Relevant changes in [commit range](https://github.com/angular/cli-builds/compare/6aa3c134c...1bc653bac): Modified - help/deploy.json - help/doc.json - help/generate.json - help/test.json - help/update.json PR Close #36160	2020-03-20 13:58:57 -07:00
profanis	feb66b00da	docs(zone.js): Typos on zone.md file and fixes on code examples. (#36138 ) 1. During reading the documentation I found some code examples that were refering to the class properties via methods, but without specifying the context `this`. 2. The 'onInvoke' hook was duplicated 3. A minor typo on `Zones and execution contexts` section 4. A minor typo on `Zones and async lifecycle hooks` section PR Close #36138	2020-03-20 13:57:01 -07:00
George Kalpakas	cb19eac105	fix(docs-infra): include correct dependencies in StackBlitz examples (#36071 ) Previously, all StackBlitz examples included the default dependencies for `cli`-type projects. However, different example types may have different `package.json` files with different dependencies. For example, the [boilerplate `package.json`][1] for `elements` examples includes an extra dependency on `@angular/elements`. This commit changes `StackblitzBuilder` to use the dependencies that correspond to each example type. (NOTE: Manually verified the changes.) Jira issue: [FW-2002][2] [1]: https://github.com/angular/angular/blob/05d058622/aio/tools/examples/shared/boilerplate/elements/package.json [2]: https://angular-team.atlassian.net/browse/FW-2002 PR Close #36071	2020-03-20 13:56:26 -07:00
George Kalpakas	6e0564ade6	refactor(docs-infra): clean up `stackblitz-builder/builder.js` script (#36071 ) - Remove unused dependencies. - Change `var` to `const/let`. - Change regular functions as callbacks to arrow functions. - Remove unnecessary intermediate variables. - Switch from custom `_existsSync()` implementation to built-in `fs.existsSync()`. PR Close #36071	2020-03-20 13:56:26 -07:00
Keen Yee Liau	05eeb7d279	test(compiler): remove whitespace in spans (#36169 ) https://github.com/angular/angular/pull/36133 and https://github.com/angular/angular/pull/35986 caused a conflict in test after they both got merged to master. This PR fixes the failed tests. PR Close #36169	2020-03-20 12:52:31 -07:00
Keen Yee Liau	2ce5fa3cce	feat(compiler): Propagate value span of ExpressionBinding to ParsedProperty (#36133 ) This commit propagates the correct value span in an ExpressionBinding of a microsyntax expression to ParsedProperty, which in turn porpagates the span to the template ASTs (both VE and Ivy). PR Close #36133	2020-03-20 10:21:11 -07:00
Sonu Kapoor	e140cdcb34	fix(docs-infra): fix image name in example (#36127 ) Closes #35618 PR Close #36127	2020-03-20 10:20:36 -07:00
Joey Perrott	14b2db1d43	feat(dev-infra): create commit-message validation script/tooling (#36117 ) PR Close #36117	2020-03-20 10:20:13 -07:00
Wagner Maciel	2afc7e982e	refactor(benchpress): delete broken code (#35922 ) PR Close #35922	2020-03-20 10:19:49 -07:00
@@ -1 +1 @@
 .18.2
 .14.1