Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@codemirror/commands	6.7.1 -> 6.8.0
@codemirror/lang-markdown	6.3.1 -> 6.3.2
@hookform/resolvers (source)	3.9.1 -> 3.10.0
@mantine/core (source)	7.15.2 -> 7.15.3
@mantine/dates (source)	7.15.2 -> 7.15.3
@mantine/hooks (source)	7.15.2 -> 7.15.3
@mantine/modals (source)	7.15.2 -> 7.15.3
@mantine/notifications (source)	7.15.2 -> 7.15.3
@next/bundle-analyzer (source)	15.1.3 -> 15.1.4
@next/env (source)	15.1.3 -> 15.1.4
@prisma/client (source)	6.1.0 -> 6.2.1
eslint-config-next (source)	15.1.3 -> 15.1.4
glob	11.0.0 -> 11.0.1
i18next (source)	24.2.0 -> 24.2.1
lucide-react (source)	^0.469.0 -> ^0.471.0
next (source)	15.1.3 -> 15.1.4
prisma (source)	6.1.0 -> 6.2.1
react-markdown	9.0.1 -> 9.0.3
stylelint (source)	16.12.0 -> 16.13.0
typescript (source)	5.7.2 -> 5.7.3

---

Release Notes

codemirror/commands (@​codemirror/commands)

v6.8.0

Compare Source

New features

The new cursorGroupForwardWin and selectGroupForwardWin commands implement Windows-style forward motion by group.

codemirror/lang-markdown (@​codemirror/lang-markdown)

v6.3.2

Compare Source

Bug fixes

Make Markdown-specific commands return false inside fenced code.

Fix an infinite loop caused by insertNewlineContinueMarkup.

react-hook-form/resolvers (@​hookform/resolvers)

v3.10.0

Compare Source

Features

• update to effect 3.10 (#​729) (10aca41)

mantinedev/mantine (@​mantine/core)

v7.15.3

Compare Source

What's Changed

• [@mantine/charts] BarChart: Fix textColor prop being passed down as attribute to the DOM node
• [@mantine/core] TypographyStylesProvider: Fix incorrect top and bottom margins of first and last elements (#​7334)
• [@mantine/core] Transition: Fix some transitions being incompatible with headless mode (#​7306)
• [@mantine/dates] DateTimePicker: Set milliseconds to 0 on the result date object (#​7328)
• [@mantine/dates] Fix hasNextLevel prop type leak to DateTimePicker component (#​7319)
• [@mantine/core] Avatar: Change initials function to use the full name to generate color (#​7322)
• [@mantine/hooks] use-merged-ref: Add support for ref cleanup function in React 19 (#​7304)
• [@mantine/hooks] use-debounced-callback: Add flush method to returned callback (#​7272)
• [@mantine/dates] Improve compatibility with dayjs plugins in all components (#​7302)
• [@mantine/core] Update peer dependencies to support React 19 (#​7321)

New Contributors

• @​baravak made their first contribution in https://github.com/mantinedev/mantine/pull/7302
• @​scamden made their first contribution in https://github.com/mantinedev/mantine/pull/7272
• @​YukiKoNeko made their first contribution in https://github.com/mantinedev/mantine/pull/7322
• @​yuki0410-dev made their first contribution in https://github.com/mantinedev/mantine/pull/7319
• @​zoubingwu made their first contribution in https://github.com/mantinedev/mantine/pull/7323
• @​clarknova made their first contribution in https://github.com/mantinedev/mantine/pull/7328

Full Changelog: mantinedev/mantine@7.15.2...7.15.3

vercel/next.js (@​next/bundle-analyzer)

v15.1.4

Compare Source

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

Core Changes

• backport: force module format for virtual client-proxy (#​74608)
• Fix prerender tags when notFound is called (#​74607)
• Use provided waitUntil for pending revalidates (#​74604)
• Feature: next/image: add support for images.qualities in next.config (#​74588)
• Chore: docs: add missing search: '' on remotePatterns (#​74587)
• Chore: docs: update version history of next/image (#​73923) (#​74570)
• Chore: next/image: improve imgopt api bypass detection for unsupported images (#​74569)

Credits

Huge thanks to @​ and @​ for helping!

prisma/prisma (@​prisma/client)

v6.2.1

Compare Source

Today we are releasing the 6.2.1 patch release to address an issue with some of the omitApi preview feature checks having been accidentally omitted when making the feature GA. Now it is fully functional without the preview feature flag.

Changes

• https://github.com/prisma/prisma/pull/25997

v6.2.0

Compare Source

Today we're releasing Prisma ORM version 6.2.0 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

We have a number of new features in this version, including support for json and enum fields in SQLite, a new updateManyAndReturn function, support for ULID values, as well as the promotion of the omit feature from Preview to Generally Availability.

Highlights

Excluding fields via omit is now production-ready

Our number one requested feature is out of Preview and Generally Available. In 6.2.0, you no longer need to add omitApi to your list of Preview features:

generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["omitApi"]
}

As a refresher: omit allows you to exclude certain fields from being returned in the results of your Prisma Client queries.

You can either do this locally, on a per-query level:

const result = await prisma.user.findMany({
  omit: {
    password: true,
  },
});

Or globally, to ensure a field is excluded from all queries of a certain model:

const prisma = new PrismaClient({
  omit: {
    user: {
      password: true
    }
  }
})

// The password field is excluded in all queries, including this one
const user = await prisma.user.findUnique({ where: { id: 1 } })

For more information on omit, be sure to check our documentation.

json and enum fields in SQLite

Previous to this version, you could not define json and enum fields in your Prisma schema when using SQLite. The respective GitHub issues have been among the most popular ones in our repo, so with our new approach to open-source governance, we finally got to work and implemented these.

Working with JSON and Enum fields works similarly to other database providers, here’s an example:

datasource db {
  provider = "sqlite"
  url      = "file:./dev.db"
}

model User {
  id   Int    @​id @​default(autoincrement())
  name String
  role Role  
  data Json
}

enum Role {
  Customer
  Admin 
}

Support for auto-generated ULID values

Similar to cuid2 support released in ORM version 6.0.0, we are now adding support for Universally Unique Lexicographically Sortable Identifiers (or short: ULIDs 😄) in version 6.2.0. A ULID value is a 26-character alphanumeric string, e.g. 01GZ0GZ3XARH8ZP44A7TQ2W4ZD.

With this new feature, you can now create records with auto-generated ULID values for String fields:

model User {
  id String @​id @​default(ulid())  
}

New batch function: updateManyAndReturn

updateMany allows you to update many records in your database, but it only returns the count of the affected rows, not the resulting rows themselves. With updateManyAndReturn you are now able to achieve this:

const users = await prisma.user.updateManyAndReturn({
  where: {
    email: {
      contains: 'prisma.io',
    }
  },
  data: {
    role: 'ADMIN'
  }
})

This call to updateManyAndReturn will now return the actual records that have been updated in the query:

[{
  id: 22,
  name: 'Alice',
  email: '[email protected]',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}, {
  id: 23,
  name: 'Bob',
  email: '[email protected]',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}]

Please note that like createManyAndReturn, updateManyAndReturn is only supported in PostgreSQL, CockroachDB, and SQLite.

Fixed runtime error in Node.js v23

While not officially supported, we understand that a lot of you like to be on the latest Node.js version — so we fixed an error that only occurred on Node.js 23. Happy coding ✌️

Prisma is hiring 🤝

Join us at Prisma to work on the most popular TypeScript ORM and other exciting products like the first serverless database built on unikernels!

We currently have two open roles in our Engineering team:

• Senior Software Engineer (Prisma ORM)
• Senior Software Engineer (Prisma Data Platform)

If these don’t fit, you can still check out our jobs page and send a general application.

vercel/next.js (eslint-config-next)

v15.1.4

Compare Source

isaacs/node-glob (glob)

v11.0.1

Compare Source

i18next/i18next (i18next)

v24.2.1

Compare Source

• Standardize null/undefined checks across codebase 2275
• fix(typescript): make TFunction augmentable again 2279, fixes 2278

lucide-icons/lucide (lucide-react)

v0.471.0: Dynamic Icon component Lucide React and new icons 0.471.0

Compare Source

New Dynamic Icon Component (lucide-react)

This is an easier approach than the previous dynamicIconImports we exported in the library. This one supports all environments.
We removed the examples in the docs of how you can make a dynamic icon yourself with a dedicated DynamicIcon component.
This one fetches the icon data itself and renders it instead of fetching the Icon component from the library.
This makes it more flexible with all the frontend frameworks and libraries that exist for React.

🚨
Not recommended for regular applications that work fine with the regular static icon components.
Using the dynamic icon component increases build time, separate bundles, and separate network requests for each icon.

How to use

DynamicIcon is useful for applications that want to show icons dynamically by icon name, for example when using a content management system where icon names are stored in a database.

const App = () => (
  <DynamicIcon name="camera" color="red" size={48} />
);

Possible Breaking changes

We have switched to the "exports" property in package.json. This can cause issues if you have directly imported scripts from the package. Please open an issue if we need to refine this export map.

New icons 🎨

• triangle-dashed (#​2652) by @​Yohh

v0.470.0: New icons 0.470.0

Compare Source

New icons 🎨

• house-wifi (#​2723) by @​akshaymemane

Modified Icons 🔨

• rat (#​2692) by @​jguddas

remarkjs/react-markdown (react-markdown)

v9.0.3

Compare Source

(same as 9.0.2 but now with d.ts files)

Full Changelog: remarkjs/react-markdown@9.0.2...9.0.3

v9.0.2

Compare Source

Types

• b151a90 Fix types for React 19
  by @​remcohaszing in https://github.com/remarkjs/react-markdown/pull/879
• 6962af7 Add declaration maps
• aa5933b Refactor to use @import to import types
  by @​remcohaszing in https://github.com/remarkjs/react-markdown/pull/836

Miscellaneous

• 9eb589e Fix typo in changelog
  by @​NicholasWilsonDEV in https://github.com/remarkjs/react-markdown/pull/874
• 515bf19 Fix typo
  by @​deep-lyra in https://github.com/remarkjs/react-markdown/pull/868

Full Changelog: remarkjs/react-markdown@9.0.1...9.0.2

stylelint/stylelint (stylelint)

v16.13.0

Compare Source

It adds 3 rules to help you write error-free at-rules and 2 rules to warn you about deprecated CSS features. We've turned these rules on in our standard config.

It also adds new rule options, a feature to display how long rules take, lax autofix and support for messageArgs in more rules. It fixes 7 bugs.

Lastly, we've made a deprecation that may affect some plugins. We've updated our docs for plugin authors and end users on how to silence deprecation warnings.

• Deprecated: ambiguous position arguments passed to utils.report() (#​8244) (@​romainmenke).
• Added: lax/strict values to the fix Node.js API option and CLI flag (#​8106) (@​ryo-manba).
• Added: support for profiling rule performance via the TIMING environment variable (#​8108) (@​ryo-manba).
• Added: at-rule-descriptor-no-unknown rule (#​8197) (@​ryo-manba).
• Added: at-rule-descriptor-value-no-unknown rule (#​8211) (@​ryo-manba).
• Added: at-rule-no-deprecated rule (#​8251) (@​jeddy3).
• Added: at-rule-prelude-no-invalid rule (#​8268) (@​ryo-manba).
• Added: declaration-property-value-keyword-no-deprecated rule (#​8223) (@​Mouvedia).
• Added: "ignore": ["at-rule-preludes", "declaration-values"] to string-no-newline (#​8214) (@​ryo-manba).
• Added: messageArgs to declaration-property-value-no-unknown, font-family-name-quotes, font-family-no-duplicate-names, function-calc-no-unspaced-operator, import-notation, media-feature-name-unit-allowed-list, selector-attribute-quotes and selector-pseudo-element-colon-notation (#​8285 & #​8252) (@​Mouvedia).
• Fixed: deprecation warnings to only display once per (custom) rule (#​8265) (@​romainmenke).
• Fixed: *-no-vendor-prefix message ambiguity (#​8239) (@​Mouvedia).
• Fixed: at-rule-(dis)allowed-list, at-rule-no-vendor-prefix, at-rule-property-required-list message argument (#​8277) (@​Mouvedia).
• Fixed: at-rule-property-required-list message for inclusion of properties and descriptors (#​8207) (@​jeddy3).
• Fixed: at-rule-* false positives and negatives for @charset rule (#​8215) (@​jeddy3).
• Fixed: declaration-property-value-no-unknown false positives for descriptors (#​8240) (@​jeddy3).
• Fixed: property-(dis)allowed-list false negatives for custom properties, use /^--/ to (dis)allow them (#​8209) (@​fbasmaison-lucca).
• Fixed: property-no-unknown false positives for descriptors (#​8203) (@​jeddy3).
• Fixed: selector-pseudo-class-no-unknown false positives for deprecated pseudo-classes (#​8264) (@​Mouvedia).
• Fixed: selector-type-case false positives for hatchPath (#​8264) (@​Mouvedia).
• Fixed: selector-type-no-unknown false positives for shadow, hatch and hatchpath (#​8264) (@​Mouvedia).

microsoft/TypeScript (typescript)

v5.7.3

Compare Source

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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 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.