Open
Description
Command
update
Is this a regression?
- Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
I am trying to execute ng update @angular/core@20 @angular/cli@20
to perform angular upgrade from version 19 to 20. However the cmd execution stops after emitting the warning "Installing a temporary Angular CLI versioned 20.0.1 to perform the update." without emitting any useful errors.
I am using yarn 4.4.1 as my package manager. In package.json, I have set "packageManager": "yarn@4.4.1"
and "packageManager": "yarn"
in angular.json cli
property.
Minimal Reproduction
$ ng update @angular/core@20 @angular/cli@20
Exception or Error
Repository is not clean. Update changes will be mixed with pre-existing changes.
The installed Angular CLI version is outdated.
Installing a temporary Angular CLI versioned 20.0.1 to perform the update.
Your Environment
Angular CLI: 19.2.2
Node: 22.16.0
Package Manager: yarn 4.4.1
OS: win32 x64
Angular: 19.2.2
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version
------------------------------------------------------------
@angular-devkit/architect 0.1902.2
@angular-devkit/build-angular 19.2.2
@angular-devkit/core 19.2.2
@angular-devkit/schematics 19.2.2
@angular/cdk 19.2.3
@angular/material 19.2.3
@angular/material-moment-adapter 19.2.3
@schematics/angular 19.2.2
ng-packagr 19.2.0
rxjs 7.8.1
typescript 5.6.3
zone.js 0.15.0
Anything else relevant?
Here is some additional info I got when using the DEBUG keyword.
$ DEBUG='*' ng update @angular/core@20 @angular/cli@20 --verbose --allow-dirty
Repository is not clean. Update changes will be mixed with pre-existing changes.
Locating potential npmrc files:
Trying 'C:\Users\admin\.npmrc'...found.
Locating potential yarnrc files:
The installed Angular CLI version is outdated.
Installing a temporary Angular CLI versioned 20.0.1 to perform the update.
2025-06-11T03:15:52.806Z corepack Checking C:\Users\admin\AppData\Local\Temp\angular-cli-packages-wk1vrZ\package.json
2025-06-11T03:15:52.808Z corepack Checking C:\Users\admin\AppData\Local\Temp\angular-cli-packages-wk1vrZ\.corepack.env
2025-06-11T03:15:52.808Z corepack No env file found at C:\Users\admin\AppData\Local\Temp\angular-cli-packages-wk1vrZ\.corepack.env
2025-06-11T03:15:52.809Z corepack Checking C:\Users\admin\AppData\Local\Temp\package.json
2025-06-11T03:15:52.809Z corepack Checking C:\Users\admin\AppData\Local\package.json
2025-06-11T03:15:52.809Z corepack Checking C:\Users\admin\AppData\package.json
2025-06-11T03:15:52.809Z corepack Checking C:\Users\admin\package.json
2025-06-11T03:15:52.810Z corepack Checking C:\Users\admin\.corepack.env
2025-06-11T03:15:52.810Z corepack No env file found at C:\Users\admin\.corepack.env
2025-06-11T03:15:52.810Z corepack C:\Users\admin\package.json defines yarn@4.4.1 as local package manager
2025-06-11T03:15:52.811Z corepack Using yarn@4.4.1 as defined in project manifest C:\Users\admin\package.json
2025-06-11T03:15:52.815Z corepack Reusing yarn@4.4.1 found in C:\Users\admin\AppData\Local\node\corepack\v1\yarn\4.4.1