fix(deps): update rjsf monorepo to v6 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@rjsf/core	^5.24.3 -> ^6.0.0
@rjsf/mui	^5.24.3 -> ^6.0.0
@rjsf/utils	^5.24.3 -> ^6.0.0
@rjsf/validator-ajv8	^5.24.3 -> ^6.0.0

---

Additional Changes Required

MUI v7 Upgrade (Required Peer Dependency)

@rjsf/mui@^6.0.0 requires @mui/material@^7.3.5 and @mui/icons-material@^7.3.5 as peer dependencies. This PR includes:

• Upgraded @mui/material: ^6.4.4 → ^7.3.5
• Upgraded @mui/icons-material: ^6.4.4 → ^7.3.5
• Migrated Grid2 → Grid: In MUI v7, Grid2 was merged into Grid. Updated NotFound.jsx accordingly.

Build Infrastructure Fixes

• Fixed config.js handling: Removed script tag from index.html and added Vite define option to provide window.config at build time. This preserves Caddy's dynamic config generation in production while allowing builds to complete successfully.

---

Release Notes

rjsf-team/react-jsonschema-form (@​rjsf/core)

v6.0.1

Compare Source

Dev / docs / playground

• Updated peer dependencies for packages to 6.x

v6.0.0

Compare Source

@​rjsf/antd

• Updated the README.md to show the theme snapshot with the latest theme UI from the playground, making it a link to the theme

@​rjsf/chakra-ui

• Updated the README.md to show the theme snapshot with the latest theme UI from the playground, making it a link to the theme

@​rjsf/core

• Updated SchemaField to add a new optional property childFieldPathId to the FieldComponent render to prevent duplicate ids, fixing (#​4819)[#​4819]
  • Also updated ObjectField and ArrayField to make children use the childFieldPathId if present, falling back to the fieldPathId if not

Dev / docs / playground

• Updated the libraries to the latest ones that aren't problematic
  Updated the playground to modernize the UI using MUI components
• Updated the documentation to switch to using an animated gif based on the latest modernized playground UI
• Updated the README.md in all themes to show the theme snapshot with the latest theme UI from the playground, making it a link to the theme

---

Testing

• ✅ npm install completes without dependency conflicts
• ✅ npm run build completes successfully
• ✅ All MUI v7 breaking changes addressed
• ✅ Production config system remains intact

---

Configuration

📅 Schedule: Branch creation - "before 6am every weekday" in timezone America/Vancouver, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.
API available
Frontend available

Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

[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: frontend/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: frontend@0.0.0
npm error Found: @mui/icons-material@6.5.0
npm error node_modules/@mui/icons-material
npm error   @mui/icons-material@"^6.4.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @mui/icons-material@"^7.0.0" from @rjsf/mui@6.0.1
npm error node_modules/@rjsf/mui
npm error   @rjsf/mui@"^6.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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/2025-11-03T10_51_46_496Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-03T10_51_46_496Z-debug-0.log

[DerekRoberts]

Additional Changes in Latest Commit

This commit addresses the dependency conflicts and build issues that arose when upgrading to RJSF v6:

MUI v7 Upgrade (Required)

• Why: @rjsf/mui@^6.0.0 requires @mui/material@^7.3.5 and @mui/icons-material@^7.3.5 as peer dependencies
• Changes:
  • Upgraded @mui/material from ^6.4.4 to ^7.3.5
  • Upgraded @mui/icons-material from ^6.4.4 to ^7.3.5
• Breaking Change: Migrated Grid2 → Grid in NotFound.jsx (MUI v7 merged Grid2 into Grid)

Build Infrastructure Fixes

• Config.js Handling:
  • Removed <script src="/config.js"> from index.html
  • Added Vite define option to provide window.config at build time
  • This preserves Caddy's dynamic config generation in production while allowing builds to complete

Results

• ✅ npm install works without dependency conflicts
• ✅ npm run build completes successfully
• ✅ All breaking changes addressed
• ✅ Production deployment compatibility maintained

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.