Skip to content
Closed
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 @@ -45,7 +45,7 @@
"dependencies": {
"@mantine/carousel": "9.2.0",
"@mantine/core": "9.2.0",
"@mantine/dates": "9.2.0",
"@mantine/dates": "9.2.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.

@dependabot [medium] Bumping only @mantine/dates to 9.2.1 leaves an unmet peer dependency — 9.2.1 declares exact peers @mantine/core: 9.2.1 and @mantine/hooks: 9.2.1, but those (along with carousel, dropzone, form, notifications and tiptap) are still pinned at 9.2.0. The lockfile even shows dates@9.2.1 resolved against core@9.2.0/hooks@9.2.0. pnpm doesn't hard-fail since strict-peer isn't enabled, but Mantine ships all @mantine/* packages in lockstep, so they should be bumped to 9.2.1 together rather than one at a time.

🤖 Prompt for AI agents

In client/package.json, @mantine/dates was bumped to 9.2.1 while the other @mantine/* packages (core, hooks, carousel, dropzone, form, notifications, tiptap) remain 9.2.0, violating @mantine/dates@9.2.1's exact peer deps on @mantine/core and @mantine/hooks 9.2.1. Bump all @mantine/* packages to 9.2.1, then run pnpm install and pnpm run sbom:force in client/ and commit the updated pnpm-lock.yaml and client/sbom/.

"@mantine/dropzone": "9.2.0",
"@mantine/form": "9.2.0",
"@mantine/hooks": "9.2.0",
Expand Down
14 changes: 7 additions & 7 deletions client/pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading