Update dependency @ngneat/overview to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@ngneat/overview	4.1.0 → 7.0.0

---

Release Notes

ngneat/overview (@​ngneat/overview)

v7.0.0

Compare Source

⚠ BREAKING CHANGES

• 🧨 min Angular version is v20

Features

• 🎸 upgrade to ng20 and use zoneless (a6c46d0)

Bug Fixes

• 🐛 use effect in teleport (1b4fa7b)

v6.2.0

Compare Source

Features

• 🎸 change teleportTo to model (5eb355e)

6.1.2 (2025-03-31)

6.1.1 (2024-08-06)

Bug Fixes

• use ngOnChanges instead of effect to avoid signal-writes error (e8c3d3c)

v6.1.2

Compare Source

v6.1.1

Compare Source

v6.1.0

Compare Source

Features

• change to signal inputs to be zoneless compatible (2965bda)

v6.0.0

Compare Source

⚠ BREAKING CHANGES

• 🧨 Peer deps are now angular 17 and everything is standalone

Features

• 🎸 update to ng17 (99de476)

5.1.1 (2023-07-05)

Bug Fixes

• 🐛 add protection (b99302b)

v5.1.1

Compare Source

v5.1.0

Compare Source

Features

• 🎸 add inputs (7512c83)

v5.0.0

Compare Source

⚠ BREAKING CHANGES

• 🧨 The context passed to a component is now a signal
• 🧨 peer dependency is now angular v16+

Features

• 🎸 use signal to provide component context (2b8aebb)

Bug Fixes

• 🐛 update view on context change (5f38a78)

• 🤖 update to angular v16 (488187c)

---

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.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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]

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

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: yah@0.10.0
npm ERR! Found: @angular/core@15.2.9
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"15.2.9" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@">=20" from @ngneat/overview@7.0.0
npm ERR! node_modules/@ngneat/overview
npm ERR!   @ngneat/overview@"7.0.0" from the root project
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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-01-19T19_46_35_854Z-debug-0.log