## Explanation
By default Renovate leaves a manifest alone when the new version already
satisfies the declared range, so MetaMask#10318 bumped `ts-jest` to 29.4.12 in
`yarn.lock` and touched no `package.json` at all. That keeps the
declared minimum at the old version and produces no changelog entry,
since nothing published changed.
We want a changelog entry for every dependency bump, so `rangeStrategy:
bump` moves the range with the release: `^29.4.11` becomes `^29.4.12`
across every workspace that declares it, the same as Dependabot does
today. Out of range updates like MetaMask#10320 already behaved this way.
`peerDependencies` are exempted back to `widen`. An explicit
`rangeStrategy` overrides Renovate's peer handling
([`npm/range.ts`](https://github.com/renovatebot/renovate/blob/main/lib/modules/manager/npm/range.ts)),
and 11 peer entries here have simple ranges that would be narrowed
rather than broadened, `@babel/runtime ^7.0.0` most obviously. The other
11 are complex ranges like `^16.8.0 || ^17.0.0` and widen regardless.
The cost is diff size. A single patch now rewrites the same line in
every manifest that declares the dependency, and each of those packages
needs an entry. MetaMask#10322 is what writes them.
> [!IMPORTANT]
> Depends on MetaMask#10322. Without it the repair workflow still skips Renovate
pull requests, and every one of them lands red on `Check changelog`.
## References
Depends on MetaMask#10322. Follows MetaMask#10317. Part of WPC-1161.
## Checklist
- [ ] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> **Low Risk**
> Tooling-only change to Renovate; it does not alter runtime code, but
it will enlarge dependency PR diffs across workspaces.
>
> **Overview**
> Renovate is configured to **raise semver ranges in `package.json`**
when a newer release still satisfies the existing constraint
(`rangeStrategy: bump`), matching Dependabot behavior so lockfile-only
bumps no longer skip manifest updates and downstream changelog tooling
can see a published change.
>
> A **peer-only override** sets `rangeStrategy: widen` for
`peerDependencies`, undoing the global bump so wide peer ranges stay
broadened instead of tightened.
>
> **Note:** This is meant to work with the changelog repair workflow in
MetaMask#10322; without that, Renovate PRs may fail `Check changelog`.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
9ab221a. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
This PR contains the following updates:
29.4.11→29.4.12Release Notes
kulshekhar/ts-jest (ts-jest)
v29.4.12Compare Source
Features
Configuration
📅 Schedule: (UTC)
🚦 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 this update again.
This PR has been generated by Mend Renovate CLI.
Note
Cursor Bugbot is generating a summary for commit 8aadb64. Configure here.