fix(deps): update dependency recharts to v2.13.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
recharts	2.13.0-alpha.4 -> 2.13.0

---

Release Notes

recharts/recharts (recharts)

v2.13.0

Compare Source

What's Changed

React 19 compat, fix annoying defaultProps warnings, bug fixes

Feat

• React 19 compatibility - see https://github.com/recharts/recharts/issues/4558

  • peerDependencies still cannot be updated until release, but for now R19 beta/RC releases can be used with Recharts under the following conditions:
    • Your react-is version matches your react and react-dom versions: use your package manager's override functionality to match your react-is version to your react version or else recharts elements will not show - see https://github.com/recharts/recharts/issues/4558#issuecomment-2135604065

• CartesianGrid: add support for ry prop to curve the corner of the grid background - progress on https://github.com/recharts/recharts/issues/3062

Fix

• General: Fix defaultProps usage in function components, removes warnings on all affected components - see https://github.com/recharts/recharts/issues/3615
• ReferenceLine: fix accidental removal of type annotation by @​zackliscio in https://github.com/recharts/recharts/pull/4610
• Line/Area: fix issue where clipDot would not take effect if it was the only property in dotProps @​ckifer in https://github.com/recharts/recharts/pull/4674
• Tooltip: fix issue where tooltip would not show in certain cases if data was set on the graphical item by @​HHongSeungWoo in https://github.com/recharts/recharts/pull/4718
• X/YAxis: use correct, adapted event types by @​ckifer in https://github.com/recharts/recharts/pull/4967
• Tooltip: defaultIndex out of range error by @​ckifer in https://github.com/recharts/recharts/pull/5054
• Pie: fix duplicate key error @​ckifer in https://github.com/recharts/recharts/pull/4958
• Text: fix duplicate key error by @​ckifer in https://github.com/recharts/recharts/pull/5088 closes https://github.com/recharts/recharts/issues/5072

Typescript

• JSDoc comments will now be preserved in TypeScript definitions by @​mxdvl in https://github.com/recharts/recharts/pull/5071

New Contributors

• @​zackliscio made their first contribution in https://github.com/recharts/recharts/pull/4610

Full Changelog: recharts/recharts@v2.12.7...v2.13.0

v2.13.0-alpha.5

Compare Source

What's Changed

Some non-breaking bug fixes that need more testing with React 19. Fixes JSX type issue for React 19 when using @types/react@19

Fix

• Line/Area: clipDot setting fails to take effect if set as the only DotProp by @​ckifer in https://github.com/recharts/recharts/pull/4674 fixes https://github.com/recharts/recharts/issues/4671
• Tooltip: Tooltip now renders correctly when data is set on the graphical item rather than the higher level chart by @​HHongSeungWoo in https://github.com/recharts/recharts/pull/4718 fixes https://github.com/recharts/recharts/issues/4717
• Pie: fix duplicate key issue when "key" exists in chart data (try not use "key" as a data point) by @​ckifer in https://github.com/recharts/recharts/pull/4958 fixes https://github.com/recharts/recharts/issues/4858

TypeScript

• XAxis/YAxis: Correct Cartesian axis event types by @​ckifer in https://github.com/recharts/recharts/pull/4967 fixes https://github.com/recharts/recharts/issues/4959
• TypeScript: return JSX in a function instead of a class component by @​ckifer in https://github.com/recharts/recharts/pull/4970 fixes React 19 type issues https://github.com/recharts/recharts/issues/4558#issuecomment-2330578162

Full Changelog: recharts/recharts@v2.13.0-alpha.4...v2.13.0-alpha.5

---

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request focus on the package.json file for the client project, specifically updating the version of the recharts package from an alpha version to a stable release. No other dependencies or devDependencies were modified, and the overall structure of the package.json remains intact.

Changes

File	Change Summary
Client/package.json	Updated recharts from "2.13.0-alpha.4" to "2.13.0"

Possibly related PRs

• fix(deps): update dependency dayjs to v1.11.13 #1014: The changes in this PR involve updating the dayjs dependency in the Client/package.json, similar to the main PR's update of the recharts dependency in the same file.
• fix(deps): update dependency joi to v17.13.3 #1016: This PR also updates a dependency (joi) in the Client/package.json, making it relevant to the main PR's changes in the same file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.