Repository navigation
chore(deps): update angular-cli monorepo to v22 - #25
renovate-appwrite[bot] wants to merge 1 commit into
Conversation
renovate-appwrite
Bot
added
the
dependencies
|
🟡 Tier B · Needs changes before merging
This updates the Angular CLI and build tool dependencies from major version 21 to 22. The application framework and compiler dependencies remain on version 21 in this change.
Fix with agent prompt### Issue 1
package.json:30-31
**Update the lockfile with these dependency versions**
`package-lock.json` still records `@angular/build` and `@angular/cli` as `^21.2.29`, so the CI workflow's `npm ci` step fails because the lockfile does not match `package.json` (the reported build failure occurs at this install step). Please regenerate and commit the lockfile alongside this change.
### Issue 2
package.json:30-31
**Keep the Angular toolchain on a compatible major version**
`@angular/build@22` requires Angular 22 peers and TypeScript `>=6.0 <6.1`, but this manifest still has Angular and `@angular/compiler-cli` 21 with TypeScript 5.9. Even after refreshing the lockfile, npm cannot resolve this dependency set and the build toolchain is incompatible; align the framework/compiler/TypeScript versions or keep `@angular/build` on 21.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.📂 Walkthrough · 1
Reviewed |
![appwrite[bot]](https://avatars.githubusercontent.com/in/325556?s=60&v=4){kind=small}
| "@angular/build": "^22.0.0", | ||
| "@angular/cli": "^22.0.0", |
There was a problem hiding this comment.
Update the lockfile with these dependency versions
package-lock.json still records @angular/build and @angular/cli as ^21.2.29, so the CI workflow's npm ci step fails because the lockfile does not match package.json (the reported build failure occurs at this install step). Please regenerate and commit the lockfile alongside this change.
Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 30-31
Comment:
**Update the lockfile with these dependency versions**
`package-lock.json` still records `@angular/build` and `@angular/cli` as `^21.2.29`, so the CI workflow's `npm ci` step fails because the lockfile does not match `package.json` (the reported build failure occurs at this install step). Please regenerate and commit the lockfile alongside this change.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.🟠 Major · bug · Reply if this doesn't apply.
| "@angular/build": "^22.0.0", | ||
| "@angular/cli": "^22.0.0", |
There was a problem hiding this comment.
Keep the Angular toolchain on a compatible major version
@angular/build@22 requires Angular 22 peers and TypeScript >=6.0 <6.1, but this manifest still has Angular and @angular/compiler-cli 21 with TypeScript 5.9. Even after refreshing the lockfile, npm cannot resolve this dependency set and the build toolchain is incompatible; align the framework/compiler/TypeScript versions or keep @angular/build on 21.
Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 30-31
Comment:
**Keep the Angular toolchain on a compatible major version**
`@angular/build@22` requires Angular 22 peers and TypeScript `>=6.0 <6.1`, but this manifest still has Angular and `@angular/compiler-cli` 21 with TypeScript 5.9. Even after refreshing the lockfile, npm cannot resolve this dependency set and the build toolchain is incompatible; align the framework/compiler/TypeScript versions or keep `@angular/build` on 21.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.🟠 Major · bug · Reply if this doesn't apply.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^21.2.29→^22.0.0^21.2.29→^22.0.0Release Notes
angular/angular-cli (@angular/build)
v22.2.5Compare Source
@angular/cli
@schematics/angular
module --routecomponent@angular-devkit/build-angular
sslKeyandsslCertrelative to the workspace root (#34399)@angular-devkit/core
@angular-devkit/schematics
partition(#34539)filterrule (#34539)@angular/build
sslKeyandsslCertrelative to the workspace root (#34399)@angular/ssr
v22.2.4Compare Source
@angular/cli
@schematics/angular
viewEncapsulationto generated application componentsfindModuleerrorwebWorkerTsConfigfor unit-test builder test targets@angular/build
browserserrorstylesandpolyfillspaths@angular/ssr
X-Forwarded-Prefixheaderv22.2.3Compare Source
@angular/cli
@schematics/angular
@angular-devkit/schematics
@angular/build
@angular/ssr
v22.2.2Compare Source
@angular-devkit/build-angular
@angular/build
contextin array-form proxy configurationsv22.2.1Compare Source
@angular/cli
@schematics/angular
@angular-devkit/schematics-cli
@angular-devkit/architect
@angular-devkit/build-angular
@angular/build
v22.2.0Compare Source
Deprecations
@angular/build
The
splittingoption in the unit-test builder is deprecated as it is no longer needed with Vitest 5.Disabling code splitting is no longer necessary with Vitest 5, as the issue where shared-module exports were uninitialized in class-field initializers under JSDOM has been resolved.
@angular/cli
--rootcommand line option tomcpcommand@angular/build
@angular/ssr
v22.1.9Compare Source
@schematics/angular
@angular-devkit/core
@angular/build
v22.1.8Compare Source
@angular/build
v22.1.7Compare Source
@angular/cli
@angular/build
@angular/ssr
v22.1.6Compare Source
@angular/build
@angular/ssr
v22.1.5Compare Source
@angular/cli
@schematics/angular
@angular/build
v22.1.4Compare Source
@angular/cli
@schematics/angular
@angular/build
| Commit
Configuration
📅 Schedule: (UTC)
* * * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate CLI.