fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@dnd-kit/core (source)	6.2.0 -> 6.3.1					dependencies	minor
@headlessui/react (source)	2.1.10 -> 2.2.0					dependencies	minor
@prisma/client (source)	5.21.1 -> 5.22.0					dependencies	minor
@radix-ui/react-toast (source)	1.2.2 -> 1.2.4					dependencies	patch
@radix-ui/react-tooltip (source)	1.1.4 -> 1.1.6					dependencies	patch
jotai	2.10.3 -> 2.11.0					dependencies	minor
next (source)	14.2.15 -> 14.2.22					dependencies	patch
next-auth (source)	4.24.10 -> 4.24.11					dependencies	patch
next-intl (source)	3.25.3 -> 3.26.3					dependencies	minor
node (source)	22.11.0 -> 22.12.0						minor
pnpm (source)	9.12.2 -> 9.15.2					packageManager	minor
postgres	17.0 -> 17.2						minor
react-hook-form (source)	7.53.2 -> 7.54.2					dependencies	minor
react-icons	5.3.0 -> 5.4.0					dependencies	minor
recharts	2.14.1 -> 2.15.0					dependencies	minor
remeda (source)	2.17.4 -> 2.19.0					dependencies	minor
superjson	2.2.1 -> 2.2.2					dependencies	patch
swr (source)	2.2.5 -> 2.3.0					dependencies	minor
tailwind-variants	^0.2.1 -> ^0.3.0					dependencies	minor
zod (source)	3.23.8 -> 3.24.1					dependencies	minor

---

Release Notes

clauderic/dnd-kit (@​dnd-kit/core)

v6.3.1

Compare Source

Patch Changes

• #​1555 62f632a Thanks @​clauderic! - Added Tab to the list of default key codes that end a drag and drop operation. Can be customized by passing in a custom list of keyCodes to the KeyboardSensor options.

v6.3.0

Compare Source

Minor Changes

• #​1539 0c6a28d Thanks @​irobot! - Make it possible to add visual cues when using activation constraints.

Context

Activation constraints are used when we want to prevent accidental dragging or when
pointer press can mean more than "start dragging".

A typical use case is a button that needs to respond to both "click" and "drag" gestures.
Clicks can be distinguished from drags based on how long the pointer was
held pressed.

The problem

A control that responds differently to a pointer press based on duration or distance can
be confusing to use -- the user has to guess how long to keep holding or how far to keep
dragging until their intent is acknowledged.

Implementing such cues is currently possible by attaching extra event listeners so that
we know when a drag is pending. Furthermore, the listener needs to have access to
the same constraints that were applied to the sensor initiating the drag. This can be
made to work in simple cases, but it becomes error-prone and difficult to maintain in
complex scenarios.

Solution

This changeset proposes the addition of two new events: onDragPending and onDragAbort.

onDragPending

A drag is considered to be pending when the pointer has been pressed and there are
activation constraints that need to be satisfied before a drag can start.

This event is initially fired on pointer press. At this time offset (see below) will be
undefined.

It will subsequently be fired every time the pointer is moved. This is to enable
visual cues for distance-based activation.

The event's payload contains all the information necessary for providing visual feedback:

export interface DragPendingEvent {
  id: UniqueIdentifier;
  constraint: PointerActivationConstraint;
  initialCoordinates: Coordinates;
  offset?: Coordinates | undefined;
}

onDragAbort

A drag is considered aborted when an activation constraint for a pending drag was violated.
Useful as a prompt to cancel any visual cue animations currently in progress.
Note that this event will not be fired when dragging ends or is canceled.

tailwindlabs/headlessui (@​headlessui/react)

v2.2.0

Compare Source

Added

• Add React 19 support (#​3543)

prisma/prisma (@​prisma/client)

v5.22.0

Compare Source

Today, we are excited to share the 5.22.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Further Tracing Improvements

In our ongoing effort to stabilize the tracing Preview feature, we’ve made our spans compliant with OpenTelemetry Semantic Conventions for Database Client Calls. This should lead to better compatibility with tools such as DataDog and Sentry.

We’ve also included numerous bug fixes that should make this Preview feature easier to work with.

Metrics bug fix

Occasionally, connection pool metrics would become negative or grow unbounded. In this release, connection pool metrics should stay consistent.

Connection Pool Timeout fix

In a specific case, there could be issues where fetching a new connection from the connection pool would time out, regardless of the state of the application and connection pool. If you have experience connection pool issues accessing a PostgreSQL database with TLS encryption in a resource-constrained environment (such as Function-as-a-Service offerings or very small VPS) this should resolve those issues.

Special thanks to @​youxq for their pull request and help resolving this issue!

Join us

Looking to make an impact on Prisma in a big way? We're hiring!

Learn more on our careers page: https://www.prisma.io/careers

Fixes and improvements

Prisma Migrate

• removing @unique in schema.prisma does not generate SQL to do so

Prisma

• Prisma generate randomly fails on Ubuntu due to missing internal .so libquery_engine-debian-openssl-1.1.x.so.node
• Timed out fetching a new connection from the connection pool.
• Some prisma:engine:connection spans have no parent
• Query-related spans outside of prisma:engine:itx_runner are disconnected from the tree
• Tracing with dataproxy/mini-proxy: itx_runner span and it's children are missing sometimes
• Incorrect OpenTelemetry span reported by Prisma
• OTEL spans are not recognised as spans from a database
• SQL Injection bug - D1 adaptor throws "Conversion failed: expected a datetime string in column" when string column contains any ISO date
• Prisma generate randomly fails on Ubuntu due to missing internal .so libquery_engine-debian-openssl-1.1.x.so.node

Credits

Huge thanks to @​tmm1, @​Takur0, @​hinaloe, @​andyjy, and @​youxq for helping!

radix-ui/primitives (@​radix-ui/react-toast)

v1.2.4

Compare Source

v1.2.3

Compare Source

pmndrs/jotai (jotai)

v2.11.0

Compare Source

There are no public API changes, but some internal behaviors have been improved. Now, atom updates are batched in a single write, which might provide a performance benefit in certain edge cases. This feature has been requested actually for a long time, and it's finally implemented. See also #​2782.

What's Changed

• refactor(store): rename pending to batch by @​dai-shi in https://github.com/pmndrs/jotai/pull/2868
• lazy recomputeDependents by @​dmaskasky in https://github.com/pmndrs/jotai/pull/2827
• fix(store): robust flush batch by @​dmaskasky in https://github.com/pmndrs/jotai/pull/2871
• fix(store): refactor batch priority by @​dmaskasky in https://github.com/pmndrs/jotai/pull/2875
• feat: dev store with unstable_derive by @​dai-shi in https://github.com/pmndrs/jotai/pull/2852

New Contributors

• @​rainagalbiati-turngate made their first contribution in https://github.com/pmndrs/jotai/pull/2882
• @​leweyse made their first contribution in https://github.com/pmndrs/jotai/pull/2883

Full Changelog: pmndrs/jotai@v2.10.4...v2.11.0

v2.10.4

Compare Source

A minor improvement for some edge cases. (For more information, see #​2789.)

What's Changed

• fix(store): do not recompute unmounted atoms eagerly by @​dai-shi in https://github.com/pmndrs/jotai/pull/2849

New Contributors

• @​rmillio made their first contribution in https://github.com/pmndrs/jotai/pull/2832
• @​sukvvon made their first contribution in https://github.com/pmndrs/jotai/pull/2851

Full Changelog: pmndrs/jotai@v2.10.3...v2.10.4

vercel/next.js (next)

v14.2.22

Compare Source

v14.2.21

Compare Source

v14.2.20

Compare Source

v14.2.19

Compare Source

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

Core Changes

• ensure worker exits bubble to parent process (#​73433)
• Increase max cache tags to 128 (#​73125)

Misc Changes

• Update max tag items limit in docs (#​73445)

Credits

Huge thanks to @​ztanner and @​ijjk for helping!

v14.2.18

Compare Source

v14.2.17

Compare Source

v14.2.16

Compare Source

nextauthjs/next-auth (next-auth)

v4.24.11

Compare Source

amannn/next-intl (next-intl)

v3.26.3

Compare Source

Bug Fixes

• Add missing deprecation warnings for next-intl@4.0 (#​1485) (1d60d08) – by @​amannn

v3.26.2

Compare Source

Bug Fixes

• Support t.has when getTranslations is called with an object argument (#​1616) (64895a2), closes /github.com/amannn/next-intl/discussions/437#discussioncomment-11593318 – by @​amannn

v3.26.1

Compare Source

Bug Fixes

• Use new domain next-intl.dev in links (#​1601) (40a9a77) – by @​amannn

v3.26.0

Compare Source

Features

• Support React 19 (#​1597) (e0ffe29) – by @​amannn

nodejs/node (node)

v22.12.0

Compare Source

pnpm/pnpm (pnpm)

v9.15.2: pnpm 9.15.2

Compare Source

Patch Changes

• Fixed publish/pack error with workspace dependencies with relative paths #​8904. It was broken in v9.4.0 (398472c).
• Use double quotes in the command suggestion by pnpm patch on Windows #​7546.
• Do not fall back to SSH, when resolving a git-hosted package if git ls-remote works via HTTPS #​8906.
• Improve how packages with blocked lifecycle scripts are reported during installation. Always print the list of ignored scripts at the end of the output. Include a hint about how to allow the execution of those packages.

Platinum Sponsors

Gold Sponsors

v9.15.1

Compare Source

v9.15.0

Compare Source

v9.14.4

Compare Source

v9.14.3

Compare Source

v9.14.2

Compare Source

Patch Changes

• pnpm publish --json should work #​8788.

Platinum Sponsors

Gold Sponsors

v9.14.1

Compare Source

Minor Changes

• Added support for pnpm pack --json to print packed tarball and contents in JSON format #​8765.

Patch Changes

• pnpm exec should print a meaningful error message when no command is provided #​8752.
• pnpm setup should remove the CLI from the target location before moving the new binary #​8173.
• Fix ERR_PNPM_TARBALL_EXTRACT error while installing a dependency from GitHub having a slash in branch name #​7697.
• Don't crash if the use-node-version setting is used and the system has no Node.js installed #​8769.
• Convert settings in local .npmrc files to their correct types. For instance, child-concurrency should be a number, not a string #​5075.
• pnpm should fail if a project requires a different package manager even if manage-package-manager-versions is set to true.
• pnpm init should respect the --dir option #​8768.

Platinum Sponsors

Gold Sponsors

v9.14.0

Compare Source

v9.13.2: pnpm 9.13.2

Compare Source

Patch Changes

• Detection of circular peer dependencies should not crash with aliased dependencies #​8759. Fixes a regression introduced in the previous version.
• Fix race condition of symlink creations caused by multiple parallel dlx processes.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v9.13.1: pnpm 9.13.1

Compare Source

Patch Changes

• Fixed some edge cases where resolving circular peer dependencies caused a dead lock #​8720.

Platinum Sponsors

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.