From 2cfc8368607c298347a4ed3283096a48c17477c8 Mon Sep 17 00:00:00 2001
From: Charles Lyding <19598772+clydin@users.noreply.github.com>
Date: Thu, 25 Jun 2026 10:42:15 -0400
Subject: [PATCH] fix(@angular/cli): respect release age policy in update
 bootstrapping logic

Querying version target returns the resolved range/tag specifier instead of the resolved specific version number if the installed CLI version is outdated. This allows the package manager to natively enforce release-age policies (like pnpm's `minimum-release-age` or yarn's `npmMinimalAgeGate`) and select an appropriate older version during temporary installation rather than crashing.
---
 .../angular/cli/src/commands/update/utilities/cli-version.ts    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/angular/cli/src/commands/update/utilities/cli-version.ts b/packages/angular/cli/src/commands/update/utilities/cli-version.ts
index 6067b81504d4..3791f7ad7070 100644
--- a/packages/angular/cli/src/commands/update/utilities/cli-version.ts
+++ b/packages/angular/cli/src/commands/update/utilities/cli-version.ts
@@ -70,7 +70,7 @@ export async function checkCLIVersion(
 
   const version = manifest.version;
 
-  return VERSION.full === version ? null : version;
+  return VERSION.full === version ? null : String(runnerVersion);
 }
 
 /**