chore(deps): update lodash-es to 4.17.23 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
lodash-es (source)	4.17.21 → 4.17.23

GitHub Vulnerability Alerts

CVE-2025-13465

Impact

Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.

The issue permits deletion of properties but does not allow overwriting their original behavior.

Patches

This issue is patched on 4.17.23.

---

Release Notes

lodash/lodash (lodash-es)

v4.17.23

Compare Source

v4.17.22

Compare Source

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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.

---

• 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   peer react@">=16.8.0" from @emotion/[email protected]
npm error   node_modules/@emotion/react
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/[email protected]
npm error     node_modules/@emotion/styled
npm error       @emotion/styled@"11.13.0" from the root project
npm error     @emotion/react@"^11.8.1" from [email protected]
npm error     node_modules/react-select
npm error       react-select@"^5.2.1" from the root project
npm error     1 more (the root project)
npm error   peer react@">=16.8.0" from @emotion/[email protected]
npm error   node_modules/@emotion/styled
npm error     @emotion/styled@"11.13.0" from the root project
npm error   32 more (@emotion/use-insertion-effect-with-fallbacks, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.0.0-0" from [email protected]
npm error node_modules/enzyme-adapter-react-16
npm error   dev enzyme-adapter-react-16@"^1.15.3" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^16.0.0-0" from [email protected]
npm error   node_modules/enzyme-adapter-react-16
npm error     dev enzyme-adapter-react-16@"^1.15.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-02T16_48_11_377Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-02T16_48_11_377Z-debug-0.log