build: update cross-repo angular dependencies

This PR contains the following updates:

Package	Type	Update	Change
@angular-devkit/architect-cli	devDependencies	minor	0.1500.0-rc.0 -> 0.1501.0-next.0
@angular-devkit/build-angular	dependencies	minor	15.0.0-rc.0 -> 15.1.0-next.0
@angular-devkit/build-angular	devDependencies	minor	15.0.0 -> 15.1.0-next.0
@angular-devkit/core	dependencies	minor	15.0.0-rc.0 -> 15.1.0-next.0
@angular-devkit/schematics	dependencies	minor	15.0.0-rc.0 -> 15.1.0-next.0
@angular/animations	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/build-tooling	devDependencies	digest	90004d8 -> 6016be3
@angular/cli	dependencies	minor	15.0.0-rc.0 -> 15.1.0-next.0
@angular/cli	devDependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/common	peerDependencies	major	^14.0.0 -> ^15.0.0
@angular/common	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/compiler	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/compiler-cli (source)	devDependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/core	peerDependencies	major	^14.0.0 -> ^15.0.0
@angular/core	dependencies	major	^13.0.0 || ^14.0.0-0 -> ^15.0.0
@angular/core	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/elements	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/forms	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/ng-dev	devDependencies	digest	60bcee1 -> 183ef30
@angular/platform-browser	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/platform-browser-dynamic	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/router (source)	dependencies	minor	15.0.0 -> 15.1.0-next.0
@angular/service-worker	dependencies	minor	15.0.0 -> 15.1.0-next.0
@schematics/angular	dependencies	minor	15.0.0-rc.0 -> 15.1.0-next.0
angular/dev-infra	action	digest	d87b1b5 -> fcdcc61

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

🔡 If you wish to disable git hash updates, add ":disableDigestUpdates" to the extends array in your config.

---

Release Notes

angular/angular-cli

v0.1501.0-next.0

Compare Source

v0.1500.1

Compare Source

v0.1500.0

Compare Source

v0.1500.0-rc.5

Compare Source

v0.1500.0-rc.4

Compare Source

v0.1500.0-rc.3

Compare Source

v0.1500.0-rc.2

Compare Source

v0.1500.0-rc.1

Compare Source

angular/angular

v15.1.0-next.0

Compare Source

Deprecations

router

• router writable properties

  The following strategies are meant to be configured by registering the application strategy in DI via the providers in the root NgModule or bootstrapApplication:

  • routeReuseStrategy
  • titleStrategy
  • urlHandlingStrategy

  The following options are meant to be configured using the options available in RouterModule.forRoot or provideRouter.

  • onSameUrlNavigation
  • paramsInheritanceStrategy
  • urlUpdateStrategy
  • canceledNavigationResolution

  The following options are available in RouterModule.forRoot but not available in provideRouter:

  • malformedUriErrorHandler - This was found to not be used anywhere internally.
  • errorHandler - Developers can instead subscribe to Router.events and filter for NavigationError.

common

Commit	Type	Description
b0a62bea47	fix	Fix MockPlatformLocation events and missing onPopState implementation (#​48113)

core

Commit	Type	Description
6acae1477a	feat	Add TestBed.runInInjectionContext to help test functions which use inject (#​47955)

forms

Commit	Type	Description
0329c13e95	fix	don't mutate validators array (#​47830)
d321880440	fix	FormBuilder.group return right type with shorthand parameters. (#​48084)

language-service

Commit	Type	Description
5f0b53c735	feat	Allow auto-imports to suggest multiple possible imports. (#​47787)
fd2eea5961	fix	correctly handle host directive inputs/outputs (#​48147)
ce8160ecb2	fix	Prevent crashes on unemitable references (#​47938)
764fa3d9c3	fix	update packages/language-service/build.sh script to work with vscode-ng-language-service's new Bazel build (#​48120)

router

Commit	Type	Description
0a8b8a66cd	docs	Deprecate public members of Router that are meant to be configured elsewhere (#​48006)
73f03ad2d2	feat	Add new NavigationSkipped event for ignored navigations (#​48024)
b51929a394	fix	correct type of nextState parameter in canDeactivate (#​48038)
1df0ed7d6e	fix	Ensure renavigating in component init works with enabledBlocking (#​48063)
1976e37475	fix	restore 'history.state' on popstate even if navigationId missing (#​48033)

Special Thanks

Alan Agius, Andrew Kushnir, Andrew Scott, Bjarki, Bob Watson, Brooke, Derek Cormier, Dylan Hunn, George Kalpakas, Greg Magolan, Ikko Ashimine, Ivan Rodriguez, Jessica Janiuk, JiaLiPassion, Joe Roxbury, Joey Perrott, Kristiyan Kostadinov, Matthieu Riegler, Mikhail Savchuk, Nebojsa Cvetkovic, Pawel Kozlowski, Volodymyr, Wooshaah and mgechev

v15.0.1

Compare Source

common

Commit	Type	Description
930af9dd26	fix	Fix MockPlatformLocation events and missing onPopState implementation (#​48113)

forms

Commit	Type	Description
b342e55509	fix	don't mutate validators array (#​47830)
a12a120272	fix	FormBuilder.group return right type with shorthand parameters. (#​48084)

language-service

Commit	Type	Description
cc8b76ef7c	fix	correctly handle host directive inputs/outputs (#​48147)
a8c33bf931	fix	update packages/language-service/build.sh script to work with vscode-ng-language-service's new Bazel build (#​48120)

router

Commit	Type	Description
e4309d57d8	fix	correct type of nextState parameter in canDeactivate (#​48038)
9baefd085f	fix	Ensure renavigating in component init works with enabledBlocking (#​48063)
fa5528fb5f	fix	restore 'history.state' on popstate even if navigationId missing (#​48033)

Special Thanks

Alan Agius, Andrew Scott, Bjarki, Bob Watson, Brooke, Derek Cormier, Dylan Hunn, George Kalpakas, Greg Magolan, Ikko Ashimine, Ivan Rodriguez, Jessica Janiuk, Joe Roxbury, Joey Perrott, Kristiyan Kostadinov, Matthieu Riegler, Mikhail Savchuk, Nebojsa Cvetkovic, Pawel Kozlowski, Volodymyr and Wooshaah

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• [ ] If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Renovate Bot.

Caretaker Note: Please ignore Branch Manager status as this was done in testing and is not necessarily accurate

@josephperrott This conflicts with 15.0.x and can't merge cleanly. Let me know what you'd like to do here.

@jessicajaniuk I noticed you marked this for merge but it has some CI failures. Looks like they are module build failures? I'm going to ask the bot for a rebase and rerun

@dylhunn adding action: cleanup typically results in no action on angular-robot PRs since a robot created them, and they end up sitting around. I don't know what our official process is here.

@josephperrott it looks like this PR has a merge conflict. Could you please rebase and resolve the conflict when you get a chance?

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: aio/content/examples/marketing-first-app/package-lock.json

npm notice 
npm notice New major version of npm available! 8.19.2 -> 9.1.3
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.3>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular/[email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/compiler
npm ERR!   @angular/compiler@"15.1.0-next.1" from the root project
npm ERR!   peer @angular/compiler@"15.1.0-next.1" from @angular/[email protected]
npm ERR!   node_modules/@angular/platform-browser-dynamic
npm ERR!     @angular/platform-browser-dynamic@"15.1.0-next.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler@"15.0.1" from @angular/[email protected]
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   dev @angular/compiler-cli@"~15.0.1" from the root project
npm ERR!   peer @angular/compiler-cli@"^15.0.0" from @angular-devkit/[email protected]
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"~15.0.1" from the root project
npm ERR!   1 more (@ngtools/webpack)
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/compiler
npm ERR!   peer @angular/compiler@"15.0.1" from @angular/[email protected]
npm ERR!   node_modules/@angular/compiler-cli
npm ERR!     dev @angular/compiler-cli@"~15.0.1" from the root project
npm ERR!     peer @angular/compiler-cli@"^15.0.0" from @angular-devkit/[email protected]
npm ERR!     node_modules/@angular-devkit/build-angular
npm ERR!       dev @angular-devkit/build-angular@"~15.0.1" from the root project
npm ERR!     1 more (@ngtools/webpack)
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2022-12-06T19_32_31_707Z-debug-0.log

Does not apply cleanly on patch, will send another pr separately

This PR was merged into the repository by commit 7c4e9ce5c0eb99f9cf6e4ad2faa9197d0ff986ec.

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.}