build(deps): bump @mantine/dates from 9.3.1 to 9.3.2 in /webui#288
Conversation
There was a problem hiding this comment.
Bug Scan Summary
Date: 2026-06-21
Commits inspected: 34c8e02..360f74c (1 commit — @mantine/dates 9.3.1 → 9.3.2)
Result: No critical bugs found.
Investigation
- Diff scope:
webui/package.jsonandwebui/package-lock.jsononly — patch-level dependency bump. - Usage trace:
@mantine/datesis not imported anywhere underwebui/src/. The only Mantine references in the repo arevite.config.tschunk-splitting hints andpackage.jsondeclarations. The production bundle contains nomantinechunk, confirming zero runtime surface. - Mantine 9.3.2 changelog: UI fixes only (TimePicker max-value typing, DatePicker range preset times). No security advisories or breaking changes.
- Validation:
npx vitest run— 154/154 passed;npm run build— succeeded.
Notable (below critical bar)
@mantine/dates@9.3.2declares peer deps on@mantine/core@9.3.2and@mantine/hooks@9.3.2. On this PR branch those peers were still at 9.1.1/9.3.1, but master has since merged #286 (hooks → 9.3.2) and #290 (core → 9.3.2). Merging this PR completes alignment. Because the package is unused, the transient mismatch has no production trigger.@mantine/core,@mantine/hooks,@mantine/dates, anddayjsall appear to be unused direct dependencies — housekeeping opportunity, not a correctness issue.
Deduplication check
- Open PRs: searched
mantine— only this PR (#288) and unrelated #285. - Recently merged PRs: #290 (core → 9.3.2), #286 (hooks → 9.3.2) — complementary alignment, not competing fixes.
- Open issues: no mantine-related issues found.
- Conclusion: No existing fix needed; safe to merge from a critical-bug perspective.
Sent by Cursor Automation: Torrentarr - Find critical bugs
Bumps [@mantine/dates](https://github.com/mantinedev/mantine/tree/HEAD/packages/@mantine/dates) 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/dates) --- updated-dependencies: - dependency-name: "@mantine/dates" dependency-version: 9.3.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
360f74c to
c0a49ab
Compare
There was a problem hiding this comment.
PR Validation (Cursor Automation)
Recommendation: Merge
Primary reason: Narrow frontend dependency bump; merge conflicts were locally resolvable against current master, and all build/test gates passed.
Gates
| Gate | Status | Notes |
|---|---|---|
| Merge conflicts | Pass | git merge origin/master conflicted only in webui/package.json and webui/package-lock.json; resolved locally by keeping Mantine packages aligned at ^9.3.2. No conflict markers remained. |
dotnet build |
Pass | dotnet build -c Release succeeded with existing warnings unrelated to this PR. |
dotnet test (non-live) |
Pass | dotnet test -c Release --no-build --filter "Category!=Live": 759 passed, 0 failed, 0 skipped. |
vitest |
Pass | npm ci succeeded; npx vitest run: 16 files passed, 154 tests passed. |
Validation
| Axis | Score | Notes |
|---|---|---|
| Purpose | Pass | Dependabot patch update for @mantine/dates adds routine dependency maintenance value. |
| Correctness | Pass | Scope is package metadata only; local merge resolution preserves master updates and aligns @mantine/core, @mantine/dates, and @mantine/hooks at 9.3.2 as required by Mantine peer relationships. |
| Tests | Pass | No source behavior changed; full backend non-live and frontend Vitest suites passed. |
| Hygiene | Pass | Two-file dependency update; no SDK junk, broad refactor, or unrelated source changes. |
| Overlap | Pass | No other open PR found for the same mantine dates theme; known duplicate-winner themes do not apply. Required docs/audits/pr-triage-*.md files were not present on fetched origin/master, so no audit file could be read. |
Why
This PR updates only the frontend package manifest and lockfile for @mantine/dates. Current master has adjacent Mantine/package metadata changes, causing a simple package conflict; resolving the local validation merge by retaining master package updates and applying the PR's @mantine/dates bump produced a consistent install and passing test run.
Overlap
None.
Commands run
git fetch origin master; git fetch origin dependabot/npm_and_yarn/webui/mantine/dates-9.3.2; git checkout -B pr-validate origin/dependabot/npm_and_yarn/webui/mantine/dates-9.3.2; git merge origin/master; local conflict resolution plus git add webui/package.json webui/package-lock.json; git diff --name-status origin/master...origin/dependabot/npm_and_yarn/webui/mantine/dates-9.3.2; gh pr list --repo Feramance/Torrentarr --state open --search "mantine dates"; temporary .NET SDK install under /tmp/dotnet because dotnet was absent from PATH; dotnet restore; dotnet build -c Release; dotnet test -c Release --no-build --filter "Category!=Live"; cd webui && npm ci; cd webui && npx vitest run.
Sent by Cursor Automation: Torrentarr PR validation triage


Bumps @mantine/dates from 9.3.1 to 9.3.2.
Release notes
Sourced from @mantine/dates's releases.
Commits
73a04e0[release] Version: 9.3.2ea9a722[@mantine/dates] TimePicker: Allow entering 01-09 hours over a selected 00 va...b431b6a[@mantine/dates] DatePickerPicker: Fix range presets ignoring specified time ...5c5eb3d[@mantine/dates] TimePicker: AddcloseDropdownOnPresetSelectprop support4a41832[@mantine/dates] TimePicker: Fix input getting stuck at maximum value when ty...