fix(deps): update dependency react-error-boundary to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-error-boundary (source)	^4.0.13 → ^6.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

bvaughn/react-error-boundary (react-error-boundary)

v6.0.1

Compare Source

v6.0.0

Compare Source

Module is ESM-only in order to better work with modern tooling.

v5.0.0

Compare Source

Update withErrorBoundary types to be compatible with the latest forwardRef types

For more background see PR #​211

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/New_York, 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.

[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: @openedx/frontend-plugin-framework@1.8.0
npm error Found: react-error-boundary@6.1.4
npm error node_modules/react-error-boundary
npm error   react-error-boundary@"^6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react-error-boundary@"^4.0.11" from @openedx/frontend-plugin-framework@1.8.0
npm error node_modules/@openedx/frontend-plugin-framework
npm error   @openedx/frontend-plugin-framework@"^1.8.0" from the root project
npm error   @openedx/frontend-plugin-framework@"^1.7.0" from @edx/frontend-component-footer@14.9.5
npm error   node_modules/@edx/frontend-component-footer
npm error     @edx/frontend-component-footer@"^14.9.0" from the root project
npm error   1 more (@edx/frontend-component-header)
npm error
npm error Conflicting peer dependency: react-error-boundary@4.1.2
npm error node_modules/react-error-boundary
npm error   peer react-error-boundary@"^4.0.11" from @openedx/frontend-plugin-framework@1.8.0
npm error   node_modules/@openedx/frontend-plugin-framework
npm error     @openedx/frontend-plugin-framework@"^1.8.0" from the root project
npm error     @openedx/frontend-plugin-framework@"^1.7.0" from @edx/frontend-component-footer@14.9.5
npm error     node_modules/@edx/frontend-component-footer
npm error       @edx/frontend-component-footer@"^14.9.0" from the root project
npm error     1 more (@edx/frontend-component-header)
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-08-31T00_34_40_764Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-31T00_34_40_764Z-debug-0.log