This repository has been archived by the owner on Feb 6, 2023. It is now read-only.
[Snyk] Upgrade prisma from 4.0.0 to 4.8.1 #95
Conversation
This file contains 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
Snyk has created this PR to upgrade prisma from 4.0.0 to 4.8.1. See this package in npm: https://www.npmjs.com/package/prisma See this project in Snyk: https://app.snyk.io/org/ntechnology0/project/186ab756-60ac-4f67-8b70-3232e98904ba?utm_source=github&utm_medium=referral&page=upgrade-pr
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Snyk has created this PR to upgrade prisma from 4.0.0 to 4.8.1.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
✨ Snyk has automatically assigned this pull request, set who gets assigned.
ℹ️ 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.
Release notes
Package name: prisma
Today, we are issuing the
4.8.1patch release.Fix in Prisma Client
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Improved serverless experience — smaller engines size
In this release, we have decreased the size of our engine files by an average of 50%. The size of the Query Engine used on Debian, with OpenSSL 3.0.x, for example, went from 39MB to 14MB. We will also remove some smaller engines to decrease the total size in future versions.
Additionally, we have started optimizing how the Prisma schema is loaded in Prisma Client. You should notice a considerable improvement when executing the first query if you're working with a bigger schema with many models and relations.
We will continue investing in this direction in the next releases and further improve the experience with Prisma and serverless environments.
Multi-schema support for CockroachDB (Preview)
We're pleased to share that this release adds Preview support for multi-schema for CockroachDB. 🎉
This release adds support for:
If you already have a CockroachDB database using multiple schemas, you can quickly get up and running set up multiple schemas by:
schemasproperty in thedatasourceblockprisma db pullYou can further evolve your database schema using the multi-schema Preview feature by using
prisma migrate dev.For further details, refer to our documentation and let us know what you think in this GitHub issue.
Improved OpenSSL 3.x support
Prisma now supports OpenSSL 3 builds for Linux Alpine on
x86_64architectures. This particularly impacts users running Prisma onnode:alpineandnode:lts-alpineDocker images. The images are based on an Alpine version that ships with OpenSSL 3.0.x, which isn’t compatible with OpenSSL 1.1.x (already supported by Prisma). You can read more details about it in this GitHub comment.We also have rewritten our OpenSSL version detection logic, making it future-proof. We now expect Prisma to support systems running with any OpenSSL 3 minor versions out of the box.
Fixes and improvements
Prisma
Uuidhas no default operator class.migrate resetonly resets first schemamultiSchemaintrospectionmigrate devdoes not detect drift between database schema and migration history formultiSchemaPrisma Migrate
multiSchemapreview feature with MySQLPrisma Client
clientExtensionspreview feature is used$extendsTS error: "Inferred type of this node exceeds the maximum length the compiler will serialize" with"declaration": trueintsconfigargsisundefinedconsole.logoutputs incorrect value whenresultextensions are usedextendedWhereUniqueon SQLLanguage tools (e.g. VS Code)
@ mapalthough already present'in optional arguments contextPrisma Engines
@@ schemaattribute should always be required whenschemasis defined in the datasourceCredits
Huge thanks to @ ivan, @ Mini256, @ cmd-johnson for helping!
Prisma Help Center (New)
We recently just launched our Help Center that you can use to find resources and get help from our support team for both the Prisma ORM and the Prisma Data Platform.
Check it out, and let us know what you think.
📺 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, December 22 at 5 pm Berlin | 8 am San Francisco.
Today, we are issuing the
4.7.1patch release.Fixes in Prisma Client
clientExtensionspreview feature is usedconsole.logoutputs incorrect value whenresultextensions are usedfindUniqueOrThrowargsisundefinedRead more
Today, we are issuing the
4.6.1patch release.Fixes in Prisma Client
findManyerrors withPANIC: index out of bounds: the len is 0 but the index is 0upsert()with nested selection errors withcalledOption::unwrap()on aNonevaluein 4.6.0Fix in Prisma Migrate
Read more
Read more
Read more
Today, we are issuing the
4.3.1patch release.Fixes in Prisma Client
Fixes in Prisma CLI