Update dependency recharts to v2.15.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
recharts	2.15.0 → 2.15.4

---

Release Notes

recharts/recharts (recharts)

v2.15.4

Compare Source

What's Changed

Last 2.x patch - releasing since the @babel/runtime vulnerability is showing up in some security scans. Hoping to release 3.0 on 6/22 🚀

Fix

• X/YAxis: fix issue where recharts class names did not get passed to custom tick components by @​MyungAe in #​5840
• Bar: allow minPointSize function to receive null and undefined values by @​eino in #​5947
• TypeScript: fix issue which caused build errors when allowSyntheticDefaultImports: false by @​tfaller in #​5810

Security

• resolve @​babel/runtime ReDoS vulnerability (SNYK-JS-BABELRUNTIME-10044504) by @​moehaje in #​5969
  • recharts isn't vulnerable to this per-se, but it does show up in security tooling like snyk

New Contributors

• @​moehaje made their first contribution in #​5969

Full Changelog: recharts/recharts@v2.15.3...v2.15.4

v2.15.3

Compare Source

Last patch release before 3.0 🚀

What's Changed

Fix

• XAxis: fix padding calculation for padding="gap" and padding="no-gap" when XAxis is type number by @​jackfletch in #​5759

Full Changelog: recharts/recharts@v2.15.2...v2.15.3

v2.15.2

Compare Source

What's Changed

Few bugfixes and bug fix backports for 2.x

Fix

• Bar/Rectangle: add index back to Bar Rectangle key to prevent duplicate key issues by @​ckifer in #​5561
• Dot: re-include points object in dotProps by @​brodriguezmilla in #​5657
• Tooltip: add SVGProps to Tooltip payload type to account for svg properties such as opacity passed by the user by @​ally1002 in #​5712
• Tooltip/Bar: fix activeBar prop not working when tooltip shared={false} by @​nizans in #​5718
• General: allow data-* props to be spread on svg elements and not be filtered out by @​prtmwrkr in #​5666

New Contributors

• @​brodriguezmilla made their first contribution in #​5657
• @​nizans made their first contribution in #​5718

Full Changelog: recharts/recharts@v2.15.1...v2.15.2

v2.15.1

Compare Source

What's Changed

Quick patch release, nothing crazy going on here.

In the meantime please help us test recharts 3.0 alpha #​5445 🚀

Fix

• Legend - Typescript: add dataKey type to legend formatter props by @​lucasassisrosa in #​5511. Fixes #​5508

Chore

• Make sure react-smooth version is up to date in package.json for R19 support by @​acomanescu in #​5422

New Contributors

• @​acomanescu made their first contribution in #​5422
• @​lucasassisrosa made their first contribution in #​5511

Full Changelog: recharts/recharts@v2.15.0...v2.15.1

---

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 is behind base branch, 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
10x-crm	Ready	Preview, Comment	May 12, 2026 2:11pm

[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. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-day-picker@8.10.1
npm error Found: date-fns@4.1.0
npm error node_modules/date-fns
npm error   date-fns@"4.1.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer date-fns@"^2.28.0 || ^3.0.0" from react-day-picker@8.10.1
npm error node_modules/react-day-picker
npm error   react-day-picker@"8.10.1" from the root project
npm error
npm error Conflicting peer dependency: date-fns@3.6.0
npm error node_modules/date-fns
npm error   peer date-fns@"^2.28.0 || ^3.0.0" from react-day-picker@8.10.1
npm error   node_modules/react-day-picker
npm error     react-day-picker@"8.10.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-05-12T14_10_15_666Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-12T14_10_15_666Z-debug-0.log