Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade recharts from 2.3.2 to 2.13.3 #620

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gptkrsh
Copy link
Owner

@gptkrsh gptkrsh commented Nov 24, 2024

snyk-top-banner

Snyk has created this PR to upgrade recharts from 2.3.2 to 2.13.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 42 versions ahead of your current version.

  • The recommended version was released on 23 days ago.

Release notes
Package name: recharts
  • 2.13.3 - 2024-11-01

    What's Changed

    Small change which may (or may not) help when using ResponsiveContainer with React 19. Worth a shot.

    !! react-is override is still needed for React 19 to work correctly with recharts !! - see #4558

    Fix

    • 7a67b41 ResponsiveContainer - swap isElement from react-is with React.isValidElement

    Full Changelog: v2.13.2...v2.13.3

  • 2.13.2 - 2024-10-30

    What's Changed

    • Another fix from 2.13. Categorical charts should have their ref props back.

    Fix

    • fix: forwardRef to CategoricalChartWrapper from CategoricalChart by @ ckifer in #5176 - fixes #5113

    Full Changelog: v2.13.1...v2.13.2

  • 2.13.1 - 2024-10-29

    What's Changed

    • Small bug fixes from the 2.13 release

    Fix

    • ResponsiveContainer: fix internal bug from 2.13 which causes responsive container to render incorrectly by @ ckifer in #5174
    • Bar: radius prop type fixed to match expected type by @ lifeofpavs in #5116

    New Contributors

    Full Changelog: v2.13.0...v2.13.1

  • 2.13.0 - 2024-10-10

    What's Changed

    React 19 compat, fix annoying defaultProps warnings, bug fixes

    Feat

    • React 19 compatibility - see #4558

      • peerDependencies still cannot be updated until 3.0 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 #4558 (comment)
    • CartesianGrid: add support for ry prop to curve the corner of the grid background - progress on #3062

    Fix

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

    Typescript

    • JSDoc comments will now be preserved in TypeScript definitions by @ mxdvl in #5071

    New Contributors

    Full Changelog: v2.12.7...v2.13.0

  • 2.13.0-alpha.5 - 2024-09-05

    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 #4674 fixes #4671
    • Tooltip: Tooltip now renders correctly when data is set on the graphical item rather than the higher level chart by @ HHongSeungWoo in #4718 fixes #4717
    • Pie: fix duplicate key issue when "key" exists in chart data (try not use "key" as a data point) by @ ckifer in #4958 fixes #4858

    TypeScript

    Full Changelog: v2.13.0-alpha.4...v2.13.0-alpha.5

  • 2.13.0-alpha.4 - 2024-06-02

    What's Changed

    Additional React 19 fixes - please keep adding reports to #4558, thanks!

    Fix

    • ReferenceLine: Re-add ReferenceLine types which caused a regression in alpha.0 by @ zackliscio in #4610
    • Fix stacked charts and other defaultProp issues in React 19 by @ ckifer in #4618

    New Contributors

    Full Changelog: v2.13.0-alpha.3...v2.13.0-alpha.4

  • 2.13.0-alpha.3 - 2024-05-28

    What's Changed

    More React 19 specific fixes. If you are using R19, you must use overrides/resolutions to match your react-is version with your react version

    Fix

    • v2.13.0-alpha.2: fix: remove isElement check on children in responsivecontainer by @ ckifer in #4587
    • v2.13.0-alpha.3: fix: legend defaultProps usage for R19 by @ ckifer in #4589

    Full Changelog: v2.13.0-alpha.1...v2.13.0-alpha.3

  • 2.13.0-alpha.2 - 2024-05-26
  • 2.13.0-alpha.1 - 2024-05-24

    What's Changed

    v2.13.0-alpha.0 contains some fixes for React 19 support
    v2.13.0-alpha.1 contains what seems to be the rest of them

    Fix

    Please test this as much as possible using React 16.8 - 19! thank you!

    Full Changelog: v2.12.7...v2.13.0-alpha.1

  • 2.13.0-alpha.0 - 2024-05-24
  • 2.12.7 - 2024-05-08

    Whats changed

    Fix

    • Area: re-add calculated area points to the areaDot callback props when it is a function. This was accidentally removed in v2.3. Fixes #4480
    • Brush: guard against undefined property access error when an ariaLabel is not specified. Follow up from #2093 (comment)

    Full Changelog: v2.12.6...v2.12.7

  • 2.12.6 - 2024-04-21

    What's Changed

    Fix

    • Tooltip: fix glitch where Tooltip always rendered in the top left even if animation was disabled by @ HHongSeungWoo in #4425 fixes #4424

    Chore

    • CI/Build fix: Added proper .js suffixes to main module and jsnext:main paths in package.json by @ dobosalparbc in #4431 fixes #2858

    Full Changelog: v2.12.5...v2.12.6

  • 2.12.5 - 2024-04-12
  • 2.12.4 - 2024-04-04
  • 2.12.3 - 2024-03-15
  • 2.12.2 - 2024-03-01
  • 2.12.1 - 2024-02-20
  • 2.12.0 - 2024-02-09
  • 2.11.0 - 2024-01-27
  • 2.10.4 - 2024-01-09
  • 2.10.3 - 2023-12-01
  • 2.10.2 - 2023-11-29
  • 2.10.1 - 2023-11-19
  • 2.10.0 - 2023-11-19
  • 2.9.3 - 2023-11-06
  • 2.9.2 - 2023-11-01
  • 2.9.1 - 2023-10-30
  • 2.9.0 - 2023-10-15
  • 2.8.0 - 2023-08-25
  • 2.7.3 - 2023-08-08
  • 2.7.2 - 2023-06-22
  • 2.7.1 - 2023-06-15
  • 2.7.0 - 2023-06-15
  • 2.7.0-alpha.0 - 2023-05-26
  • 2.6.2 - 2023-05-10
  • 2.6.1 - 2023-05-10
  • 2.6.0 - 2023-05-08
  • 2.5.0 - 2023-03-15
  • 2.4.3 - 2023-02-16
  • 2.4.2 - 2023-02-15
  • 2.4.1 - 2023-02-10
  • 2.4.0 - 2023-02-09
  • 2.3.2 - 2023-01-12
from recharts GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade recharts from 2.3.2 to 2.13.3.

See this package in npm:
recharts

See this project in Snyk:
https://app.snyk.io/org/krishguptadev/project/4b6a3be2-3c33-41ee-a670-8c88a094faeb?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's great having you contribute to this project

Welcome to the community 🤓

If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord chat and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

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.

2 participants