-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update prisma monorepo to v5 (major) #656
Conversation
1f414b2
to
c53b3f4
Compare
Any update on this? |
i'll check this during this weekend. |
65b5e7f
to
f9c4906
Compare
a3aec61
to
974ad87
Compare
6d1e3b4
to
fe04603
Compare
fe04603
to
b672853
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
## [2.0.0](v1.0.18...v2.0.0) (2023-08-01) ### ⚠ BREAKING CHANGES * **deps:** Upgrade prisma dependencies to v5 ### chore * **deps:** update prisma monorepo to v5 (major) ([#656](#656)) ([c19b45d](c19b45d))
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR contains the following updates:
^4.0
->^5.0.0
^4.0
->^5.0.0
^4.0
->^5.0.0
^4.0
->^5.0.0
Release Notes
prisma/prisma (@prisma/client)
v5.0.0
Compare Source
We’re excited to share the
5.0.0
release today 🎉Prisma
5.0.0
contains a lot of changes that improve Prisma’s performance, especially in serverless environments. If you want to learn more about the performance improvements, we wrote a blog post that sums up all the changes we made: Prisma 5: Faster by Default.As this is a major release, it includes a few breaking changes that might affect a small group of our users. Before upgrading, we recommend that you check out our upgrade guide to understand the impact on your application.
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Here’s a summary of the changes:
jsonProtocol
: improves communication between Prisma Client and the query engine, makes Prisma faster by default.fieldReference
: adds support for comparing columns of the same table.extendedWhereUnique
: adds support for non-unique columns insidewhere
clauses for queries that operate on unique records.rejectOnNotFound
propertycockroachdb
provider is now required when connecting to a CockroachDB databaseruntime/index.js
from the generated Prisma ClientbeforeExit
hook from the library engineprisma2
executableexperimentalFeatures
generator property in the Prisma schemamigration-engine
toschema-engine
A JSON-based protocol that improves Prisma’s performance
We’re thrilled to announce that the
jsonProtocol
Preview feature is now Generally Available. You can now remove the Preview feature flag from your schema after upgrading. We made the JSON-based wire protocol the default protocol used for communication between Prisma Client and the query engine.We introduced this feature in version 4.11.0 to improve Prisma’s performance. Previously, Prisma used a GraphQL-like protocol to communicate between Prisma Client and the query engine. Applications with larger schemas had higher CPU and memory consumption compared to smaller schemas which created a performance bottleneck.
The JSON-based wire protocol improves efficiency when Prisma Client is communicating with the query engine.
Removal of array shortcuts
We took the opportunity to remove some array shortcuts to make our typings more consistent and logical. These shortcuts were a way to add a single element as a value to an array-based operator instead of wrapping a single element in an array. We will now require array values for the following:
OR
operator shortcutsin
andnotIn
operator shortcutspath
field shortcutHere’s an example query using the
OR
operator shortcut for a single element;We recommend taking a look at the upgrade guide to learn how you can update your queries to work in Prisma 5.
Support for comparing multiple columns
We’re excited to announce that the
fieldReference
Preview feature is now stable and Generally Available. This means you can use this feature without the Preview feature flag in your Prisma schema.We first introduced this feature in 4.5.0 to add the ability to compare columns on the same table. For example, the following query returns records where the
quantity
value is less than thewarnQuantity
of a product:To learn more about this feature, refer to our documentation.
Support for filtering non-unique columns in queries for a unique record
We’re excited to announce the
extendedWhereUnique
Preview feature is now Generally Available. This means you can use the feature without the Preview feature flag in the Prisma schema.We first introduced this feature in version 4.5.0 to add support for non-unique columns inside
where
clauses for queries that operate on unique records, such asfindUnique
,update
, anddelete
, which was previously not possible.For example, consider the following model:
You can filter on non-unique columns such as the
version
field as follows:To learn more about this feature, refer to our documentation.
Minimum Node.js version change to 16.13.0
The minimum version of Node.js Prisma supports is
16.13.0
. If you're using an earlier version of Node.js, you will need to upgrade your Node.js version.Refer to our system requirements for the minimum versions Prisma requires.
Minimum TypeScript version change to 4.7
The minimum version of TypeScript Prisma supports is 4.7. If your project is using an earlier version of TypeScript, you will need to upgrade your TypeScript version.
Refer to our system requirements for the minimum versions Prisma requires.
Minimum PostgreSQL version change to 9.6
The minimum version of PostgreSQL Prisma supports is version 9.6. If you’re either using 9.4 or 9.5, you will need to update your PostgreSQL version to at least 9.6.
Refer to our system requirements for the minimum database versions Prisma requires.
Prisma Client embedded SQLite version upgrade
We upgraded the embedded version of SQLite from 3.35.4 to 3.41.2. We do not anticipate any breaking changes or changes needed in projects using SQLite. However, if you’re using SQLite, especially with raw queries that might go beyond Prisma's functionality, make sure to check the SQLite changelog.
Removal of
rejectOnNotFound
propertyIn version 5.0.0, we removed the
rejectOnNotFound
parameter from Prisma Client that was deprecated in version 4.0.0. We removed this feature to provide better type-safety using thefindUniqueOrThrow
andfindFirstOrThrow
methods as well have a consistent API.If you are using the
rejectOnNotFound
parameter we recommend either:findFirstOrThrow
orfindUniqueOrThrow
methods if enabled at a query-levelfindFirstOrThrow
andfindUniqueOrThrow
model methods with your custom error handling if enabled at the client-levelWe recommend taking a look at the upgrade guide for more information on how to adapt your application if you’re using
rejectOnNotFound
.cockroachdb
provider is now required when connecting to a CockroachDB databasePrior to adding explicit support for CockroachDB with the
cockroachdb
provider in 3.9.0, it was possible to use the PostgreSQL provider when working with CockroachDB databases.We’re now making it mandatory to use the CockroachDB connector when working with CockroachDB databases. CockroachDB and PostgreSQL have a few differences such as the available native types which impact the generated migrations.
If you were using the PostgreSQL connector to work with CockroachDB, take a look at the upgrade guide to learn how you can update your connector.
Removal of the generated
runtime/index.js
file from Prisma ClientWith Prisma 5, we removed the
runtime/index.js
file from Prisma Client. If you were using APIs fromruntime/index.js
, such asDecimal
,PrismaClientKnownRequestError
,NotFoundError
,PrismaClientUnknownRequestError
, we recommend updating your imports:We recommend taking a look at the upgrade guide to learn how you can migrate to Prisma 5
Removal of the
beforeExit
hook from thelibrary
query engineWe removed the
beforeExit
hook from the defaultlibrary
Query Engine. We recommend using the built-in Node.js exit events.-prisma.$on('beforeExit', () => { /* your code */ }) // Replacements process.on('beforeExit', () => { /* your code */ }) process.on('exit', exitHandler) process.on('SIGINT', exitHandler) process.on('SIGTERM', exitHandler) process.on('SIGUSR2', exitHandler)
We recommend taking a look at the upgrade guide to learn how you can migrate to Prisma 5.
Removal of deprecated
prisma2
executableWhen we released Prisma 2, the
prisma2
executable was used to differentiate it from Prisma 1. In a later release, theprisma2
CLI took over theprisma
executable name.The
prisma2
executable has been deprecated for a while and will now be removed. If you’re usingprisma2
in your scripts, replace it withprisma
.Removal of deprecated flags in the Prisma CLI
We removed the following deprecated flags in the Prisma CLI:
--preview-feature
: used in theprisma db execute
,prisma db seed
, andprisma migrate diff
commands--experimental
and--early-access-feature
: used in theprisma migrate
commands such asprisma migrate dev
--force
: forprisma db push
. The--force
flag was replaced by--accept-data-loss
in version 2.17.0--experimental-reintrospection
and--clean
: forprisma db pull
In the event you’re using one of these flags, we recommend removing the flags.
Removal of deprecated
experimentalFeatures
generator propertyIn this release, we removed the
experimentalFeatures
property that used to be in the generator property in the Prisma schema but has been renamed topreviewFeatures
for a long time now. If you’re still using this property, you can either manually rename it topreviewFeatures
or use the VS Code action to rename it if you’re using the latest version of the Prisma VS Code extension.Renamed
migration-engine
toschema-engine
In this release, we renamed the
migration-engine
, responsible for running introspection and migration commands, toschema-engine
. For the majority of our users, no changes will be required. However, if you explicitly include or exclude the engine files you will need to update your code references. Refer to the upgrade guide for more information.Fixes and improvements
Prisma Client
create
call<Model>RelationFilterInput
does not take nullability into accountOR
broke after opting in tojsonProtocol
feature.jsonProtocol
)jsonProtocol
GAbinaries.prisma.sh/all_commits/
rejectOnNotFound
runtime/index.js
bundle from clientprisma dev
commandphotonResolver
andprovider=photonjs
handlingfieldReference
GAextendedWhereUnique
GAprisma2
"executable"$extend
in factory function whencompilerOptions.composite
istrue
query
type tonever
The package "path" wasn't found on the file system but is built into node
undefined
explicitly passed toselect
/include
Prisma Migrate
provider = "postgresql"
an errorexperimentalFeatures
generator propertydb pull
: Remove the version checker from introspectiondoctor
commandexperimentalFeatures
generator propertyexperimentalFeatures
Language tools (e.g. VS Code)
experimentalFeatures
as obsoleteCredits
Huge thanks to @michaelpoellath, @RobertCraigie, @Coder246, @RDIL, @oohwooh, @rqres, @zhiyan114, @spudly, @hayes, @boennemann, @DongGunYoon for helping!
📺 Join us for another "What's new in Prisma" live stream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.
The stream takes place on YouTube on Thursday, July 13 at 5 pm Berlin | 8 am San Francisco.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Mend Renovate. View repository job log here.