Repository navigation
ng update not showing patches #33508
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
not sure exactly, probably since 21.x.x
Description
"ng update" is not showing patches versions, it says everything is "up to date" but there are pending patches. However, if I run "ng update @angular/cli" it works properly and installs the latest patch.
Minimal Reproduction
I have cloned a project, I have deleted package-lock.json and I have done a clean "npm install" to make sure all package.json, package-lock.json and node_modules are aligned. When I run "ng update" after that it says:
Using package manager: npm
Collecting installed dependencies...
Found 23 dependencies.
We analyzed your package.json and everything seems to be in order. Good work!
But when I check for new versions (I use ncu) I see this:
❯ (*) @angular/animations ^22.0.1 → ^22.0.5
(*) @angular/build ^22.0.1 → ^22.0.5
(*) @angular/cdk ^22.0.1 → ^22.0.3
(*) @angular/cli ^22.0.1 → ^22.0.5
(*) @angular/common ^22.0.1 → ^22.0.5
(*) @angular/compiler ^22.0.1 → ^22.0.5
(*) @angular/compiler-cli ^22.0.1 → ^22.0.5
(*) @angular/core ^22.0.1 → ^22.0.5
(*) @angular/forms ^22.0.1 → ^22.0.5
(*) @angular/material ^22.0.1 → ^22.0.3
(*) @angular/platform-browser ^22.0.1 → ^22.0.5
(*) @angular/router ^22.0.1 → ^22.0.5
If I run manually "ng update @angular/cli @angular/core @angular/material" it works fine and the new versions are installed.
This is my current package.json file:
{
"name": "ipuinak",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"watch": "ng build --watch --configuration development",
"test": "ng test",
"lint": "ng lint"
},
"private": true,
"packageManager": "npm@11.17.0",
"dependencies": {
"@angular/animations": "^22.0.1",
"@angular/cdk": "^22.0.1",
"@angular/common": "^22.0.1",
"@angular/compiler": "^22.0.1",
"@angular/core": "^22.0.1",
"@angular/forms": "^22.0.1",
"@angular/material": "^22.0.1",
"@angular/platform-browser": "^22.0.1",
"@angular/router": "^22.0.1",
"@osumi/angular-tools": "^1.5.1",
"@osumi/tools": "^1.7.1",
"rxjs": "~7.8.2",
"tslib": "^2.8.1"
},
"devDependencies": {
"@angular/build": "^22.0.1",
"@angular/cli": "^22.0.1",
"@angular/compiler-cli": "^22.0.1",
"@eslint/js": "^10.0.1",
"angular-eslint": "22.0.0",
"eslint": "^10.5.0",
"jsdom": "^29.1.1",
"typescript": "~6.0.3",
"typescript-eslint": "^8.61.1",
"vitest": "^4.1.9"
}
}Exception or Error
Your Environment
Angular CLI : 22.0.1
Angular : 22.0.1
Node.js : 24.16.0
Package Manager : npm 11.17.0
Operating System : win32 x64
┌───────────────────────────┬───────────────────┬───────────────────┐
│ Package │ Installed Version │ Requested Version │
├───────────────────────────┼───────────────────┼───────────────────┤
│ @angular/animations │ 22.0.1 │ ^22.0.1 │
│ @angular/build │ 22.0.1 │ ^22.0.1 │
│ @angular/cdk │ 22.0.1 │ ^22.0.1 │
│ @angular/cli │ 22.0.1 │ ^22.0.1 │
│ @angular/common │ 22.0.1 │ ^22.0.1 │
│ @angular/compiler │ 22.0.1 │ ^22.0.1 │
│ @angular/compiler-cli │ 22.0.1 │ ^22.0.1 │
│ @angular/core │ 22.0.1 │ ^22.0.1 │
│ @angular/forms │ 22.0.1 │ ^22.0.1 │
│ @angular/material │ 22.0.1 │ ^22.0.1 │
│ @angular/platform-browser │ 22.0.1 │ ^22.0.1 │
│ @angular/router │ 22.0.1 │ ^22.0.1 │
│ rxjs │ 7.8.2 │ ~7.8.2 │
│ typescript │ 6.0.3 │ ~6.0.3 │
│ vitest │ 4.1.9 │ ^4.1.9 │
└───────────────────────────┴───────────────────┴───────────────────┘
Anything else relevant?
There was another issue opened about this (#33500) but it was closed without a useful answer. I am opening this issue addressing all the points that were used as a reply to show that is not working properly.
Activity
osumionline commentedon Jul 3, 2026
I forgot to add that this used to be the previous usage, as every week I used to install the new updates on a lot of projects that I have.
alan-agius4 commentedon Jul 3, 2026
This behavior is intentional and consistent with previous versions.
osumionline commentedon Jul 5, 2026
It's not "consistent with previous versions" because it used to work and now it doesn't. How are we suposed to install new versions? How is it consistent to tell "there are no updates" but if I run the update command for a package it works?
angular-automatic-lock-bot commentedon Aug 5, 2026
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.