## Description Configure Renovate so it stops opening PRs that change the `pnpm.overrides` entries in the root `package.json`. These overrides are intentionally pinned via tilde ranges (see #6888) so that patch-level updates flow naturally through `pnpm-lock.yaml` (already covered by `lockFileMaintenance`), without rewriting the constraint string in `package.json` on every patch release. Renovate currently still opens PRs (e.g. #6884) to bump those override constraints — this change disables that behavior. The new `packageRule` matches the `pnpm.overrides` `depType` on the root `package.json` and disables updates for it. Lockfile maintenance keeps picking up resolvable patch versions automatically. ## Checklist — _Don't delete this checklist and make sure you do the following before opening the PR_ - [x] I have a full understanding of every line in this PR — whether the code was hand-written, AI-generated, copied from external sources or produced by any other tool - [ ] I flagged the impact of my change (minor / patch / major) either by running `pnpm run bump` or by following the instructions from the changeset bot - [x] I kept this PR focused on a single concern and did not bundle unrelated changes - [x] I followed the [gitmoji](https://gitmoji.dev/) specification for the name of the PR, including the package scope (e.g. `🐛(vitest) Something...`) when the change targets a package other than `fast-check` - [ ] I added relevant tests and they would have failed without my PR (when applicable) Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Nicolas DUBIEN <dubzzz@users.noreply.github.com>