Skip to content

chore(deps)(deps-dev): bump recharts from 2.15.4 to 3.9.0#1361

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/recharts-3.9.0
Open

chore(deps)(deps-dev): bump recharts from 2.15.4 to 3.9.0#1361
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/recharts-3.9.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 29, 2026

Copy link
Copy Markdown
Contributor

Bumps recharts from 2.15.4 to 3.9.0.

Release notes

Sourced from recharts's releases.

v3.9.0

What's Changed

Animations

3.9 comes with new animations! There are several bug fixes and what's best, all animations are now fully customizable.

See the animations guide on https://recharts.github.io/en-US/guide/animations/

New features other than animations

Bugfixes

Tree-shaking

We now have focused tree-shaking tests that allow us to observe exactly which components end up in the final bundle and why. I have also removed some unnecessary loops and you should see the final bundle size decrease somewhat as a result.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by corkscreewe, a new releaser for recharts since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [recharts](https://github.com/recharts/recharts) from 2.15.4 to 3.9.0.
- [Release notes](https://github.com/recharts/recharts/releases)
- [Changelog](https://github.com/recharts/recharts/blob/main/CHANGELOG.md)
- [Commits](recharts/recharts@v2.15.4...v3.9.0)

---
updated-dependencies:
- dependency-name: recharts
  dependency-version: 3.9.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Jun 29, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, npm, security. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

"react-dom": "^19",
"react-router-dom": "^7",
"recharts": "^2",
"recharts": "^3",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Issue: Recharts v3 needs the multi-axis grid to target an existing axis

What's wrong
The dependency bump changes Recharts’ CartesianGrid axis-selection behavior, but the existing multi-axis chart was not updated. Because both Y axes have non-default ids, the grid can stop rendering after this upgrade, weakening the Operations hardware chart’s readability.

Example
Open the Operations hardware history after two snapshots. With Recharts 2, the Network & RPC chart grid used the first Y axis implicitly. With Recharts 3, there is no default-id Y axis in that chart, so the grid lines can disappear; expected behavior is that the grid remains visible.

Suggested direction
Audit the Recharts v3 migration notes against the existing charts and set the grid’s axis id explicitly for the multi-axis chart so the visual contract survives the dependency bump.

Confidence note
I could not run a local build because pnpm is not installed in this environment; this is based on the official Recharts v3 migration note and the existing chart markup.

For Agents
In packages/node-ui/src/ui/pages/Operations.tsx, update the Network & RPC chart’s CartesianGrid to target an existing axis id, for example yAxisId="left", or add a default axis if that is the intended contract. Add/render a focused check that the multi-axis chart still emits grid lines under Recharts 3.

Major Recharts upgrade is not backed by chart rendering coverage

What's wrong
This changes the charting runtime from Recharts 2 to 3 for user-facing Observability charts, but the diff adds no validation that those charts still render or that the page’s Recharts-specific interactions still work. The existing Operations tests can pass even if the upgraded chart library produces no visible series or breaks legend toggling.

Example
A regression where Recharts v3 renders an empty ResponsiveContainer, drops SVG series paths, or stops Legend onClick from toggling hidden series would still leave the existing Operations e2e tests green because they only require surrounding labels and controls to be visible. A focused Playwright test could seed/mock fetchPerTypeStats with two buckets, open Observability, assert svg.recharts-surface and at least one rendered bar/area path are visible, then click a legend item and assert that series is hidden/dimmed.

Suggested direction
Add or extend an Operations UI/e2e test that forces chart data to be present and verifies the user-visible chart output and the existing legend interaction, rather than only checking that the Observability page shell loads.

For Agents
Look at packages/node-ui/src/ui/pages/Operations.tsx Recharts usages and packages/node-ui/e2e/specs/operations.spec.ts. Add coverage that supplies enough operation and hardware history to render charts, then assert actual chart SVG/series output and legend toggle behavior survive the Recharts v3 upgrade.

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