Update dependency @angular/core to v16.2.12

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@angular/core (source)	16.2.10 -> 16.2.12

---

Release Notes

angular/angular (@​angular/core)

v16.2.12

Compare Source

animations

Commit	Type	Description
03f4050636	fix	remove finish listener once player is destroyed (#​51136)

common

Commit	Type	Description
e092184a5c	fix	apply fixed_srcset_width values only to fixed srcsets (#​52486)

compiler-cli

Commit	Type	Description
b3b4ae4c3a	fix	properly emit literal types in input coercion function arguments (#​52437)
873c4f2454	fix	use originally used module specifier for transform functions (#​52437)

v16.2.11

Compare Source

core

Commit	Type	Description
54ea3b65c3	fix	emit provider configured event when a service is configured with providedIn (#​52365)
78533324dc	fix	get root and platform injector providers in special cases (#​52365)
019a0f4c22	fix	load global utils before creating platform injector in the standalone case (#​52365)

router

Commit	Type	Description
b79b4aca91	fix	RouterTestingHarness should throw if a component is expected but navigation fails (#​52357)

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate[bot]]

⚠ 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: libraries/angular/package-lock.json

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/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"16.2.10" from @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"16.2.10" from the root project
npm ERR!   peer @angular/common@"16.2.10" from @angular/[email protected]
npm ERR!   node_modules/@angular/forms
npm ERR!     @angular/forms@"16.2.10" from the root project
npm ERR!   3 more (@angular/platform-browser, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"16.2.10" from @angular/[email protected]
npm ERR!   node_modules/@angular/common
npm ERR!     @angular/common@"16.2.10" from the root project
npm ERR!     peer @angular/common@"16.2.10" from @angular/[email protected]
npm ERR!     node_modules/@angular/forms
npm ERR!       @angular/forms@"16.2.10" from the root project
npm ERR!     3 more (@angular/platform-browser, ...)
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/2024-05-08T23_11_51_289Z-debug-0.log

[renovate[bot]]

⚠️ 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: libraries/angular/package-lock.json

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/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"16.2.10" from @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"16.2.10" from the root project
npm ERR!   peer @angular/common@"16.2.10" from @angular/[email protected]
npm ERR!   node_modules/@angular/forms
npm ERR!     @angular/forms@"16.2.10" from the root project
npm ERR!   3 more (@angular/platform-browser, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"16.2.10" from @angular/[email protected]
npm ERR!   node_modules/@angular/common
npm ERR!     @angular/common@"16.2.10" from the root project
npm ERR!     peer @angular/common@"16.2.10" from @angular/[email protected]
npm ERR!     node_modules/@angular/forms
npm ERR!       @angular/forms@"16.2.10" from the root project
npm ERR!     3 more (@angular/platform-browser, ...)
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/2024-09-09T20_45_37_982Z-debug-0.log