Bump @mantine/dates from 9.2.0 to 9.2.1 in /client#1083
Conversation
Bumps [@mantine/dates](https://github.com/mantinedev/mantine/tree/HEAD/packages/@mantine/dates) from 9.2.0 to 9.2.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.2.1/packages/@mantine/dates) --- updated-dependencies: - dependency-name: "@mantine/dates" dependency-version: 9.2.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 Routine @mantine/dates 9.2.1 patch bump. Two things before this can merge: run-tests / build is red because the client SBOM wasn't regenerated after the lockfile change, and bumping dates on its own leaves an unmet peer dep since Mantine pins all its packages to the exact same version. Easiest path is to bump every @mantine/* to 9.2.1 together and refresh the SBOM — details inline.
| '@mantine/dates': | ||
| specifier: 9.2.0 | ||
| version: 9.2.0(@mantine/core@9.2.0(@mantine/hooks@9.2.0(react@19.2.6))(@types/react@19.2.15)(react-dom@19.2.6(react@19.2.6))(react@19.2.6))(@mantine/hooks@9.2.0(react@19.2.6))(dayjs@1.11.20)(react-dom@19.2.6(react@19.2.6))(react@19.2.6) | ||
| specifier: 9.2.1 |
There was a problem hiding this comment.
@dependabot [high] run-tests / build is failing here because the client SBOM is stale after the lockfile/package.json change — the CI error is client/sbom/ is stale (pnpm-lock.yaml or package.json changed). Run 'pnpm run sbom:force' and commit the result. Dependabot doesn't regenerate it, so someone needs to run that and commit the updated client/sbom/ before this can go green.
🤖 Prompt for AI agents
The client SBOM is stale after bumping @mantine/dates, causing the run-tests / build check to fail with "client/sbom/ is stale". In the client/ directory run pnpm run sbom:force and commit the regenerated client/sbom/ files (bom.json and .lock-hash).
| "@mantine/carousel": "9.2.0", | ||
| "@mantine/core": "9.2.0", | ||
| "@mantine/dates": "9.2.0", | ||
| "@mantine/dates": "9.2.1", |
There was a problem hiding this comment.
@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/.
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/client/mantine/dates-9.2.1
branch
2 participants
Bumps @mantine/dates from 9.2.0 to 9.2.1.
Release notes
Sourced from @mantine/dates's releases.
Commits
cd3bff3[release] Version: 9.2.1c8ac4e4[refactor] Fix testsa73cdec[core] Update minor dependencies versionDependabot 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)