From 15a3d9a7bce195608a07057d5cd62484d8ebd57a Mon Sep 17 00:00:00 2001
From: Charles Lyding <19598772+clydin@users.noreply.github.com>
Date: Thu, 11 Dec 2025 12:54:51 -0500
Subject: [PATCH] refactor(@angular/cli): remove unused update requirements
 metadata field

The internal `update` schematic was attempting to parse a `requirements`
field on the `ng-update` package.json metadata. This field is otherwise
unused and can be safely removed.
---
 .../cli/src/commands/update/schematic/index.ts     | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/packages/angular/cli/src/commands/update/schematic/index.ts b/packages/angular/cli/src/commands/update/schematic/index.ts
index 26d2d06836b4..86bfe92deca1 100644
--- a/packages/angular/cli/src/commands/update/schematic/index.ts
+++ b/packages/angular/cli/src/commands/update/schematic/index.ts
@@ -389,20 +389,6 @@ function _getUpdateMetadata(
     result.packageGroupName = metadata['packageGroupName'];
   }
 
-  if (metadata['requirements']) {
-    const requirements = metadata['requirements'];
-    // Verify that requirements are
-    if (
-      typeof requirements != 'object' ||
-      Array.isArray(requirements) ||
-      Object.keys(requirements).some((name) => typeof requirements[name] != 'string')
-    ) {
-      logger.warn(`requirements metadata of package ${packageJson.name} is malformed. Ignoring.`);
-    } else {
-      result.requirements = requirements;
-    }
-  }
-
   if (metadata['migrations']) {
     const migrations = metadata['migrations'];
     if (typeof migrations != 'string') {