⬆️(dependencies) update js dependencies by renovate[bot] · Pull Request #2448 · suitenumerique/docs

renovate · 2026-06-22T08:19:41Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@ai-sdk/openai (source)	`3.0.65` → `3.0.71`
@mantine/core (source)	`9.2.1` → `9.3.1`
@mantine/hooks (source)	`9.2.1` → `9.3.1`
@next/eslint-plugin-next (source)	`16.2.6` → `16.2.9`
@react-aria/live-announcer	`3.5.0` → `3.5.1`
@sentry/nextjs (source)	`10.53.1` → `10.57.0`
@sentry/node (source)	`10.53.1` → `10.57.0`
@sentry/profiling-node (source)	`10.53.1` → `10.57.0`
@tanstack/eslint-plugin-query (source)	`5.100.14` → `5.101.0`
@tanstack/react-query (source)	`5.100.14` → `5.101.0`
@tanstack/react-query-devtools (source)	`5.100.14` → `5.101.0`
@tiptap/extensions (source)	`3.23.6` → `3.26.1`
@types/node (source)	`24.12.4` → `24.13.2`
@types/react (source)	`19.2.15` → `19.2.17`
@typescript-eslint/eslint-plugin (source)	`8.59.4` → `8.61.0`
@typescript-eslint/parser (source)	`8.59.4` → `8.61.0`
@typescript-eslint/utils (source)	`8.59.4` → `8.61.0`
@vitest/eslint-plugin	`1.6.18` → `1.6.20`
ai (source)	`6.0.191` → `6.0.205`
axios (source)	`1.16.1` → `1.18.0`
eslint (source)	`10.4.0` → `10.5.0`
eslint-config-next (source)	`16.2.6` → `16.2.9`
eslint-plugin-prettier	`5.5.5` → `5.5.6`
i18next (source)	`26.2.0` → `26.3.1`
mjml (source)	`5.2.2` → `5.3.0`
next (source)	`16.2.6` → `16.2.9`
posthog-js (source)	`1.376.0` → `1.386.6`
prettier (source)	`3.8.3` → `3.8.4`
prosemirror-view	`1.41.8` → `1.41.9`
react (source)	`19.2.6` → `19.2.7`
react-aria-components	`1.17.0` → `1.18.0`
react-dom (source)	`19.2.6` → `19.2.7`
vitest (source)	`4.1.7` → `4.1.9`
webpack	`5.107.1` → `5.107.2`
yjs (source)	`13.6.30` → `13.6.31`
zustand	`5.0.13` → `5.0.14`

Release Notes

vercel/ai (@ai-sdk/openai)

`v3.0.71`

Patch Changes

Updated dependencies [bfa5864]
Updated dependencies [f42aa79]
- @ai-sdk/provider-utils@4.0.29

`v3.0.69`

Compare Source

Patch Changes

9a55f6d: feat(openai): add namespaces for tool definitions

`v3.0.68`

Compare Source

Patch Changes

c65c952: fix(openai): round-trip namespace on function_call input items

When tool_search dispatches a deferred tool, the resulting function_call carries a namespace field identifying which deferred-tool group the model picked. #14789 preserved this on the read side (providerMetadata.openai.namespace), but the write side still serialized function_call input items without namespace. Multi-step / multi-turn conversations then failed with Missing namespace for function_call '<name>'. ... Round-trip the model's function_call item with its namespace field included.

convert-to-openai-responses-input.ts now reads namespace from providerOptions.openai.namespace (or providerMetadata.openai.namespace) on tool-call parts and includes it on the serialized function_call item, mirroring how itemId is round-tripped.

`v3.0.67`

Compare Source

Patch Changes

c679fec: feat(provider/azure):web search tool in the Azure OpenAI Responses API.

`v3.0.66`

Compare Source

Patch Changes

c82ab42: feat(openai): forward web_search_call.action.queries from Responses API

mantinedev/mantine (@mantine/core)

`v9.3.1`

Compare Source

What's Changed

[@mantine/notifications] Fix stale DOM nodes references not being cleaned up when notifications is closed (#8955)
[@mantine/dates] DateInput: Add presets support (#8954)
[@mantine/core] Collapse: Fix keepMounted prop not being set correctly (#8949)
[@mantine/core] Menu: Add controlled state support for Menu.Sub opened state
[@mantine/schedule] Fix incorrect current time indicator position when time does not divide evenly with interval minutes in DayView and WeekView (#8945)
[@mantine/core] Popover: Fix context menu not working on iOS touch devices (#8942)
[@mantine/core] SegemntedControl: Fix incorrect indicator border-radius calculation (#8904)
[@mantine/core] PinInput: Fix incorrect placeholder text centering (#8943)
[@mantine/core] Tree: Fix arrow key navigation focusing hidden nodes when keepMounted is set (#8939)
[@mantine/core] MaskInput: Fix compatibility issues with uncontrolled use-form (#8947)
[@mantine/hooks] use-id: Fix id changing to new value with Activity (#8925)

New Contributors

@spokodev made their first contribution in #8925
@cyphercodes made their first contribution in #8947
@KasperiP made their first contribution in #8939

Full Changelog: mantinedev/mantine@9.3.0...9.3.1

`v9.3.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.

Pagination responsive layout

Pagination component now supports layout="responsive" prop that uses CSS container
queries to switch between page number buttons and a compact "Page X of Y" label based on the available width.

import { Box, Pagination } from '@&#8203;mantine/core';

function Demo() {
  return (
    <Box style={{ resize: 'horizontal', overflow: 'auto', minWidth: 200, maxWidth: '100%' }}>
      <Pagination total={20} layout="responsive" />
    </Box>
  );
}

Text textWrap prop

Text and Blockquote components now support
textWrap prop that controls the text-wrap CSS property. You can use it to balance line lengths
or prevent orphaned words in paragraphs.

import { Text } from '@&#8203;mantine/core';

function Demo() {
  return (
    <Text textWrap="wrap">
      Lorem, ipsum dolor sit amet consectetur adipisicing elit. Quasi voluptatibus inventore iusto
      cum dolore molestiae perspiciatis! Totam repudiandae impedit maxime!
    </Text>
  );
}

use-splitter hook

New use-splitter hook provides resizable split-pane functionality
with pointer drag, keyboard navigation (WAI-ARIA Window Splitter pattern), collapsible panels
and min/max constraints:

import React from 'react';
import { DotsSixVerticalIcon } from '@&#8203;phosphor-icons/react';
import { useSplitter } from '@&#8203;mantine/hooks';

const colors = ['var(--mantine-color-blue-filled)', 'var(--mantine-color-teal-filled)'];
const labels = ['Panel A', 'Panel B'];

function Demo() {
  const splitter = useSplitter({
    panels: [
      { defaultSize: 50, min: 20 },
      { defaultSize: 50, min: 20 },
    ],
  });

  return (
    <div
      ref={splitter.ref}
      style={{
        display: 'flex',
        height: 200,
        borderRadius: 'var(--mantine-radius-md)',
        overflow: 'hidden',
      }}
    >
      {splitter.sizes.map((size, i) => (
        <React.Fragment key={i}>
          {i > 0 && (
            <div
              {...splitter.getHandleProps({ index: i - 1 })}
              style={{
                width: 4,
                flexShrink: 0,
                cursor: 'col-resize',
                touchAction: 'none',
                backgroundColor: 'var(--mantine-color-default-border)',
                position: 'relative',
              }}
            >
              <div
                style={{
                  position: 'absolute',
                  top: '50%',
                  left: '50%',
                  transform: 'translate(-50%, -50%)',
                  width: 8,
                  height: 40,
                  display: 'flex',
                  alignItems: 'center',
                  justifyContent: 'center',
                  borderRadius: 'var(--mantine-radius-xs)',
                  backgroundColor: 'var(--mantine-color-default)',
                  border: '1px solid var(--mantine-color-default-border)',
                  color: 'var(--mantine-color-dimmed)',
                }}
              >
                <DotsSixVerticalIcon />
              </div>
            </div>
          )}
          <div
            style={{
              width: `${size}%`,
              display: 'flex',
              flexDirection: 'column',
              alignItems: 'center',
              justifyContent: 'center',
              backgroundColor: colors[i],
              color: 'var(--mantine-color-white)',
              fontWeight: 500,
              whiteSpace: 'nowrap',
              gap: 2,
            }}
          >
            {labels[i]} ({Math.round(size)}%)
          </div>
        </React.Fragment>
      ))}
    </div>
  );
}

Splitter component

New Splitter component provides declarative resizable split pane layout
built on top of the use-splitter hook:

import { Splitter } from '@&#8203;mantine/core';

function Demo() {
  return (
    <Splitter orientation="horizontal" h={200}>
      <Splitter.Pane defaultSize={50} min={20} bg="blue">
        First pane
      </Splitter.Pane>
      <Splitter.Pane defaultSize={50} min={20} bg="teal">
        Second pane
      </Splitter.Pane>
    </Splitter>
  );
}

CodeHighlight line numbers

CodeHighlight component now supports withLineNumbers prop
to display line numbers alongside the code:

import { CodeHighlight } from '@&#8203;mantine/code-highlight';

const exampleCode = `...`;

function Demo() {
  return <CodeHighlight code={exampleCode} language="tsx" withLineNumbers />;
}

OverflowList collapseFrom

OverflowList component now supports collapseFrom prop that controls
from which direction items are collapsed when they overflow. Set collapseFrom="start" to
collapse items from the beginning – this is useful for breadcrumb-like patterns where
the last items should remain visible.

// OverflowListDemo.tsx
import { Badge, OverflowList } from '@&#8203;mantine/core';
import { data } from './data';

function Demo() {
  return (
    <div style={{ resize: 'horizontal', overflow: 'auto', maxWidth: '100%' }}>
      <OverflowList
        data={data}
        gap={4}
        collapseFrom="start"
        renderOverflow={(items) => <Badge>+{items.length} more</Badge>}
        renderItem={(item, index) => <Badge key={index}>{item}</Badge>}
      />
    </div>
  );
}

// data.ts
export const data = [
  'Apple',
  'Banana',
  'Cherry',
  'Date',
  'Elderberry',
  'Fig',
  'Grape',
  'Honeydew',
  'Indian Fig',
  'Jackfruit',
  'Kiwi',
  'Lemon',
  'Mango',
  'Nectarine',
  'Orange',
  'Papaya',
];

Textarea bottomSection

Textarea component now supports bottomSection prop that renders content
inside the input border at the bottom. This is useful for displaying character counters
or other supplementary information:

import { useState } from 'react';
import { Text, Textarea } from '@&#8203;mantine/core';

function Demo() {
  const maxLength = 500;
  const [value, setValue] = useState('');

  return (
    <Textarea
      label="Your message"
      placeholder="Type your message..."
      autosize
      minRows={4}
      value={value}
      onChange={(event) => setValue(event.currentTarget.value.slice(0, maxLength))}
      bottomSection={
        <Text size="xs" c="dimmed">
          {value.length}/{maxLength} characters
        </Text>
      }
    />
  );
}

Combobox floatingHeight

Combobox, Select, MultiSelect,
Autocomplete and TagsInput now support
floatingHeight="viewport". When set, the dropdown grows to fill the available vertical
space in the viewport and the flip middleware is disabled – useful when working with
large option lists:

import { useState } from 'react';
import { Combobox, Input, InputBase, ScrollArea, useCombobox } from '@&#8203;mantine/core';

const countries = [
  'Afghanistan', 'Albania', 'Algeria', 'Andorra', 'Angola', 'Argentina', 'Armenia', 'Australia',
  'Austria', 'Azerbaijan', 'Bahamas', 'Bahrain', 'Bangladesh', 'Barbados', 'Belarus', 'Belgium',
  'Belize', 'Benin', 'Bhutan', 'Bolivia', 'Botswana', 'Brazil', 'Brunei', 'Bulgaria', 'Burkina Faso',
  'Burundi', 'Cambodia', 'Cameroon', 'Canada', 'Cape Verde', 'Chad', 'Chile', 'China', 'Colombia',
  'Comoros', 'Costa Rica', 'Croatia', 'Cuba', 'Cyprus', 'Czech Republic', 'Denmark', 'Djibouti',
  'Dominica', 'Ecuador', 'Egypt', 'El Salvador', 'Estonia', 'Eswatini', 'Ethiopia', 'Fiji',
  'Finland', 'France', 'Gabon', 'Gambia', 'Georgia', 'Germany', 'Ghana', 'Greece', 'Grenada',
  'Guatemala', 'Guinea', 'Guyana', 'Haiti', 'Honduras', 'Hungary', 'Iceland', 'India', 'Indonesia',
  'Iran', 'Iraq', 'Ireland', 'Israel', 'Italy', 'Jamaica', 'Japan', 'Jordan', 'Kazakhstan', 'Kenya',
  'Kiribati', 'Kuwait', 'Kyrgyzstan', 'Laos', 'Latvia', 'Lebanon', 'Lesotho', 'Liberia', 'Libya',
  'Liechtenstein', 'Lithuania', 'Luxembourg', 'Madagascar', 'Malawi', 'Malaysia', 'Maldives',
  'Mali', 'Malta', 'Mauritania', 'Mauritius', 'Mexico', 'Moldova', 'Monaco', 'Mongolia',
];

function Demo() {
  const combobox = useCombobox({
    onDropdownClose: () => combobox.resetSelectedOption(),
  });

  const [value, setValue] = useState<string | null>(null);

  const options = countries.map((item) => (
    <Combobox.Option value={item} key={item}>
      {item}
    </Combobox.Option>
  ));

  return (
    <Combobox
      store={combobox}
      floatingHeight="viewport"
      onOptionSubmit={(val) => {
        setValue(val);
        combobox.closeDropdown();
      }}
    >
      <Combobox.Target>
        <InputBase
          component="button"
          type="button"
          pointer
          rightSection={<Combobox.Chevron />}
          rightSectionPointerEvents="none"
          onClick={() => combobox.toggleDropdown()}
        >
          {value || <Input.Placeholder>Pick a country</Input.Placeholder>}
        </InputBase>
      </Combobox.Target>

      <Combobox.Dropdown>
        <Combobox.Options>
          <ScrollArea.Autosize mah="var(--combobox-floating-options-max-height)" type="scroll">
            {options}
          </ScrollArea.Autosize>
        </Combobox.Options>
      </Combobox.Dropdown>
    </Combobox>
  );
}

Menu submenu safe polygon

Menu submenus now use a safe polygon when moving the cursor from
the parent item to the dropdown. This allows you to move the cursor diagonally
across other menu items without accidentally closing the submenu.

import { Button, Menu } from '@&#8203;mantine/core';

function Demo() {
  return (
    <Menu width={200} position="bottom-start">
      <Menu.Target>
        <Button>Toggle Menu</Button>
      </Menu.Target>

      <Menu.Dropdown>
        <Menu.Item>Dashboard</Menu.Item>

        <Menu.Sub openDelay={120} closeDelay={150}>
          <Menu.Sub.Target>
            <Menu.Sub.Item>Products</Menu.Sub.Item>
          </Menu.Sub.Target>

          <Menu.Sub.Dropdown>
            <Menu.Item>All products</Menu.Item>
            <Menu.Item>Categories</Menu.Item>
            <Menu.Item>Tags</Menu.Item>
            <Menu.Item>Attributes</Menu.Item>
            <Menu.Item>Shipping classes</Menu.Item>
          </Menu.Sub.Dropdown>
        </Menu.Sub>

        <Menu.Item>Customers</Menu.Item>
        <Menu.Item>Reports</Menu.Item>

        <Menu.Sub>
          <Menu.Sub.Target>
            <Menu.Sub.Item>Orders</Menu.Sub.Item>
          </Menu.Sub.Target>

          <Menu.Sub.Dropdown>
            <Menu.Item>Open</Menu.Item>
            <Menu.Item>Completed</Menu.Item>
            <Menu.Item>Cancelled</Menu.Item>
          </Menu.Sub.Dropdown>
        </Menu.Sub>

        <Menu.Sub>
          <Menu.Sub.Target>
            <Menu.Sub.Item>Settings</Menu.Sub.Item>
          </Menu.Sub.Target>

          <Menu.Sub.Dropdown>
            <Menu.Item>Profile</Menu.Item>
            <Menu.Item>Security</Menu.Item>
            <Menu.Item>Notifications</Menu.Item>
          </Menu.Sub.Dropdown>
        </Menu.Sub>
      </Menu.Dropdown>
    </Menu>
  );
}

Menu search

Menu now supports Menu.Search – a search input that filters items
without taking focus away from the input. Use ArrowUp/ArrowDown to move the
highlight, Enter to trigger the highlighted item. Filtering logic is controlled
by the user: pass value/onChange and filter Menu.Item children based on the query.
The search value is cleared automatically after the menu close transition completes; set
clearSearchOnClose={false} to keep the query between openings.

import { useState } from 'react';
import { Button, Menu, Text } from '@&#8203;mantine/core';

const data = [
  'Dashboard',
  'Customers',
  'Products',
  'Orders',
  'Reports',
  'Settings',
  'Integrations',
  'Billing',
  'Team members',
  'Help center',
];

function Demo() {
  const [query, setQuery] = useState('');
  const items = data.filter((item) => item.toLowerCase().includes(query.toLowerCase().trim()));

  return (
    <Menu shadow="md" width={240}>
      <Menu.Target>
        <Button>Toggle menu</Button>
      </Menu.Target>

      <Menu.Dropdown>
        <Menu.Search
          value={query}
          onChange={(event) => setQuery(event.currentTarget.value)}
          placeholder="Search items"
        />

        {items.length > 0 ? (
          items.map((item) => <Menu.Item key={item}>{item}</Menu.Item>)
        ) : (
          <Text c="dimmed" size="sm" ta="center" py="xs">
            Nothing found
          </Text>
        )}
      </Menu.Dropdown>
    </Menu>
  );
}

Menu checkbox and radio items

Menu now supports Menu.CheckboxItem, Menu.RadioItem, and Menu.RadioGroup
for building option menus. Checkbox and radio items render an indicator slot at the start
and do not close the menu on click by default. The new alignItemsLabels prop on Menu
controls how indicator slot space is reserved so labels stay aligned when mixing plain
and indicator items.

import { useState } from 'react';
import { Button, Menu } from '@&#8203;mantine/core';

function Demo() {
  const [columns, setColumns] = useState({
    name: true,
    email: true,
    role: false,
    lastSeen: false,
  });

  const setColumn = (key: keyof typeof columns) => (checked: boolean) =>
    setColumns((current) => ({ ...current, [key]: checked }));

  return (
    <Menu shadow="md" width={220} closeOnItemClick={false}>
      <Menu.Target>
        <Button>Columns</Button>
      </Menu.Target>

      <Menu.Dropdown>
        <Menu.Label>Visible columns</Menu.Label>
        <Menu.CheckboxItem checked={columns.name} onChange={setColumn('name')}>
          Name
        </Menu.CheckboxItem>
        <Menu.CheckboxItem checked={columns.email} onChange={setColumn('email')}>
          Email
        </Menu.CheckboxItem>
        <Menu.CheckboxItem checked={columns.role} onChange={setColumn('role')}>
          Role
        </Menu.CheckboxItem>
        <Menu.CheckboxItem checked={columns.lastSeen} onChange={setColumn('lastSeen')}>
          Last seen
        </Menu.CheckboxItem>
      </Menu.Dropdown>
    </Menu>
  );
}

import { useState } from 'react';
import { Button, Menu } from '@&#8203;mantine/core';

function Demo() {
  const [sort, setSort] = useState('newest');

  return (
    <Menu shadow="md" width={220} closeOnItemClick={false}>
      <Menu.Target>
        <Button>Sort by</Button>
      </Menu.Target>

      <Menu.Dropdown>
        <Menu.Label>Order</Menu.Label>
        <Menu.RadioGroup value={sort} onChange={setSort}>
          <Menu.RadioItem value="newest">Newest first</Menu.RadioItem>
          <Menu.RadioItem value="oldest">Oldest first</Menu.RadioItem>
          <Menu.RadioItem value="popular">Most popular</Menu.RadioItem>
          <Menu.RadioItem value="commented">Most commented</Menu.RadioItem>
        </Menu.RadioGroup>
      </Menu.Dropdown>
    </Menu>
  );
}

Menu context menu

Menu now supports Menu.ContextMenu – a target replacement that opens the
dropdown at the cursor position when the wrapped element is right-clicked. The browser's
default context menu is suppressed, and right-clicking again repositions the dropdown to
the new coordinates.

import { Menu, Paper, Text } from '@&#8203;mantine/core';

function Demo() {
  return (
    <Menu shadow="md" width={200}>
      <Menu.ContextMenu>
        <Paper withBorder p="xl" radius="md" style={{ userSelect: 'none', textAlign: 'center' }}>
          <Text fw={500}>Right-click anywhere inside this area</Text>
          <Text c="dimmed" size="sm" mt={4}>
            The menu will open at the cursor position
          </Text>
        </Paper>
      </Menu.ContextMenu>

      <Menu.Dropdown>
        <Menu.Label>Actions</Menu.Label>
        <Menu.Item>Open</Menu.Item>
        <Menu.Item>Rename</Menu.Item>
        <Menu.Item>Duplicate</Menu.Item>
        <Menu.Divider />
        <Menu.Item color="red">Delete</Menu.Item>
      </Menu.Dropdown>
    </Menu>
  );
}

Popover context menu

Popover now supports Popover.ContextMenu – a target replacement that
opens the dropdown at the cursor position on right-click. Unlike Menu.ContextMenu,
Popover.Dropdown can contain any content.

import { Avatar, Button, Group, Paper, Popover, Stack, Text } from '@&#8203;mantine/core';

function Demo() {
  return (
    <Popover width={260} shadow="md" position="bottom-start" offset={0}>
      <Popover.ContextMenu>
        <Paper withBorder p="xl" radius="md" style={{ userSelect: 'none', textAlign: 'center' }}>
          <Text fw={500}>Right-click anywhere inside this area</Text>
          <Text c="dimmed" size="sm" mt={4}>
            A popover will open at the cursor position
          </Text>
        </Paper>
      </Popover.ContextMenu>

      <Popover.Dropdown>
        <Stack gap="xs">
          <Group gap="sm" wrap="nowrap">
            <Avatar radius="xl" color="blue">JD</Avatar>
            <div>
              <Text size="sm" fw={500}>Jane Doe</Text>
              <Text size="xs" c="dimmed">jane@example.com</Text>
            </div>
          </Group>
          <Group grow gap="xs">
            <Button size="xs" variant="default">Message</Button>
            <Button size="xs">Follow</Button>
          </Group>
        </Stack>
      </Popover.Dropdown>
    </Popover>
  );
}

Menu type-ahead navigation

When focus is inside Menu dropdown (and Menu.Search is not used), pressing a
printable character key now moves focus to the next item whose label starts with the typed
character. Pressing the same character cycles through matches, and multiple characters typed
within 500ms match items by full prefix.

import { Menu, Button, Text } from '@&#8203;mantine/core';
import { GearSixIcon, MagnifyingGlassIcon, ImageIcon, ChatCircleIcon, TrashIcon, IconArrowsLeftRight } from '@&#8203;phosphor-icons/react';

function Demo() {
  return (
    <Menu shadow="md" width={200}>
      <Menu.Target>
        <Button>Toggle menu</Button>
      </Menu.Target>

      <Menu.Dropdown>
        <Menu.Label>Application</Menu.Label>
        <Menu.Item leftSection={<GearSixIcon size={14} />}>
          Settings
        </Menu.Item>
        <Menu.Item leftSection={<ChatCircleIcon size={14} />}>
          Messages
        </Menu.Item>
        <Menu.Item leftSection={<ImageIcon size={14} />}>
          Gallery
        </Menu.Item>
        <Menu.Item
          leftSection={<MagnifyingGlassIcon size={14} />}
          rightSection={
            <Text size="xs" c="dimmed">
              ⌘K
            </Text>
          }
        >
          Search
        </Menu.Item>

        <Menu.Divider />

        <Menu.Label>Danger zone</Menu.Label>
        <Menu.Item
          leftSection={<IconArrowsLeftRight size={14} />}
        >
          Transfer my data
        </Menu.Item>
        <Menu.Item
          color="red"
          leftSection={<TrashIcon size={14} />}
        >
          Delete my account
        </Menu.Item>
      </Menu.Dropdown>
    </Menu>
  );
}

Highlight accent and case insensitive matching

Highlight component now supports caseInsensitive and accentInsensitive
props. Both are enabled by default – matching is case-insensitive and accent-insensitive,
so cafe matches café, CAFÉ, etc. Set either prop to false to opt out:

import { Highlight, Stack, Text } from '@&#8203;mantine/core';

function Demo() {
  return (
    <Stack gap="md">
      <div>
        <Text size="sm" fw={500} mb={5}>
          With accent-insensitive matching (default)
        </Text>
        <Highlight highlight="cafe">We visited café and cafe.</Highlight>
      </div>

      <div>
        <Text size="sm" fw={500} mb={5}>
          {'With accent-sensitive matching (accentInsensitive={false})'}
        </Text>
        <Highlight highlight="cafe" accentInsensitive={false}>
          We visited café and cafe.
        </Highlight>
      </div>
    </Stack>
  );
}

PieChart and DonutChart labelsType="name"

PieChart and DonutChart components now support
labelsType="name" to display segment names as labels instead of values or percentages:

// Demo.tsx
import { PieChart } from '@&#8203;mantine/charts';
import { data } from './data';

function Demo() {
  return <PieChart data={data} withLabelsLine labelsPosition="outside" labelsType="name" withLabels />;
}

// data.ts
export const data = [
  { name: 'USA', value: 400, color: 'indigo.6' },
  { name: 'India', value: 300, color: 'yellow.6' },
  { name: 'Japan', value: 300, color: 'teal.6' },
  { name: 'Other', value: 200, color: 'gray.6' },
];

Tooltip merge arrow position

Tooltip, Popover and other components based on Popover
now support arrowPosition="merge". When set, the arrow forms a right triangle merged
with the corresponding corner of the dropdown, and the border radius of that corner is removed.

import { Tooltip, Button } from '@&#8203;mantine/core';

function Demo() {
  return (
    <Tooltip arrowPosition="center" arrowOffset={10} arrowSize={4} arrowRadius={0} label="Tooltip" withArrow opened position="top-start">
      <Button>Button with tooltip</Button>
    </Tooltip>
  );
}

Popover preventPositionChangeWhenVisible default

Popover and all components built on top of it (Combobox,
Select, MultiSelect, Autocomplete,
TagsInput, Menu, HoverCard, Tooltip,
ColorInput, date pickers and others) now treat preventPositionChangeWhenVisible
as true by default.

With this behavior, the dropdown picks its side once on open – respecting the position prop
when there is enough room – and then stays on that side until the dropdown is closed. Scrolling,
resizing, or changes to the dropdown content (for example narrowing a searchable Select) no
longer cause the dropdown to flip between top and bottom while it is open. The next open recalculates
the side from scratch.

The flip is also more predictable: when neither side fits, the dropdown falls back to the
preferred position prop instead of the side with marginally more space.

To restore the previous behavior – where the dropdown could re-flip while open whenever
available space changed – pass preventPositionChangeWhenVisible={false}:

<Select
  comboboxProps={{ preventPositionChangeWhenVisible: false }}
  data={['React', 'Angular', 'Svelte']}
/>

Schedule getCurrentTime

DayView and WeekView components now support getCurrentTime
prop – a function that returns the current time used by the current time indicator. It is called on
every tick, so the indicator keeps updating automatically. Combined with the timezone-agnostic event
strings, this allows displaying the indicator in any timezone without re-implementing the update loop:

// Demo.tsx
import { useState } from 'react';
import dayjs from 'dayjs';
import timezone from 'dayjs/plugin/timezone';
import utc from 'dayjs/plugin/utc';
import { Select, Stack } from '@&#8203;mantine/core';
import { DayView } from '@&#8203;mantine/schedule';
import { getEvents } from './data';

dayjs.extend(utc);
dayjs.extend(timezone);

const timezones = ['UTC', 'America/New_York', 'Europe/Berlin', 'Asia/Kolkata', 'Asia/Tokyo'];

function Demo() {
  const [tz, setTz] = useState('UTC');

  // getCurrentTime is called on every tick, so the indicator keeps updating
  const getCurrentTime = () => dayjs().tz(tz).format('YYYY-MM-DD HH:mm:ss');
  const currentDate = getCurrentTime().split(' ')[0];

  return (
    <Stack>
      <Select
        label="Display timezone"
        data={timezones}
        value={tz}
        onChange={(value) => setTz(value!)}
        allowDeselect={false}
      />

      <DayView
        date={currentDate}
        events={getEvents(currentDate)}
        getCurrentTime={getCurrentTime}
        startScrollTime={dayjs(getCurrentTime()).subtract(2, 'hour').format('HH:mm:ss')}
        withCurrentTimeIndicator
        withCurrentTimeBubble
      />
    </Stack>
  );
}

// data.ts
import dayjs from 'dayjs';
import { ScheduleEventData } from '@&#8203;mantine/schedule';

export function getEvents(date: string): ScheduleEventData[] {
  return [
    { id: 1, title: 'Morning standup', start: `${date} 09:00:00`, end: `${date} 09:30:00`, color: 'blue' },
    { id: 2, title: 'Team meeting', start: `${date} 12:00:00`, end: `${date} 13:00:00`, color: 'teal' },
    { id: 3, title: 'Code review', start: `${date} 16:00:00`, end: `${date} 17:00:00`, color: 'grape' },
  ];
}

`v9.2.2`

Compare Source

What's Changed

[@mantine/core] Pill: Fix incorrect overflow handling (#8929)
[@mantine/dates] TimePicker: Fix incorrect am/pm switching in some cases in production builds (#8911)
[@mantine/hooks] use-mask: Fix undo keyboard shortcut not working (#8927)
[@mantine/hooks] use-mask: Fix cursor jumping on paste/cut (#8926)
[@mantine/core] Input: Fix sections misplaced when dir overrides parent direction (#8905)
[@mantine/core] Select: Fix clear button not showing for falsy primitive values (#8901)
[@mantine/core] Fix incorrect attributes type in Modal, Drawer and Spotlight
[@mantine/tiptap] Fix controls throwing errors when editor is destroyed/not initialized (#8900)
[@mantine/core] Menu: Add option to pass safe area polygon options down to Menu.Sub (#8908)

New Contributors

@chbaefront made their first contribution in #8908
@krusche made their first contribution in #8900
@hyeongjun6364 made their first contribution in #8901
@Israadaassi1 made their first contribution in #8921

Full Changelog: mantinedev/mantine@9.2.1...9.2.2

vercel/next.js (@next/eslint-plugin-next)

`v16.2.9`

Compare Source

Empty release to ensure next@latest points at a stable release. Next.js only allows publishing with Trusted Publishing enabled. In order to fix NPM dist-tags, we have to release a new version. Updating dist-tags is not possible with Trusted Publishing.

`v16.2.8`

Compare Source

Release with no changes in an attempt to fix next@latest pointing at a prerelease version.

`v16.2.7`

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

Backport documentation fixes for v16.2 (#93804)
[backport] Patch playwright-core to resolve _finishedPromise on requestFailed (#93920)
[backport] Fix dev mode hydration failure when page is served from HTTP cache (#93492)
[backport] Fix catch-all router.query corruption with basePath + rewrites (#93917)
[backport] Encode non-ASCII characters in cache tags at construction (#93918)
[backport] Fix server action forwarding loop with middleware rewrites (#93919)
[backport] Turbopack: switch from base40 to base38 hash encoding (#93932)
[ci] Disable hanging node 24 typescript tests on 16.2 backport branch (#94164)
[backport] Fix "type: module" in project dir when using standalone or adapters (#94050)
[backport] Propagate adapter preferred regions (#94200)
[16.2.x] Don't drop FormData entries (#94240)
[backport] feat(turbopack): add LocalPathOrProjectPath PostCSS config resolution (#94284)

Credits

Huge thanks to @eps1lon, @icyJoseph, @unstubbable, @mischnic, @bgw, @timneutkens, and @lukesandberg for helping!

adobe/react-spectrum (@react-aria/live-announcer)

`v3.5.1`

Compare Source

getsentry/sentry-javascript (@sentry/nextjs)

`v10.57.0`

Compare Source

Important Changes

feat(angular): Add support for Angular 22 (#21330)

@sentry/angular now officially supports Angular 22.
ref(core): Deprecate sendDefaultPii in favor of dataCollection (#21277)

sendDefaultPii is deprecated and will be removed in v11. The new dataCollection option lets you control each category of collected data.
sendDefaultPii: true still works and maps to enabling all dataCollection categories.
dataCollection.userInfo defaults to true when dataCollection is provided, meaning auto-populated user.* fields (e.g. IP address from a request) are collected by default.
Data you set explicitly (like via Sentry.setUser()) is always sent regardless.
When dataCollection is not set at all, the legacy sendDefaultPii behavior applies (userInfo: false by default) to preserve backward compatibility.

Note that an empty dataCollection: {} falls back to more permissive defaults than sendDefaultPii: false, so replicate the old behavior by opting out explicitly:
```
Sentry.init({
  dataCollection: {
    userInfo: false,
    genAI: { inputs: false, outputs: false },
    httpBodies: [],
    httpHeaders: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
    cookies: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
    queryParams: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
  },
});
```

Other Changes

feat: Use dataCollection.frameContextLines for ContextLines integration (#21323)
feat(cloudflare): Auto instrument D1 based on env (#21276)
feat(core): Change default of dataCollection.userInfo to true (#21348)
feat(core): Default dataCollection.httpBodies to all valid body types (#21352)
feat(hono): Filter noisy transactions (favicon etc) (#21365)
fix(cloudflare): Don't track negatively sampled spans (#21367)
fix(core): Use safeDateNow calls for new Date() reads (#21351)
fix(nextjs): Shim pinoIntegration on edge runtime (#21347)
fix(node): Prevent PostgresJs integration from emitting duplicate spans per query (#21364)
fix(node-core): Read __SENTRY_SERVER_MODULES__ lazily so Turbopack injection is honored (#21339)
fix(react): Detect React Router v6/v7 navigations in a layout effect to propagate the correct trace (#21326)
fix(react): Remove unused react.componentStack event context (#21183)
fix(replays): Record sentry._internal.replay_is_buffering for spans (#21297)

Internal Changes

chore: Bump volta node version from 20.19.

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- "before 7am on monday"
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

github-actions · 2026-06-22T08:29:19Z

Size Change: +7.59 kB (+0.18%)

Total Size: 4.34 MB

📦 View Changed

Filename	Size	Change
`apps/impress/out/_next/static/b4522711/_buildManifest.js`	672 B	+672 B (new file)	🆕
`apps/impress/out/_next/static/chunks/250.js`	0 B	-644 kB (removed)	🏆
`apps/impress/out/_next/static/chunks/8614.js`	649 kB	+649 kB (new file)	🆕
`apps/impress/out/_next/static/chunks/pages/_app.js`	586 kB	+2.08 kB (+0.36%)
`apps/impress/out/_next/static/css/2ad3b202f2a12d85.css`	11.7 kB	+11.7 kB (new file)	🆕
`apps/impress/out/_next/static/css/38e3ed7af6015b2d.css`	0 B	-11.5 kB (removed)	🏆
`apps/impress/out/_next/static/css/498ca728c74efcfc.css`	13.8 kB	+13.8 kB (new file)	🆕
`apps/impress/out/_next/static/css/b89d8f3797333578.css`	0 B	-13.7 kB (removed)	🏆
`apps/impress/out/_next/static/fd6dd310/_buildManifest.js`	0 B	-676 B (removed)	🏆

_{compressed-size-action}

renovate · 2026-06-23T09:43:16Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

We are pinning the prosemirror dependencies to avoid conflicts with other versions.

Moderate: - @babel/core - @opentelemetry/core - dompurify - form-data - js-yaml - markdown-it - undici - ws

renovate Bot added automated Pull request created automatically dependencies Pull requests that update a dependency file noChangeLog labels Jun 22, 2026

AntoLC self-assigned this Jun 22, 2026

AntoLC force-pushed the renovate/js-dependencies branch from 585a649 to a983369 Compare June 23, 2026 09:42

AntoLC force-pushed the renovate/js-dependencies branch from a983369 to cce39d1 Compare June 23, 2026 09:51

AntoLC self-requested a review June 23, 2026 09:52

AntoLC approved these changes Jun 23, 2026

View reviewed changes

AntoLC mentioned this pull request Jun 23, 2026

[Snyk] Upgrade mjml from 5.2.2 to 5.3.0 #2434

Closed

renovate Bot and others added 3 commits June 23, 2026 12:17

⬆️(dependencies) update js dependencies

e4b6132

📌(dependencies) pin prosemirror deps

b8c2406

We are pinning the prosemirror dependencies to avoid conflicts with other versions.

🔒️(js) fix security warning

3304c12

Moderate: - @babel/core - @opentelemetry/core - dompurify - form-data - js-yaml - markdown-it - undici - ws

AntoLC force-pushed the renovate/js-dependencies branch from cce39d1 to 3304c12 Compare June 23, 2026 10:18

AntoLC merged commit 3304c12 into main Jun 23, 2026
40 checks passed

AntoLC deleted the renovate/js-dependencies branch June 23, 2026 10:39

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

⬆️(dependencies) update js dependencies#2448

⬆️(dependencies) update js dependencies#2448
AntoLC merged 3 commits into
mainfrom
renovate/js-dependencies

renovate Bot commented Jun 22, 2026

Uh oh!

github-actions Bot commented Jun 22, 2026 •

edited

Loading

Uh oh!

renovate Bot commented Jun 23, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate Bot commented Jun 22, 2026

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

What's Changed

New Contributors

v9.3.0: 🥵

Support Mantine development

Pagination responsive layout

Text textWrap prop

use-splitter hook

Splitter component

CodeHighlight line numbers

OverflowList collapseFrom

Textarea bottomSection

Combobox floatingHeight

Menu submenu safe polygon

Menu search

Menu checkbox and radio items

Menu context menu

Popover context menu

Menu type-ahead navigation

Highlight accent and case insensitive matching

PieChart and DonutChart labelsType="name"

Tooltip merge arrow position

Popover preventPositionChangeWhenVisible default

Schedule getCurrentTime

What's Changed

New Contributors

Core Changes

Credits

Important Changes

Other Changes

Configuration

Uh oh!

github-actions Bot commented Jun 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

renovate Bot commented Jun 23, 2026

Edited/Blocked Notification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

`v9.3.0`: 🥵

github-actions Bot commented Jun 22, 2026 •

edited

Loading