[Snyk] Upgrade @prisma/client from 5.1.1 to 5.9.1 #9
Conversation
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
Snyk has created this PR to upgrade @prisma/client from 5.1.1 to 5.9.1. See this package in npm: https://www.npmjs.com/package/@prisma/client See this project in Snyk: https://app.snyk.io/org/neo00007/project/e7404f73-11b1-491c-be83-ffa8132cb650?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.9.1.
ℹ️ 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/client
Today, we are issuing the
5.9.1patch release.Fixes in Prisma Client
In
5.9.0we have changed our conditional exports in@ prisma/client. This resulted in broken types for TypesScript users using certain combinations ofmodule/moduleResolutionsettings. Additionally, it also caused a regression for Next.js users which have encountered invalid error messages from our side.You can now try out
5.9.1and let us know if you find a bug at https://pris.ly/prisma-prisma-bug-reportError: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.#22889Note: many issues are duplicates.
Today, we are excited to share the
5.9.0stable release 🎉🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.
This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks:
Highlights
Optimized result sets for more efficient queries
We continue our efforts of the performance of Prisma Client queries. In
5.1.0, we introduced theRETURNINGkeyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use ofRETURNINGto SQLite and a broader range of queries for existing databases (e.g.deleteon PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs:SQL Server: Return proper error for unreachable database
When trying migrate/introspect a SQL server instance that’s unreachable, Prisma ORM now returns the correct
P1001error instead of failing without an error. Learn more in this PR: SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url.Fixes and improvements
Prisma Client
selectqueries on create/update/deletePrisma Migrate
ERROR: column "..." being dropped, try again laterwhen applying migrations with CRDB 23.1Language tools (e.g. VS Code)
Company news
Test edge functions support in Early Access
Today, the only way how to use Prisma ORM in edge functions (e.g. Cloudflare Workers or Vercel Edge Functions) is by using Prisma Accelerate. However, we are actively working on making Prisma ORM compatible with edge functions natively as well. If you want to become an early tester, you can apply for the private Early Accessing program by taking this survey.
We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing
Last year, AWS announced the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on IPv6. Learn more in this technical deep dive into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate.
Credits
Huge thanks to @ laplab, @ Druue, @ anuraaga, @ onichandame, @ LucianBuzzo, @ RobertCraigie, @ almeidx, @ victorgdb, @ tinola, @ sampolahtinen, @ AikoRamalho, @ petradonka for helping!
Today, we are issuing the
5.8.1patch release.Fix in Prisma Client
🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release. 🌟
Highlights
Happy New Year from your friends at Prisma! 🎊
In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉
relationJoinsimprovements: Relation loading strategy per query (Preview)In version 5.7.0, we released
relationJoinsinto Preview. TherelationJoinsfeature enables support forJOINs for relation queries.This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case.
You can now load relation data using either of the following strategies:
join— usesJOINs to fetch relation dataquery— uses separate queries to fetch relation dataWhen the
relationJoinsPreview feature is enabled, by default, the relation fetching strategy used isjoin. You can override the default behavior by using therelationLoadStrategyquery option.To get started, enable the Preview feature:
… and specify the relation loading strategy for your query as follows:
Try it out and share your feedback and create a bug report if you encounter any issues.
Survey: Edge functions support
We’re working on bringing Edge function support to Prisma ORM and we would appreciate your input by submitting a response to our survey. By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out.
Fixes and improvements
Prisma Client
targetandtimestampare undefined ininfoevents in Data Proxy clienttimestampanddurationin query events with Data Proxycitextfields with neon database driver causes conversion errorPrisma Migrate
Environment is non-interactivewhenVERCELenv var is definedLanguage tools (e.g. VS Code)
Error validating field 'id' in model 'Post': MongoDB '@ default(auto())' fields must have 'ObjectId' native type.Credits
Huge thanks to @ anuraaga, @ onichandame, @ LucianBuzzo, @ RobertCraigie, @ fqazi, @ KhooHaoYit, @ alencardc, @ Oreilles, @ tinola, @ AikoRamalho, @ luxaritas for helping!
Company news
🎉 A billion queries and counting: Prisma Accelerate
Prisma Accelerate, our global database cache has served over 1 billion queries since its General Availability launch.
We’d like to give a shoutout to our team and everyone who’s been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024!
🔮 Prisma ORM Ecosystem
Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? Let us know.
We would like to learn about it and feature it on our Ecosystem page.
💼 We’re hiring
If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. Check out our Careers page for open positions.
Today, we are issuing the
5.7.1patch release.This patch fixes multiple small problems in our
relationJoinspreview feature. If you ran into problems when testingrelationJoinsbefore, please give it another go with 5.7.1 and share your feedback or create a bug report if you encounter any issues.Fixes in Prisma Client
relationJoins: Int[] return as nullrelationJoins: fails when filtering includes by isNot: nullrelationJoins: "The table (not available) does not exist in the current database."relationJoins: PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }relationJoins: Inconsistent column data: Unexpected conversion failure from String to datetime. Reason: $trailing inputRead more
Read more