chore(deps): bump @rjsf/utils from 5.24.13 to 6.0.2 #2446
Conversation
Bumps [@rjsf/utils](https://github.com/rjsf-team/react-jsonschema-form) from 5.24.13 to 6.0.2. - [Release notes](https://github.com/rjsf-team/react-jsonschema-form/releases) - [Changelog](https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md) - [Commits](rjsf-team/react-jsonschema-form@5.24.13...6.0.2) --- updated-dependencies: - dependency-name: "@rjsf/utils" dependency-version: 6.0.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
AssigneesThe following users could not be added as assignees: Please fix the above issues or remove invalid values from |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| "@metamask/sdk": "^0.33.1", | ||
| "@rjsf/core": "^5.24.12", | ||
| "@rjsf/utils": "^5.24.13", | ||
| "@rjsf/utils": "^6.0.2", |
There was a problem hiding this comment.
Bug: RJSF Upgrade Breaks Peer Dependencies
Upgrading @rjsf/utils to 6.0.2 creates a peer dependency conflict. Both @rjsf/core (v5.24.12) and @rjsf/validator-ajv8 (v5.24.12) explicitly require @rjsf/utils version ^5.24.x, but this change installs version 6.0.2. This major version mismatch will cause npm peer dependency warnings or errors and may result in runtime incompatibilities since the packages expect different API versions.
Bumps @rjsf/utils from 5.24.13 to 6.0.2.
Release notes
Sourced from
@rjsf/utils's releases.... (truncated)
Changelog
Sourced from
@rjsf/utils's changelog.... (truncated)
Commits
cdf57d3- Added xl stylec7c75c3- Updated snapshotsbc315cc- Made it responsivee5b301e- Fixed rjsf-team/react-jsonschema-form#483814fd2e3Releasing 6.0.2f1640b5Feature: expanded FallbackField for object and array (#4857)bdc063bFix: Reworked the additional properties remove code (#4852)fd3024dChore: Update fluent packages and add Node 24 (#4851)a3870e7Chore update form snapshots test to use@testing-library/react(#4848)d7f6e15Chore update object snapshots test to use@testing-library/react(#4847)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Upgrade @rjsf/utils to 6.0.2 with updated Node/React requirements and lockfile changes.
@rjsf/utilsfrom^5.24.13to^6.0.2inpackage.json.@rjsf/[email protected]now requiresnode >=20andreact >=18.fast-uri@^3.1.0and bumpsreact-isto^18.3.1.package-lock.jsonto reflect new versions and metadata (e.g.,[email protected]).Written by Cursor Bugbot for commit 5b06b3d. This will update automatically on new commits. Configure here.