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 @@ -49,7 +49,7 @@
"@mantine/dropzone": "9.4.0",
"@mantine/form": "9.4.0",
"@mantine/hooks": "9.4.0",
"@mantine/notifications": "9.4.0",
"@mantine/notifications": "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 package set with unsatisfied peers: @mantine/notifications@9.4.1 requires @mantine/core and @mantine/hooks 9.4.1, but package.json still pins both at 9.4.0. Bump the Mantine packages together and refresh the lockfile so pnpm installs a consistent graph.

🤖 Prompt for AI agents

In client/package.json, @mantine/notifications is bumped to 9.4.1 while the rest of the Mantine packages stay on 9.4.0, leaving exact peer dependencies unsatisfied. Update the direct @mantine/* dependencies that are part of the 9.4.1 release to matching 9.4.1 versions and regenerate client/pnpm-lock.yaml with pnpm so the peer graph is consistent. Keep the change scoped to the Mantine package set.

"@mantine/tiptap": "9.4.0",
"@phosphor-icons/react": "2.1.10",
"@tiptap/core": "3.27.1",
Expand Down
Loading
Loading