Update dependency @jsonforms/core to v3.7.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@jsonforms/core (source)	3.6.0 → 3.7.0

---

Release Notes

eclipsesource/jsonforms (@​jsonforms/core)

v3.7.0

Compare Source

What's Changed

[angular] Build against Angular v19 and drop support for v18; Allow v21 RC (#​2501)
[angular] Migrate to standalone components (#​2502)
[angular] Allow Angular 21 release in peer dependencies (#​2505)
[angular-material] fix: array layout renderer error count fix (#​2477)

[core] fix: root $ref resolving (#​2472)
[core] feat(validator): add config to ValidateFunctionContext (#​2483)

[react-material]: Upgrade to MUI ^7 and x-date-picker ^7.28 (#​2476)
[react-material]: Update MUI X date pickers from v7 to v8 (#​2493)

[vue, vue-vuetify] deps: Update to Vuetify ^3.9 and Vue ^3.5 (#​2468)
[vue-vuetify]: update MixedRenderer to add VExpansionPanels (#​2463)
[vue-vuetify] fix how we handle empty values (#​2481)
[vue-vuetify] Enable overriding control-wrapper with custom component (#​2482)
[vue-vuetify] feat: add prepend slot to date/time control renderers (#​2504)

[dev] Ignore pnpm-lock.yaml with prettier and regenerate it unformatted (#​2474)
[dev] bump vite-plugin-static-copy from 1.0.6 to 2.3.2 (#​2499)
[dev] Update various dev dependencies (#​2503)

When migrating from 3.6 to 3.7 no migration should be necessary, except if you still use Angular 18.
See the migration guide when upgrading from an older version.

Contributors

Many thanks to @​kchobantonov, @​martin-trajanovski, @​yaffol for their great contributions!

New Contributors

• @​martin-trajanovski made their first contribution in (#​2477)
• @​yaffol made their first contribution in (#​2504)

Full Changelog: (eclipsesource/jsonforms@v3.6.0...v3.7.0)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "after 10pm every weekday,every weekend,before 5am every weekday"
• Automerge
  • "after 10pm and before 5am on every weekday,every weekend"

🚦 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 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]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @jsonforms/material-renderers@3.6.0
npm ERR! Found: @jsonforms/core@3.7.0
npm ERR! node_modules/@jsonforms/core
npm ERR!   @jsonforms/core@"3.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @jsonforms/core@"3.6.0" from @jsonforms/material-renderers@3.6.0
npm ERR! node_modules/@jsonforms/material-renderers
npm ERR!   @jsonforms/material-renderers@"3.6.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @jsonforms/core@3.6.0
npm ERR! node_modules/@jsonforms/core
npm ERR!   peer @jsonforms/core@"3.6.0" from @jsonforms/material-renderers@3.6.0
npm ERR!   node_modules/@jsonforms/material-renderers
npm ERR!     @jsonforms/material-renderers@"3.6.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-04-08T18_41_11_957Z-debug-0.log