Bump @mantine/hooks from 9.4.0 to 9.4.1 in /client#1153
Conversation
Bumps [@mantine/hooks](https://github.com/mantinedev/mantine/tree/HEAD/packages/@mantine/hooks) from 9.4.0 to 9.4.1. - [Release notes](https://github.com/mantinedev/mantine/releases) - [Changelog](https://github.com/mantinedev/mantine/blob/master/CHANGELOG.md) - [Commits](https://github.com/mantinedev/mantine/commits/9.4.1/packages/@mantine/hooks) --- updated-dependencies: - dependency-name: "@mantine/hooks" dependency-version: 9.4.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Claudia-Anthropica
left a comment
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@dependabot[bot] This bump currently mixes @mantine/hooks 9.4.1 with the rest of Mantine at 9.4.0, but Mantine packages declare exact same-version peers. Please update the Mantine suite together; CI is also red right now because the new lock entry is still inside pnpm's minimum-release-age window.
| "@mantine/dropzone": "9.4.0", | ||
| "@mantine/form": "9.4.0", | ||
| "@mantine/hooks": "9.4.0", | ||
| "@mantine/hooks": "9.4.1", |
There was a problem hiding this comment.
@dependabot[bot] [medium] This bumps only @mantine/hooks, while @mantine/core, @mantine/notifications, @mantine/tiptap, and the other Mantine packages remain on 9.4.0. Mantine publishes exact same-version peers (@mantine/core@9.4.1 expects @mantine/hooks@9.4.1), so update the whole Mantine suite to 9.4.1 together instead of resolving a mixed set.
🤖 Prompt for AI agents
In client/package.json, @mantine/hooks is updated to 9.4.1 while the rest of the @mantine/* suite stays at 9.4.0. Fix this by updating all direct Mantine dependencies in client/package.json to 9.4.1 and regenerating client/pnpm-lock.yaml with pnpm.
1 participant
Bumps @mantine/hooks from 9.4.0 to 9.4.1.
Release notes
Sourced from @mantine/hooks's releases.
Commits
d709e0b[release] Version: 9.4.14f3d7d0[@mantine/hooks] Fix use-set and use-map hooks using stale values when used w...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 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)