fix(deps): update prisma monorepo to v6.2.1 #757
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.1.0
->6.2.1
6.1.0
->6.2.1
Release Notes
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
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
andenum
fields in SQLite, a newupdateManyAndReturn
function, support for ULID values, as well as the promotion of theomit
feature from Preview to Generally Availability.Highlights
Excluding fields via
omit
is now production-readyOur 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:
Or globally, to ensure a field is excluded from all queries of a certain model:
For more information on
omit
, be sure to check our documentation.json
andenum
fields in SQLitePrevious to this version, you could not define
json
andenum
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:
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: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. WithupdateManyAndReturn
you are now able to achieve this:This call to
updateManyAndReturn
will now return the actual records that have been updated in the query: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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.