Skip to content

fix(deps): update dependency deepmerge to ^4.3.1 - #10437

Merged
cryptodev-2s merged 2 commits into
mainfrom
renovate/deepmerge-4.x
Sep 25, 2026
Merged

cryptodev-2s merged 2 commits into
mainfrom
renovate/deepmerge-4.x

Conversation

@metamask-ci

@metamask-ci metamask-ci Bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
deepmerge ^4.2.2 → ^4.3.1 age confidence

Configuration

📅 Schedule: (UTC)

  • 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 has been generated by Mend Renovate CLI.


Note

Low Risk
Routine patch-level dependency bump with no code changes; primary touch surface is test config merging, aside from accounts-controller listing deepmerge as a runtime dependency.

Overview
This PR bumps deepmerge from ^4.2.2 to ^4.3.1 across the monorepo’s workspace package.json files and refreshes yarn.lock so everything resolves to 4.3.1.

For almost all packages the dependency stays in devDependencies (typically merged into shared Jest config via jest.config.cjs). @metamask/accounts-controller is the exception where deepmerge remains a runtime dependency; its Unreleased changelog records the bump.

There are no application or library source changes—only version pins and lockfile updates.

Reviewed by Cursor Bugbot for commit bac3acb. Bugbot is set up for automated code reviews on this repo. Configure here.

@metamask-ci
metamask-ci Bot requested review from a team as code owners September 24, 2026 14:07
@metamask-ci
metamask-ci Bot deployed to dependabot September 24, 2026 14:07 Active
@metamask-ci
metamask-ci Bot requested review from a team as code owners September 24, 2026 14:07
@metamask-ci
metamask-ci Bot deployed to default-branch September 24, 2026 14:07 Active
cryptodev-2s
cryptodev-2s previously approved these changes Sep 24, 2026
@cryptodev-2s
cryptodev-2s added this pull request to the merge queue Sep 24, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Sep 24, 2026
@metamask-ci
metamask-ci Bot deployed to dependabot September 25, 2026 06:16 Active
@cryptodev-2s
cryptodev-2s added this pull request to the merge queue Sep 25, 2026
Merged via the queue into main with commit 9def618 Sep 25, 2026
339 checks passed
@cryptodev-2s
cryptodev-2s deleted the renovate/deepmerge-4.x branch September 25, 2026 09:05
@abretonc7s abretonc7s mentioned this pull request Sep 30, 2026
3 of 4 tasks
github-merge-queue Bot pushed a commit that referenced this pull request Sep 30, 2026
## Explanation

- Release major perps-controller 19.0.0

Breaking changes (see changelog):
- `OrderFill.liquidation.liquidatedUser` is now optional
- `FrontendOrder.orderType` union adds `Twap Slice`, `Vault Close`,
`Spot Dust Conversion`
- Removed `LighterPersonalSigner` and the `personalSigner` / `l1Address`
fields of `LighterAuthConfig`

## References

- #10414, #10437, #10464, #10559, #10588, #10589, #10591

## Checklist

- [x] 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
- [x] 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant