Skip to content

Update Routine updates - #252

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/routine-updates
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/routine-updates

Conversation

@renovate

@renovate renovate Bot commented Aug 3, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@convex-dev/batch-worker 0.3.3 → 0.3.6 age confidence dependencies patch
@convex-dev/migrations 0.3.6 → 0.3.7 age confidence devDependencies patch
@eslint/eslintrc 3.3.6 → 3.3.7 age confidence devDependencies patch
@fast-check/vitest (source) 0.4.1 → 0.5.0 age confidence devDependencies minor
@mantine/core (source) 9.5.0 → 9.7.2 age confidence devDependencies minor
@mantine/emotion (source) 9.5.0 → 9.7.2 age confidence devDependencies minor
@mantine/hooks (source) 9.5.0 → 9.7.2 age confidence devDependencies minor
@mantine/notifications (source) 9.5.0 → 9.7.2 age confidence devDependencies minor
@tabler/icons-react (source) 3.46.0 → 3.49.0 age confidence devDependencies minor
@types/node (source) 22.20.1 → 22.20.5 age confidence devDependencies patch
@types/react (source) 19.2.17 → 19.3.0 age confidence devDependencies minor
@types/react-dom (source) 19.2.3 → 19.3.0 age confidence devDependencies minor
@typescript-eslint/eslint-plugin (source) 8.65.0 → 8.71.2 age confidence devDependencies minor
@typescript-eslint/parser (source) 8.65.0 → 8.71.2 age confidence devDependencies minor
@vitejs/plugin-react (source) 6.0.4 → 6.1.2 age confidence devDependencies minor
@vitest/coverage-v8 (source) 4.1.10 → 4.1.11 age confidence devDependencies patch 4.1.12
@xyflow/react (source) 12.11.2 → 12.12.0 age confidence devDependencies minor
actions/checkout (changelog) de0fac2 → d23441a action digest
actions/checkout (changelog) 93cb6ef → fbc6f39 action digest
eslint-plugin-react-refresh 0.5.3 → 0.5.7 age confidence devDependencies patch
globals 17.8.0 → 17.13.0 age confidence devDependencies minor
pkg-pr-new (source) 0.0.82 → 0.0.91 age confidence devDependencies patch
prettier (source) 3.9.6 → 3.9.10 age confidence devDependencies patch
react (source) 19.2.8 → 19.3.0 age confidence devDependencies minor 19.3.1
react-dom (source) 19.2.8 → 19.3.0 age confidence devDependencies minor 19.3.1
typescript-eslint (source) 8.65.0 → 8.71.2 age confidence devDependencies minor
vite (source) 8.1.5 → 8.3.4 age confidence devDependencies minor
zizmorcore/zizmor-action v0.6.0 → v0.6.4 age confidence action patch v0.7.1 (+1)

Release Notes

get-convex/batch-worker (@​convex-dev/batch-worker)

v0.3.6

Compare Source

  • Updates the /test entrypoint for compatibility with convex-test's new
    defineTestApp capability.

v0.3.5

Compare Source

  • Improve the test entrypoint generics

v0.3.4

Compare Source

  • Remove the unnecessary react peer dependency and entrypoint
get-convex/migrations (@​convex-dev/migrations)

v0.3.7

Compare Source

  • Updates the /test entrypoint for compatibility with convex-test's new
    defineTestApp capability.
eslint/eslintrc (@​eslint/eslintrc)

v3.3.7

Compare Source

Bug Fixes
dubzzz/fast-check (@​fast-check/vitest)

v0.5.0

Support for plugins and for Vitest v5
[Code][Diff]

Features

  • (PR#7219) Support plugin API of fast-check
  • (PR#7244) Support Vitest 5

mantinedev/mantine (@​mantine/core)

v9.7.2

Compare Source

  • [@mantine/core] PinInput: Fix readOnly not preventing value changes on Delete, Backspace and paste (#​9258)
  • [@mantine/core] Divider: Add aria-orientation (#​9259)
  • [@mantine/core] Tooltip: Fix disabled tooltip setting aria-describedby on its target (#​9261)
  • [@mantine/core] Transition: Fix frames and callbacks running after unmount during the first frame (#​9263)
  • [@mantine/hooks] use-scroll-into-view: Reset start time on cancel (#​9265)
  • [@mantine/core] Fix Backspace removing the last value when readOnly is set in MultiSelect and TreeSelect components (#​9267)
  • [@mantine/schedule] ResourcesDayView: Fix sticky resource labels covering the time labels row (#​9268)
  • [@mantine/hooks] use-debounced-callback: Avoid repeating completed leading calls (#​9269)
  • [@mantine/schedule] MobileMonthView: Fix multi-day event time display on start, middle and end days (#​9272)
  • [@mantine/form] Add UseContextForm type export (#​9275)
  • [@mantine/form] Fix potential global prototype position
  • [@mantine/tiptap] Add option to handle images pasted with other rich text elements in the image extension (#​9270)

v9.7.1

Compare Source

  • [@mantine/schedule] Fix startScrollTime scroll position (#​9255)
  • [@mantine/core] RollingNumber: Fix sub-pixel digit misalignment at fractional zoom levels (#​9251)
  • [@mantine/core] Tree: Add aria-expanded to tree items with children (#​9247)
  • [@mantine/core] SegmentedControl: Do not call Math.random during render (#​9245)
  • [@mantine/core] Popover: Add capture prop to control events capturing phase (#​9243)
  • [@mantine/form] Fix clearing state of unrelated fields (#​9242)
  • [@mantine/core] AngleSlider: Set aria-disabled on thumb when disabled (#​9238)
  • [@mantine/core] Combobox: Set aria-disabled on disabled Combobox.Option (#​9236)
  • [@mantine/form] Fix reorderListItem moving errors of items whose index shares a prefix with the reordered index (#​9235)
  • [@mantine/schedule] MonthView: Fix quadratic row assignment for weeks with many events (#​9232)
  • [@mantine/hooks] use-pagination: Fix single page being replaced with dots on the right side (#​9229)
  • [@mantine/core] ScrollArea: Fix wheel listener on document blocking compositor scrolling for the whole page (#​9225)
  • [@mantine/dates] DateTimePicker: Fix time not being limited by minDate and maxDate (#​9221)
  • [@mantine/core] Select, MultiSelect, Autocomplete, TagsInput: Fix listbox aria-labelledby referencing a missing label element (#​9219) (#​9220)
  • [@mantine/hooks] use-debounced-state: Fix leading edge firing only once (#​9214)

v9.7.0: 😳

Compare Source

View changelog with demos on mantine.dev website

Support Mantine development

You can now sponsor Mantine development with OpenCollective.
All funds are used to improve Mantine and create new features and components.

@​mantine/mcp-server documentation coverage

@​mantine/mcp-server now exposes 406 documentation
pages instead of 164. Previously only components were indexed – hooks, @​mantine/form,
styling, theming, guides and help.mantine.dev FAQ pages are now included as
well. Changelog pages are deliberately excluded to keep search results focused on current APIs.

Documentation is now retrieved by section rather than by whole page. get_item_doc returns a page
outline (description, import statement and the list of section headings) by default, a single section
with the section argument, or the entire page with full: true. Requesting useForm this way returns
about 1KB instead of 9KB, and the largest pages drop from roughly 89KB to 4KB.

Other improvements:

  • New get_api tool – resolves a symbol such as useForm or useDisclosure to its TypeScript
    signature and exported types without knowing which page documents it
  • Ranked search – search_docs results point at the specific section that matched, so a query like
    "validate a form with zod" resolves to the zod section of the schema validation page
  • Search synonyms – queries now match the search keywords maintained in the documentation, so
    "command palette" finds Spotlight
  • More filters – list_items accepts group, category and package in addition to kind
  • Hook signatures – get_item_props returns the TypeScript signature for hooks, and points at the
    relevant section for pages that document their API in prose

The server was also migrated to the official Model Context Protocol SDK, so the protocol version is
negotiated with the client instead of being pinned.

For setup details, supported tools, and client-specific instructions, see Mantine with LLMs.

Tour component

New Tour component provides interactive step-by-step application onboarding.
It highlights target elements with a spotlight overlay and displays tooltips with navigation controls.
Supports both guided (sequential) and beacon (non-sequential) modes.

Toolbar component

New Toolbar component provides an accessible toolbar container with roving tabindex
keyboard navigation, toggle groups with single/multiple selection, visual grouping, and dividers.
Styling is similar to RichTextEditor toolbar.

Toggle component

New Toggle component is a button that can be toggled between active and inactive states:

JsonViewer component

New JsonViewer component can be used to display complex JSON
structures with expand/collapse, type indicators, copy to clipboard, and other features:

Light Checkbox and Radio variant

Checkbox and Radio components now support variant="light" –
the indicator uses a light background color with a colored icon, similar to the light variant
available in other components like Button:

import { Radio, Checkbox, Stack } from '@mantine/core';

function Demo() {
  return (
    <Stack gap={7}>
      <Checkbox variant="light" label="Light Checkbox" defaultChecked />
      <Checkbox variant="light" label="Light indeterminate Checkbox" indeterminate />
      <Radio variant="light" label="Light Radio" defaultChecked />
    </Stack>
  );
}
RichTextEditor image upload

RichTextEditor now supports image upload with loading states.
Images can be uploaded via toolbar button, drag and drop, or paste.
During upload, a local preview is shown with a loading indicator.

Configuring getUploadImageExtension is enough to enable uploads – onImageUpload and
onImageUploadError props of RichTextEditor are optional overrides for the toolbar control.
onImageUpload can resolve either to a string or to { src, alt, title } (new exported
ImageUploadResult type) to set alternative text on the uploaded image. Several files picked,
dropped or pasted together are inserted in the order they were selected and are undone as one step.

import TipTapImage from '@tiptap/extension-image';
import { useEditor } from '@tiptap/react';
import StarterKit from '@tiptap/starter-kit';
import { getUploadImageExtension, ImageUploadResult, RichTextEditor } from '@mantine/tiptap';

function handleImageUpload(file: File): Promise<ImageUploadResult> {
  return new Promise((resolve) => {
    setTimeout(() => {
      resolve({ src: URL.createObjectURL(file), alt: file.name });
    }, 3000);
  });
}

function Demo() {
  const editor = useEditor({
    shouldRerenderOnTransaction: true,
    extensions: [
      StarterKit,
      getUploadImageExtension(TipTapImage, { onImageUpload: handleImageUpload }),
    ],
    content: '<p>Click the image button in the toolbar, or drag & drop / paste an image into the editor.</p>',
  });

  return (
    <RichTextEditor editor={editor}>
      <RichTextEditor.Toolbar>
        <RichTextEditor.ControlsGroup>
          <RichTextEditor.Bold />
          <RichTextEditor.Italic />
        </RichTextEditor.ControlsGroup>

        <RichTextEditor.ControlsGroup>
          <RichTextEditor.ImageUpload />
        </RichTextEditor.ControlsGroup>
      </RichTextEditor.Toolbar>

      <RichTextEditor.Content />
    </RichTextEditor>
  );
}
Schedule event overlap mode

DayView and WeekView now support eventOverlapMode prop
that controls how events overlapping in time share the horizontal space. The default columns mode
splits the available width evenly between them, which becomes unreadable once a large number of events
overlap. The new cascade mode indents each event and stacks it over the previous one, so every event
keeps a readable width no matter how many of them overlap.

The indent shrinks automatically as the group grows, so the event on top always keeps at least 60% of
the available width. Covered events can still be read and used: rest the pointer on one and it is
raised above the events covering it, which also makes its resize handles reachable. Keyboard users get
the same result by focusing the event with Tab. eventOverlapRaiseDelay prop controls how long the
pointer must rest on an event before it is raised, in milliseconds (600 by default).

import { useState } from 'react';
import { SegmentedControl, Stack } from '@mantine/core';
import { ScheduleEventOverlapMode, WeekView } from '@mantine/schedule';
import { events } from './data';

function Demo() {
  const [mode, setMode] = useState<ScheduleEventOverlapMode>('cascade');

  return (
    <Stack>
      <SegmentedControl
        value={mode}
        onChange={(value) => setMode(value as ScheduleEventOverlapMode)}
        data={[
          { value: 'columns', label: 'columns' },
          { value: 'cascade', label: 'cascade' },
        ]}
      />

      <WeekView
        date={new Date()}
        events={events}
        startTime="08:00:00"
        endTime="14:00:00"
        eventOverlapMode={mode}
      />
    </Stack>
  );
}
Schedule drop validation

All Schedule views can now reject a drag or resize before it is committed,
based on where the event is being dropped rather than on which event is being dragged. Previously
canDragEvent and canResizeEvent only decided whether an event was draggable or resizable at all,
so the only way to prevent a double booking was to accept the drop, notice the conflict in the
handler and not update state – which produced a snap-back with no explanation:

  • preventEventOverlap rejects placements that would make the event overlap another event. Pass a
    function to decide per pair of events: return true to forbid that particular overlap.
  • canDropEvent and canResizeEventTo are called before a drop or resize is committed – return
    false to reject it.
  • canDropExternalEvent does the same for items dragged in from outside the schedule.
  • onEventPlacementRejected reports the rejection with the conflicting events and the reason.

The checks compose: a placement is allowed only when the overlap check passes and the matching
callback returns a value other than false. The overlap check runs first, so onEventPlacementRejected
can report conflicts without your code repeating the work. While the pointer is over an invalid
target the drag ghost and the resizing event get data-invalid, so the rejection is visible before the
pointer is released.

import { useState } from 'react';
import dayjs from 'dayjs';
import { Stack, Text } from '@mantine/core';
import { WeekView, ScheduleEventData } from '@mantine/schedule';

const startOfWeek = dayjs()
  .subtract((dayjs().day() + 6) % 7, 'day')
  .format('YYYY-MM-DD');

const initialEvents: ScheduleEventData[] = [
  {
    id: 1,
    title: 'Standup',
    start: `${startOfWeek} 09:00:00`,
    end: `${startOfWeek} 09:30:00`,
    color: 'blue',
  },
  {
    id: 2,
    title: 'Design review',
    start: `${startOfWeek} 11:00:00`,
    end: `${startOfWeek} 12:00:00`,
    color: 'grape',
  },
  {
    id: 3,
    title: 'Retro',
    start: `${startOfWeek} 14:00:00`,
    end: `${startOfWeek} 15:00:00`,
    color: 'teal',
  },
];

function Demo() {
  const [date, setDate] = useState(dayjs().format('YYYY-MM-DD'));
  const [events, setEvents] = useState(initialEvents);
  const [message, setMessage] = useState<string | null>(null);

  return (
    <Stack>
      <WeekView
        date={date}
        onDateChange={setDate}
        events={events}
        startTime="08:00:00"
        endTime="18:00:00"
        withEventsDragAndDrop
        withEventResize
        eventDragInterval={15}
        preventEventOverlap
        onEventDrop={({ eventId, newStart, newEnd }) => {
          setMessage(null);
          setEvents((prev) =>
            prev.map((event) =>
              event.id === eventId ? { ...event, start: newStart, end: newEnd } : event
            )
          );
        }}
        onEventResize={({ eventId, newStart, newEnd }) => {
          setMessage(null);
          setEvents((prev) =>
            prev.map((event) =>
              event.id === eventId ? { ...event, start: newStart, end: newEnd } : event
            )
          );
        }}
        onEventPlacementRejected={(data) => {
          if (data.action === 'external-drop') {
            return;
          }

          setMessage(
            `${data.event.title} cannot be ${data.action === 'drop' ? 'moved' : 'resized'} there – it would overlap ${data.conflicts
              .map((conflict) => conflict.title)
              .join(', ')}`
          );
        }}
      />

      {message && <Text c="red" size="sm">{message}</Text>}
    </Stack>
  );
}

In resource views the conflict set is scoped to the target
resource, so moving an event onto another resource row is checked against that row rather than the one
it came from:

import { useState } from 'react';
import dayjs from 'dayjs';
import { Stack, Text } from '@mantine/core';
import { ResourcesDayView, ScheduleEventData, ScheduleResourceData } from '@mantine/schedule';

const today = dayjs().format('YYYY-MM-DD');

const resources: ScheduleResourceData[] = [
  { id: 'room-a', label: 'Room A' },
  { id: 'room-b', label: 'Room B' },
  { id: 'room-c', label: 'Room C (large groups only)' },
];

const initialEvents: ScheduleEventData[] = [
  {
    id: 1,
    title: 'Interview (2 people)',
    start: `${today} 09:00:00`,
    end: `${today} 10:00:00`,
    color: 'blue',
    resourceId: 'room-a',
    payload: { attendees: 2 },
  },
  {
    id: 2,
    title: 'All-hands (40 people)',
    start: `${today} 11:00:00`,
    end: `${today} 12:00:00`,
    color: 'grape',
    resourceId: 'room-c',
    payload: { attendees: 40 },
  },
];

function Demo() {
  const [date, setDate] = useState(dayjs().format('YYYY-MM-DD'));
  const [events, setEvents] = useState(initialEvents);
  const [message, setMessage] = useState<string | null>(null);

  return (
    <Stack>
      <ResourcesDayView
        date={date}
        onDateChange={setDate}
        resources={resources}
        events={events}
        startTime="08:00:00"
        endTime="18:00:00"
        withEventsDragAndDrop
        preventEventOverlap
        canDropEvent={({ event, resourceId }) =>
          resourceId !== 'room-c' || (event.payload?.attendees ?? 0) >= 20
        }
        onEventDrop={({ eventId, newStart, newEnd, resourceId }) => {
          setMessage(null);
          setEvents((prev) =>
            prev.map((event) =>
              event.id === eventId
                ? { ...event, start: newStart, end: newEnd, resourceId }
                : event
            )
          );
        }}
        onEventPlacementRejected={(data) => {
          if (data.action === 'external-drop') {
            return;
          }

          setMessage(
            data.reason === 'overlap'
              ? `${data.event.title} would overlap ${data.conflicts.length} event(s) in that room`
              : 'Room C is reserved for meetings with 20 or more attendees'
          );
        }}
      />

      {message && <Text c="red" size="sm">{message}</Text>}
    </Stack>
  );
}
TreeSelect renderPill

TreeSelect now supports renderPill prop to customize how pills are rendered
for selected values in multiple and checkbox modes, similar to renderPill prop of
MultiSelect. The callback receives the tree node, so pills can use
nodeProps or the node structure, for example to show a different icon for parent and leaf nodes:

import { FileTextIcon, FolderSimpleIcon } from '@phosphor-icons/react';
import { Group, Pill, TreeSelect, TreeSelectProps } from '@mantine/core';
import { data } from './data';

const renderTreePill: TreeSelectProps['renderPill'] = ({ node, onRemove, disabled, readOnly }) => (
  <Pill withRemoveButton={!readOnly} onRemove={onRemove} disabled={disabled}>
    <Group gap={4} wrap="nowrap">
      {node.children || node.hasChildren ? (
        <FolderSimpleIcon size={12} />
      ) : (
        <FileTextIcon size={12} />
      )}
      {node.label}
    </Group>
  </Pill>
);

function Demo() {
  return (
    <TreeSelect
      mode="checkbox"
      checkedStrategy="parent"
      label="Categories"
      placeholder="Pick categories"
      data={data}
      defaultValue={['phones', 'headphones']}
      defaultExpandAll
      renderPill={renderTreePill}
    />
  );
}
Tooltip hideDetached

Tooltip now supports hideDetached prop, which works the same way as
Popover hideDetached. It is enabled by default: the tooltip is now
hidden when its target element is removed from the DOM, hidden with display: none, or scrolled out
of a container that clips it. Previously, the tooltip stayed in place, floating over unrelated
content. Set hideDetached={false} to restore the previous behavior. The prop has no effect on
Tooltip.Floating, which is positioned relative to the mouse pointer.

Note that jsdom reports zero-size rectangles for every element, so in Jest and Vitest every tooltip
is treated as detached and hidden unless the test wrapper sets env="test" on MantineProvider
(as described in the Jest and Vitest guides) or the component is
rendered with hideDetached={false}.

import { Box, Button, Group, Tooltip } from '@mantine/core';

function Demo() {
  return (
    <Box
      bd="1px solid var(--mantine-color-dimmed)"
      p="xl"
      w={{ base: 340, sm: 400 }}
      h={200}
      style={{ overflow: 'auto' }}
    >
      <Box w={1000} h={400}>
        <Group>
          <Tooltip label="Hidden when detached" position="bottom" opened>
            <Button>Hides when detached</Button>
          </Tooltip>

          <Tooltip label="Visible when detached" position="bottom" opened hideDetached={false}>
            <Button>Stays visible</Button>
          </Tooltip>
        </Group>
      </Box>
    </Box>
  );
}
Notifications auto close progress

Notifications now support withAutoCloseProgress prop. When set, a progress line
that fills up until the notification auto closes is displayed at the bottom of every notification.
The line fades out while the auto close timer is paused (for example, when the notification is hovered),
starts over when the timer restarts, and uses the notification color. The prop sets the default for all notifications, it can be overridden
for individual notifications with withAutoCloseProgress property in notifications.show and
notifications.update functions:

import { Button, Group } from '@mantine/core';
import { notifications } from '@mantine/notifications';

function Demo() {
  return (
    <Group justify="center">
      <Button
        onClick={() =>
          notifications.show({
            title: 'Auto close progress',
            message: 'This notification will close in 5 seconds',
            withAutoCloseProgress: true,
            autoClose: 5000,
          })
        }
      >
        Show notification with progress
      </Button>

      <Button
        color="red"
        onClick={() =>
          notifications.show({
            title: 'Something went wrong',
            message: 'Progress line uses notification color',
            color: 'red',
            withAutoCloseProgress: true,
            autoClose: 8000,
          })
        }
      >
        Red notification with progress
      </Button>
    </Group>
  );
}
Notifications promise

New notifications.promise function displays a loading notification while a promise is pending and
updates it with success or error state once the promise settles. success and error can be
functions that receive the resolved value or the rejection reason:

import { Button, Group } from '@mantine/core';
import { notifications } from '@mantine/notifications';

function saveDocument(shouldFail: boolean) {
  return new Promise<{ name: string }>((resolve, reject) => {
    setTimeout(() => {
      if (shouldFail) {
        reject(new Error('Network error'));
      } else {
        resolve({ name: 'report.pdf' });
      }
    }, 2000);
  });
}

function Demo() {
  const save = (shouldFail: boolean) =>
    notifications.promise(saveDocument(shouldFail), {
      loading: {
        title: 'Saving document',
        message: 'Please wait, it will take a couple of seconds',
      },
      success: (value) => ({
        title: 'Document saved',
        message: `${value.name} was saved successfully`,
      }),
      error: (error) => ({
        title: 'Failed to save document',
        message: (error as Error).message,
      }),
    });

  return (
    <Group justify="center">
      <Button onClick={() => save(false)}>Save document</Button>
      <Button color="red" onClick={() => save(true)}>
        Save document (fails)
      </Button>
    </Group>
  );
}
AppShell resizable sections

AppShell now supports resizing AppShell.Navbar/AppShell.Aside
horizontally and AppShell.Header/AppShell.Footer vertically. Pass a useAppShellResize
hook instance to the resize prop to enable it for the configured sections – handles support
mouse, touch and keyboard, and can report drag-to-collapse. Each section accepts a label option
to localize the aria-label of its handle.
See AppShell examples for more details.

Note that when the resize prop is used, --app-shell-* CSS variables are defined on the
AppShell root element instead of :root, so they cannot be read from content rendered in a
Portal, for example from a Modal or a Drawer.

Templates and guides
Other changes
  • HoverCard now opens on keyboard focus, closes with Escape or a press outside, and is announced by screen readers. New events, interactive, role and returnFocus props, and onDismiss callback.
  • HoverCard no longer opens with a tap on touch devices. Set events={{ focus: false, touch: true }} and closeOnEscape={false} to restore the previous behavior.
  • Checkbox and Radio variant="light" colors are resolved with theme.variantColorResolver, so any CSS color or theme color with a shade can be used.
  • ActionBar with keepMounted now uses React Activity instead of display: none, so effects are paused while the bar is closed. Set transitionProps={{ keepMountedMode: 'display-none' }} to restore the previous behavior.
  • Mantine skills for AI coding agents (mantine-form, mantine-combobox, mantine-custom-components) have been updated for 9.x with corrected API details and new patterns.
  • Gatsby and Redwood guides have been removed, gatsby-template and redwood-template are no longer maintained. Existing applications can keep using Mantine, the setup does not change.

v9.6.3

Compare Source

  • [@mantine/hooks] use-click-outside: Add capture phase support (#​9213)
  • [@mantine/core] Select: Fix dropdown not closing on blur when searchable is not set (#​9215)
  • [@mantine/core] PasswordInput: Fix aria-describedby not being taken from InputWrapperContext (#​9216)
  • [@mantine/core] Fix aria-labelledby referencing a missing label element in Checkbox.Group, Radio.Group, Switch.Group (#​9217)
  • [@mantine/core] Slider: Fix thumbProps not being passed to the thumb element (#​9218)
  • [@mantine/core] Table: Fix memoized rows rerendering when Table rerenders with the same props (#​6422)
  • [@mantine/hooks] use-intersection: Use the last entry from a batched observer callback (#​9019)
  • [@mantine/hooks] use-media-query: Catch matchMedia errors when reading the initial value synchronously (#​9020)
  • [@mantine/core] Portal: Cache shared portal node lookup (#​9101)
  • [@mantine/schedule] MobileMonthView: Fix multi-day events not showing when they start in the previous month (#​9153)
  • [@mantine/form] Fix removeListItem not clearing non-nested item errors (#​9180)
  • [@mantine/core] Rating: Fix value being changed by scroll gestures on touch devices (#​9159)
  • [@mantine/notifications] Fix uneven spacing in expanded stacks (#​9176)
  • [@mantine/charts] Fix textColor and gridColor props being passed as attributes to the DOM node (#​9181)
  • [@mantine/hooks] use-hotkeys: Fix preventDefault not being applied when other hotkey options are set (#​9164)
  • [@mantine/hooks] use-throttled-callback: Fix callback becoming unresponsive after clearTimeout (#​9146)
  • [@mantine/hooks] use-roving-index: Fix disabled items not being skipped by ArrowLeft/ArrowRight in grid mode (#​9169)
  • [@mantine/hooks] use-mask: Fix transform not being applied to the initial input value (#​9170)

v9.6.2

Compare Source

  • [@mantine/core] Combobox: Fix incorrect aria-selected setting on up/down arrows press (#​9205)
  • [@mantine/core] NumberInput: Fix min and max boundaries not being respected when trimLeadingZeroesOnBlur is false (#​9192)
  • [@mantine/hooks] use-mask: Fix incorrect handling of input with mixed static values (#​9196)
  • [@mantine/schedule] Add option to resize bacground events (#​9190)
  • [@mantine/schedule] MobileMonthView: Fix missing localization for all day events label (#​9191)
  • [@mantine/hooks] use-scroll-spy: Fix stale nodes being used when element cannot be resolved by the given selector
  • [@mantine/core] ComboboxPopover: Fix incorrect focus management
  • [@mantine/charts] GaugeChart: Fix incorrect roundCaps handling with multiple sections (#​9189)
  • [@mantine/core] NumberInput: Fix incorrect thousands separator handling on paste (#​9102)

v9.6.1

Compare Source

  • [@mantine/ligtbox] Add option to render custom thumbnails for video
  • [@mantine/core] OverflowList: Fix ResizeObserver console warning (#​9177)
  • [@mantine/core] Fix incorrect escape handling in Modal and Drawer stacks (#​9188)
  • [@mantine/core] SegmentedControl: Fix indicator disappearing when data list is replaced with a list with the same length (#​9175)
  • [@mantine/lightbox] Fix circular esm dependency (#​9166)
  • [@mantine/core] Accordion: Fix incorrect border radius being applied to the contained items
  • [@mantine/schedule] Add event overlap mode support to WeekView and DayView
  • [@mantine/core] Menu: Fix incorrect withinPortal prop being available
  • [@mantine/core] Popover: Fix position not being updated when prop changes when the dropdown is opened (#​9156)
  • [@mantine/schedule] Fix same-day events ending at exclusive midnight being dropped in WeekView and DayView components (#​9157)
  • [@mantine/hooks] use-interval: Fix timer restarting when fn changes (#​9158)
  • [@mantine/core] Textarea: Fix ResizeObserver loop error when autosize textarea width changes (#​9162)
  • [@mantine/hooks] use-collapse: Fix incorrect transition state switching when used with Activity (#​9160)

v9.6.0: 🔥

Compare Source

View changelog with demos on mantine.dev website

Support Mantine development

You can now sponsor Mantine development with OpenCollective.
All funds are used to improve Mantine and create new features and components.

@​mantine/lightbox package

New @​mantine/lightbox package – a full-screen media lightbox with carousel navigation,
zoom, thumbnails, toolbar customization, and store-based API. Supports image, video, and custom slides:

import '@mantine/lightbox/styles.css';
import { useState } from 'react';
import { Image, SimpleGrid } from '@mantine/core';
import { Lightbox, LightboxSlideData } from '@mantine/lightbox';

const images = [
  'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-1.png',
  'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-2.png',
  'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-3.png',
  'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-4.png',
  'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-5.png',
];

const slides: LightboxSlideData[] = images.map((src) => ({ src }));

function Demo() {
  const [opened, setOpened] = useState(false);
  const [index, setIndex] = useState(0);

  return (
    <>
      <Lightbox
        opened={opened}
        onClose={() => setOpened(false)}
        slides={slides}
        currentIndex={index}
        onIndexChange={setIndex}
      />

      <SimpleGrid cols={3}>
        {images.map((src, i) => (
          <Image
            key={src}
            src={src}
            radius="md"
            style={{ cursor: 'pointer' }}
            onClick={() => {
              setIndex(i);
              setOpened(true);
            }}
          />
        ))}
      </SimpleGrid>
    </>
  );
}

Key features:

  • Zoom – click to zoom on desktop, double-tap on mobile, scroll wheel and pinch gestures
  • Thumbnails – bottom thumbnail strip with active indicator
  • Store API – mount once, open from anywhere (same pattern as Spotlight and Notifications)
  • Video slides – native video player with auto-pause on navigation
  • Custom slides – render anything with custom thumbnails
  • Transitions – animated open and close with configurable transitionProps (same API as Modal)
  • Keyboard shortcuts – Escape, arrows, F/T/Z for fullscreen/thumbnails/zoom
  • Localization – every string is defined in the labels prop

Notifications custom rendering

Notifications now support renderNotification prop that allows you to completely
replace the default notification with custom content. All animations (enter, exit, drag dismiss)
are preserved for custom notifications:

import { Avatar, Button, Group, rem, Text } from '@mantine/core';
import { notifications } from '@mantine/notifications';

function Demo() {
  return (
    <Group justify="center">
      <Button
        onClick={() =>
          notifications.show({
            autoClose: false,
            renderNotification: (notification) => (
              <div
                style={{
                  display: 'flex',
                  alignItems: 'center',
                  gap: rem(12),
                  padding: rem(16),
                  borderRadius: rem(8),
                  backgroundColor: 'var(--mantine-color-body)',
                  border: '1px solid var(--mantine-color-default-border)',
                  boxShadow: 'var(--mantine-shadow-lg)',
                  userSelect: 'none',
                }}
              >
                <Avatar src={null} radius="xl" color="blue">
                  DM
                </Avatar>
                <div style={{ flex: 1, minWidth: 0 }}>
                  <Text size="sm" fw={600}>
                    Dan sent you a message
                  </Text>
                  <Text size="xs" c="dimmed" lineClamp={1}>
                    Hey, are you free for a quick call?
                  </Text>
                  <Group gap="xs" mt={8}>
                    <Button
                      size="compact-xs"
                      variant="filled"
                      onClick={() =>
                        notifications.hide(notification.id!)
                      }
                    >
                      Reply
                    </Button>
                    <Button
                      size="compact-xs"
                      variant="default"
                      onClick={() =>
                        notifications.hide(notification.id!)
                      }
                    >
                      Dismiss
                    </Button>
                  </Group>
                </div>
              </div>
            ),
            message: '',
          })
        }
      >
        Show custom notification
      </Button>
    </Group>
  );
}

Notifications stacked layout

Notifications now support layout="stacked" prop that displays notifications in a stacked
layout where only the latest notification is fully visible, and older notifications peek out behind it:

import { Button, Group } from '@mantine/core';
import { Notifications, notifications } from '@mantine/notifications';

function Demo() {
  return (
    <>
      {/* Replace your existing Notifications with layout="stacked" */}
      <Notifications layout="stacked" />
      <Group justify="center">
        <Button
          onClick={() => {
            notifications.show({
              title: 'New notification',
              message: 'This notification is part of a stacked layout',
            });
          }}
        >
          Show stacked notification
        </Button>
      </Group>
    </>
  );
}

ActionBar component

New ActionBar component – a fixed-position bottom bar
for bulk selection actions. Designed to be controlled by table or checkbox
selections, it provides a set of actions that can be performed on selected items.

import { useState } from 'react';
import { ActionBar, Button, Checkbox, Table, Text } from '@mantine/core';

const elements = [
  { position: 6, mass: 12.011, symbol: 'C', name: 'Carbon' },
  { position: 7, mass: 14.007, symbol: 'N', name: 'Nitrogen' },
  { position: 39, mass: 88.906, symbol: 'Y', name: 'Yttrium' },
  { position: 56, mass: 137.33, symbol: 'Ba', name: 'Bar

> [!IMPORTANT]
> ✂ PR body was truncated to here.


</details>

---

### Configuration

📅 **Schedule**: (in timezone America/Los_Angeles)

- Branch creation
  - Monday through Friday (`* * * * 1-5`)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/get-convex/aggregate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4zLjIiLCJ1cGRhdGVkSW5WZXIiOiI0NC4xNjQuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

@pkg-pr-new

pkg-pr-new Bot commented Aug 3, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@convex-dev/aggregate@252

commit: ef68046

@renovate
renovate Bot force-pushed the renovate/routine-updates branch 9 times, most recently from 7f045c1 to cc27739 Compare August 9, 2026 17:15
@renovate
renovate Bot force-pushed the renovate/routine-updates branch 15 times, most recently from 22d5b18 to bae10f2 Compare August 18, 2026 21:55
@renovate
renovate Bot force-pushed the renovate/routine-updates branch 5 times, most recently from 6450e82 to e402576 Compare August 24, 2026 06:17
@renovate
renovate Bot force-pushed the renovate/routine-updates branch 5 times, most recently from ef68046 to 1a81ada Compare September 3, 2026 15:40
@renovate

renovate Bot commented Sep 3, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vitest/[email protected]
npm error Found: [email protected]
npm error node_modules/vitest
npm error   dev vitest@"4.1.10" from the root project
npm error   peer vitest@"^4.1.0 || ^5.0.0" from @fast-check/[email protected]
npm error   node_modules/@fast-check/vitest
npm error     dev @fast-check/vitest@"0.5.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vitest@"4.1.11" from @vitest/[email protected]
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"4.1.11" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vitest
npm error   peer vitest@"4.1.11" from @vitest/[email protected]
npm error   node_modules/@vitest/coverage-v8
npm error     dev @vitest/coverage-v8@"4.1.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-15T23_35_09_567Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-15T23_35_09_567Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/routine-updates branch 10 times, most recently from 762ab77 to 0794da2 Compare September 10, 2026 17:55
@renovate
renovate Bot force-pushed the renovate/routine-updates branch 10 times, most recently from 3ca55d2 to 9e5930d Compare September 17, 2026 16:50
@renovate
renovate Bot force-pushed the renovate/routine-updates branch 3 times, most recently from 55a3577 to 87136d7 Compare September 20, 2026 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants