Closed boeckMt closed 2 weeks ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@angular-devkit/architect@0.1602.10, npm/@angular-devkit/build-angular@16.2.10, npm/@angular-devkit/core@16.2.10, npm/@angular-devkit/schematics@16.2.10, npm/@angular/animations@16.2.12, npm/@angular/cli@16.2.10, npm/@angular/common@16.2.12, npm/@angular/compiler-cli@16.2.12, npm/@angular/compiler@16.2.12, npm/@angular/core@16.2.12, npm/@angular/forms@16.2.12, npm/@angular/language-service@16.2.12, npm/@angular/platform-browser-dynamic@16.2.12, npm/@angular/platform-browser@16.2.12, npm/@angular/router@16.2.12, npm/@cds/core@6.9.0, npm/@clr/angular@15.13.0, npm/@clr/icons@13.0.2, npm/@clr/ui@15.13.0, npm/@compodoc/compodoc@1.1.23, npm/@schematics/angular@16.2.10, npm/@types/cpx@1.5.5, npm/@types/node@20.10.1, npm/cpx@1.5.0, npm/delaunator@5.0.0, npm/jasmine-core@4.6.0
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎
This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number:
232
What is the new behavior?
Angular is updated to version 17 and all related packages are set to a comatible version of angular 17.
Updates:
A pre-release 13.0.1-next.0 has been built in case someone needs to stay with Angulr 16 and wants the updates of Map cesium
And a pre-release 14.0.0-next.0 for this PR
Does this PR introduce a breaking change?
Other information
Is it part of one/more packages and which?
All of the packages