fix(deps): update all non-major dependencies #159

renovate · 2025-01-06T00:56:28Z

This PR contains the following updates:

Package	Change	Type	Update
@hookform/resolvers (source)	`3.9.1` -> `3.10.0`	dependencies	minor
@prisma/client (source)	`6.1.0` -> `6.3.0`	dependencies	minor
@radix-ui/react-toast (source)	`1.2.4` -> `1.2.5`	dependencies	patch
@radix-ui/react-tooltip (source)	`1.1.6` -> `1.1.7`	dependencies	patch
@t3-oss/env-nextjs (source)	`^0.11.0` -> `^0.12.0`	dependencies	minor
jotai	`2.11.0` -> `2.11.2`	dependencies	patch
next (source)	`14.2.22` -> `14.2.23`	dependencies	patch
node (source)	`22.12.0` -> `22.13.1`		minor
pnpm (source)	`9.15.2` -> `9.15.4`	packageManager	patch
recharts	`2.15.0` -> `2.15.1`	dependencies	patch
remeda (source)	`2.19.0` -> `2.20.0`	dependencies	minor
tailwind-variants	`0.3.0` -> `0.3.1`	dependencies	patch

Release Notes

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

`v3.10.0`

Compare Source

Features

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

prisma/prisma (@prisma/client)

`v6.3.0`

Compare Source

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

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

Highlights

A brand new Prisma Studio

In this release we've included several great improvements to Prisma Studio's developer experience. You can learn all about the changes we've made in our release blog post, but here's a short list:

Prisma Studio is back in the Console

Fans of Prisma Data Browser rejoice! The new Prisma Studio is now in the Prisma Console and is available for all PostgreSQL and MySQL databases.

A new model viewer

Previously, switching from model to model in Prisma Studio would require backing all the way out to the model view, then digging in again. With our new UI, it's easy to switch from model to model while keeping your place.

A new editing experience

If you're trying to edit a given field in a model, Prisma Studio made it quite easy. However, if you're trying to edit every field in a given row, it could get quite annoying to keep scrolling left to right. Our new edit sidebar resolves that with the ability to edit all fields for a given row at once.

Clean up at the click of a button

When editing a number of models, it can get difficult to get back to a clean slate. In the new Prisma Studio, we've added a "Close all" button that puts you back to a fresh start.

Add `limit` to `updateMany()` and `deleteMany()`

Previously, limit has not existed as a valid option in top level updateMany() and deleteMany() queries. In 6.3.0 limit is now available in these queries, bringing their features more in line with other query types.

You can use limit like the following:

await prisma.user.deleteMany({
  where: { column: 'value' },
  limit: 100,
});

This will limit the number of deleted users to 100 at maximum.

Sort `generator` fields deterministically

In previous version of Prisma ORM, the fields inside of a generator block in your Prisma Schema were not deterministically sorted. This could lead to cases where prisma db pull could lead to re-ordering of fields.

In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first prisma db pull after you upgrade, but it will remain consistent afterwards.

Replace `NOT IN` with `NOT EXISTS` for PostgreSQL relation filters

In previous versions of Prisma ORM, when using the none or some relation filters, the SQL queries generated used NOT IN. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of IN with EXISTS in order to improve query performance.

A special thank you

We'd like to extend our heartfelt thanks to @loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #19249 and #17303. Their insights and partnership have been invaluable in improving our product.

If your team could benefit from dedicated support and tailored solutions, learn more about our enterprise support plan.

Fixes and improvements

Prisma Client

Add take or limit to updateMany() & deleteMany()

Prisma

Credits

Huge thanks to @WhyAsh5114 for their contributions to this release!

`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    @&#8203;id @&#8203;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 @&#8203;id @&#8203;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: 'alice@prisma.io',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}, {
  id: 23,
  name: 'Bob',
  email: 'bob@prisma.io',
  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:

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

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

`v1.2.5`

Compare Source

t3-oss/t3-env (@t3-oss/env-nextjs)

`v0.12.0`

Compare Source

Minor Changes

#299 b13d46b Thanks @EskiMojo14! - feat!: support standard schema

Validators can now be any validator that supports Standard Schema,
for example Zod & Valibot.

This feature comes with some breaking changes:
- If using Zod, the minimum required version is now 3.24.
- onValidationError now gets StandardSchemaV1.Issue[] instead of ZodError
#310 eb37304 Thanks @EskiMojo14! - feat!: add valibot presets

Presets using Valibot are now available using the /presets-valibot entrypoint.

This feature comes with some breaking changes:
- Zod presets have now been moved to /presets-zod.

Patch Changes

Updated dependencies [b13d46b, 7c09bc3, eb37304, bb80923, bb80923]:
- @t3-oss/env-core @0.12.0

pmndrs/jotai (jotai)

`v2.11.2`

Compare Source

There was a regression in v2.11.1, which is fixed in this patch.

What's Changed

fix(core): derived atom is not re-evaluated if it read between multiple set by @dai-shi in

New Contributors

@moonheekim0118 made their first contribution in https://github.com/pmndrs/jotai/pull/2961

Full Changelog: pmndrs/jotai@v2.11.1...v2.11.2

`v2.11.1`

Compare Source

Jotai v2.11.0 was a big change, and we faced some fundamental issues. It required time to reconsider the architecture from the ground up. We've added various tests, and this patch version should be more stable.

Having that said, we are still in the middle of the re-architecture. If you prefer to stay away from bleeding-edge features and encounter no bugs, feel free to keep using the previous versions.

Kudos to @dmaskasky