[Snyk] Upgrade @prisma/client from 5.1.1 to 5.11.0#6
Open
darlaterry wants to merge 1 commit into
Open
Conversation
Snyk has created this PR to upgrade @prisma/client from 5.1.1 to 5.11.0. See this package in npm: https://www.npmjs.com/package/@prisma/client See this project in Snyk: https://app.snyk.io/org/tdarlak-mwb/project/36dbf813-efbd-46a9-8e8c-ae121b489703?utm_source=github&utm_medium=referral&page=upgrade-pr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @prisma/client from 5.1.1 to 5.11.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version fixes:
SNYK-JS-ZOD-5925617
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
SNYK-JS-NEXT-6032387
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
SNYK-JS-POSTCSS-5926692
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: @prisma/client
Today, we are excited to share the
5.11.0stable release 🎉🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.
Highlights
Edge function support for Cloudflare and Vercel (Preview)
We’re thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview 🥳 As of this release, you can deploy your apps that are using Prisma ORM to:
In order to deploy to an edge function, you’ll need to use a compatible database driver (along with its Prisma driver adapter):
pgdriver (for traditional PostgreSQL databases)@ libsql/clientdriver (for SQLite databases hosted via Turso)Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.
You can also read more about it in the announcement blog post!
Performance improvements in nested
createoperationsWith Prisma ORM, you can create multiple new records in nested queries, for example:
In previous versions, Prisma ORM would translate this into multiple SQL
INSERTqueries, each requiring its own roundtrip to the database. As of this release, these nestedcreatequeries are optimized and theINSERTqueries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.With this change, using the nested
createoption to create multiple records effectively becomes equivalent to using a nestedcreateManyoperation (except thatcreateManyonly works with one-to-many relations, whereascreateworks both with one-to-many and many-to-many).Fixes and improvements
Prisma Client
console.log(new PrismaClient())enumthrows error (collationcp1250_czech_csor similar)NOTcondition leaks out of its desired boundsPrismaClientobject is slowprisma generateon Litespeed Web Server cPanel with sshtsc:Cannot find namespace 'debug'.pushmethod still unimplemented for scalar lists in CockroachDBInvalid charactererror persists on 5.10.1 in Prisma StudioruntimeDescriptionis not defined errorPrisma Migrate
npx prisma db pullwith DeepinOS 20.9GNU/LInuxLinux MintError: Invalid characterwhenschema.prismaincludes Chinese/Non-ASCII characters in a commentPrisma Engines
Today, we are issuing the
5.10.2patch release.Fix in Prisma CLI
Invalid charactererror persists on 5.10.1 in Prisma StudioToday, we are issuing the
5.10.1patch release.Fix in Prisma Client / Prisma CLI
Today, we are excited to share the
5.10.0stable release 🎉🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.
Highlights
Optimized relation queries in MySQL (Preview)
This release brings the optimizations for relation queries from the previous releases to MySQL as well! This means that by enabling the
relationJoinsPreview feature with themysqldatabase provider, you now also get access to therelationLoadStrategyoption in relation queries that let you choose whether you want to merged relations on the application- or database-level.If you enable the
relationJoinsPreview feature, you can choose between thejoinandqueryoptions:join(default): Sends a single query to the database and joins the data on the database-level.query: Sends multiple queries to the database and joins the data on the application-level.To get started, enable the Preview feature in your Prisma schema:
Be sure to re-generate Prisma Client afterwards:
And finally, specify the relation loading strategy for your relation query via the
relationLoadStrategyoption as follows:Note that in the example above, the
relationLoadStrategycould be omitted altogether becausejoinis used as the default value.A few notes about
relationLoadStrategysupport on MySQL:relationLoadStrategyis supported for MySQL v8.0.14 and higher. MariaDB is not supported.LATERALJOINs which are used on PostgreSQL).Configure transaction options in the
PrismaClientconstructorThis feature enables you to configure the following transaction options on a global level via the
PrismaClientconstructor:isolationLevel: Sets the transaction isolation level. By default, this is set to the value currently configured in your database.timeout: The maximum amount of time the interactive transaction can run before being canceled and rolled back. The default value is 5 seconds.maxWait: The maximum amount of time Prisma Client will wait to acquire a transaction from the database. The default value is 2 seconds.Here is an example of how you can set this value globally for all transactions:
Thanks a lot to our fantastic community member
@ tockn, who took the initiative to implement this feature in Prisma ORM 🎉Note that you can still override the global values by setting them on a particular transaction.
New
P2037code for “Too many database connections opened” errorsWe introduced a new error code for “Too many database connections opened” errors:
P2037. You can find all error codes in our documentation.Access the Prisma Data Platform via Prisma CLI
Now available in Early Access, you can manage your workspace and configure Prisma Accelerate and Prisma Pulse directly from the terminal.
Visit our docs to learn more about the integration and try it out for yourself!
Fixes and improvements
Prisma Client
Option::unwrap()on aNonevalue when using the relationJoins preview feature with driver adaptersPrisma.TransactionClientappears to be missing types@ prisma/clientin Next.js middleware$extendsalways returnanyError: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.t3.bookGenreTitledoes not exist in the current database"relationJoinspreview feature: calledOption::unwrap()on aNonevalueRead more
Read more
Today, we are issuing the
5.8.1patch release.Fix in Prisma Client
Read more