Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion client/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@
"@mantine/carousel": "9.4.0",
"@mantine/core": "9.4.0",
"@mantine/dates": "9.4.0",
"@mantine/dropzone": "9.4.0",
"@mantine/dropzone": "9.4.1",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@app/dependabot [medium] This leaves the Mantine suite in an invalid peer state: @mantine/dropzone@9.4.1 requires @mantine/core and @mantine/hooks 9.4.1, while the rest of the Mantine packages are still on 9.4.0 with exact peers back to core/hooks@9.4.0. Bump the Mantine packages as a set and regenerate the lockfile; CI also needs a green rerun after pnpm accepts 9.4.1 under the release-age policy.

🤖 Prompt for AI agents

In client/package.json, @mantine/dropzone is 9.4.1 while the other @mantine/* dependencies remain 9.4.0, creating exact peer mismatches in client/pnpm-lock.yaml. Update the Mantine dependency set in client/package.json to 9.4.1, regenerate client/pnpm-lock.yaml with pnpm, and rerun CI once the minimumReleaseAge policy accepts 9.4.1.

"@mantine/form": "9.4.0",
"@mantine/hooks": "9.4.0",
"@mantine/notifications": "9.4.0",
Expand Down
Loading
Loading