build(deps): bump @mantine/hooks from 9.3.1 to 9.3.2 in /webui#286
Conversation
Bumps [@mantine/hooks](https://github.com/mantinedev/mantine/tree/HEAD/packages/@mantine/hooks) from 9.3.1 to 9.3.2. - [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.3.2/packages/@mantine/hooks) --- updated-dependencies: - dependency-name: "@mantine/hooks" dependency-version: 9.3.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Bug Scan Summary
Date: 2026-06-21
Commits inspected: e045e4b..2e96745 (PR #286 — @mantine/hooks 9.3.1 → 9.3.2)
Result: No critical bugs found.
Investigation
- Diff scope:
webui/package.jsonandpackage-lock.jsononly — patch bump of a direct dev dependency. - Upstream changes (9.3.1→9.3.2):
@mantine/hookschanges are limited touse-splitterimprovements and tests. No auth, data-persistence, or crash-class regressions in the release notes. - Call-path trace: No
webui/srcimports of@mantine/hooks,@mantine/core, or@mantine/dates. Mantine appears only invite.config.tschunk config and a Tailwind comment — it is not on any production UI code path, so theuse-splitterchange has no reachable trigger in this app. - Validation:
npx vitest run— 154/154 passed;npm run build— succeeded with no mantine chunk in the output bundle.
Notes (below critical bar)
- Before follow-up PR #290 landed,
npm lsreported peer-version warnings (@mantine/core@9.1.1expectinghooks@9.1.1while top-level resolvedhooks@9.3.2). That mismatch is now resolved onmastervia #290. Even pre-fix, it had no production trigger because Mantine is unused in source. - Mantine packages remain listed in
package.jsonbut unused — housekeeping opportunity, not a correctness bug.
Deduplication
- Open PRs:
mantine,mantine hooks— #288 (@mantine/datesbump, separate dep) - Recently merged: #286 (this PR), #290 (
@mantine/core9.3.2 alignment) - Open issues: none for mantine version mismatch
Sent by Cursor Automation: Torrentarr - Find critical bugs
There was a problem hiding this comment.
PR Validation (Cursor Automation)
Recommendation: Merge
Primary reason: Clean dependency-only bump; local merge with current master had no conflicts and all validation gates passed. Note: GitHub already shows this PR as merged into master.
Gates
| Gate | Status | Notes |
|---|---|---|
| Merge conflicts | Pass | Clean local merge of PR #286 with origin/master; conflicts: none. |
dotnet build |
Pass | dotnet build -c Release succeeded with 0 errors; warnings only and unrelated to this frontend dependency bump. |
dotnet test (non-live) |
Pass | 759 passed, 0 failed, 0 skipped across Core, Host, and Infrastructure test projects. |
vitest |
Pass | 16 test files passed; 154 tests passed. |
Validation
| Axis | Score | Notes |
|---|---|---|
| Purpose | Pass | Routine Dependabot patch bump of @mantine/hooks from 9.3.1 to 9.3.2; justified dependency maintenance. |
| Correctness | Pass | Minimal webui/package.json and webui/package-lock.json update; npm ci accepted the lockfile and frontend tests passed. |
| Tests | Pass | No source behavior changed; full non-live .NET suite and Vitest suite both passed. |
| Hygiene | Pass | Scope limited to 2 frontend dependency files; no unrelated files or generated junk. |
| Overlap | Pass | No open @mantine/hooks duplicate found; PR is already represented on current master by its merge commit. |
Why
This PR only updates the Mantine hooks dependency metadata and lockfile entry. The change merged cleanly with latest master, installed successfully with npm ci, and did not regress the backend or frontend test suites. The required docs/parity/contract-baseline.md was reviewed; docs/audits/pr-triage-*.md was not present in the checked-out merged tree, so no audit-specific duplicate winner applied.
Overlap
None.
Commands run
git fetch origin mastergit fetch origin dependabot/npm_and_yarn/webui/mantine/hooks-9.3.2(remote ref unavailable), thengit fetch origin pull/286/head:refs/remotes/origin/pr/286git checkout -B pr-validate origin/pr/286git merge origin/masterdotnet restoredotnet build -c Releasedotnet test -c Release --no-build --filter "Category!=Live"cd webui && npm ci && npx vitest rungh pr listoverlap checks formantine hooks/@mantine/hooks
Sent by Cursor Automation: Torrentarr PR validation triage


Bumps @mantine/hooks from 9.3.1 to 9.3.2.
Release notes
Sourced from @mantine/hooks's releases.
Commits
73a04e0[release] Version: 9.3.2bb00207[@mantine/core] Splitter: Add option to reset on double click (#8957)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)