fix(deps): update prisma monorepo to v6.5.0 #9548
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.4.1->6.5.06.4.1->6.5.06.4.1->6.5.06.4.1->6.5.0Release Notes
prisma/prisma (@prisma/client)
v6.5.0Compare Source
Today, we are excited to share the
6.5.0stable release 🎉🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟
Highlights
Databases can only be reset manually and explicitly
In previous versions, if Prisma ORM determined that a
migratecommand could not be applied cleanly to the underlying database, you would get a message like this one:While "no" was the default, we've determined that having this prompt in the first place was a mistake. In this version we're removing the prompt entirely and instead exiting with an appropriate error message.
To get the previous behavior, you will need to run
prisma migrate resetdirectly.Support for
prisma.config.tsin Prisma StudioWe've expanded support for our
prisma.config.tsfile to include Prisma Studio!To use the new config file, including the ability to connect to driver adapter enabled databases with Prisma Studio, add a
studioblock to yourprisma.config.tsfile:Notice how this looks a little different from last release! Instead of an
@prisma/configpackage there’s now two different options:defineConfighelper exported byprisma/config.PrismaConfigutility type exported byPrisma.All the relevant info for the
prisma.config.tsfile, including these new ways of defining your config, can be found in our docs.Allow for chaining
$onand$extends.In previous versions of Prisma ORM, the return type of the
$onclient method wasvoid. This did not allow for chaining$on()and$extends()calls, as$onis not available on extended clients.In this version we've resolved this issue and
$onwill now return the modified Prisma Client.Community fixes
We have a number of community-submitted fixes that improve Prisma ORM:
Prisma is hiring
Join us at Prisma and work on our TypeScript ORM (now faster than ever) and our Cloud products like Prisma Postgres (now in GA!)
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.
Enterprise support
Prisma offers an enterprise support plan for Prisma ORM. Get direct help from our team and a joint slack channel! With Prisma ORM 7 on the horizon this is a great time to upgrade your support today.
Credits
Thank you to @overbit, @RaHehl, @toniopelo, and @de-novo for your contributions to this release!
Configuration
📅 Schedule: Branch creation - "before 7am on Tuesday,before 7am on Wednesday" in timezone Australia/Sydney, 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.
🔕 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.