[Snyk] Upgrade @prisma/client from 5.4.1 to 5.8.1 #2
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/client from 5.4.1 to 5.8.1. See this package in npm: https://www.npmjs.com/package/@prisma/client See this project in Snyk: https://app.snyk.io/org/gr00nd/project/96bd7367-461e-4d2c-bcc5-93833e3fe523?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.4.1 to 5.8.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.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
Today, we are issuing the
5.5.2patch release.Fix in Prisma CLI
Today, we are issuing the
5.5.1patch release.Fix in Prisma Client
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Serverless database drivers improvements and request for feedback (Preview)
In version 5.4.0, we released
driverAdaptersinto Preview. ThedriverAdapterfeature enables Prisma Client to access your database using other JavaScript or Serverless database drivers such as Neon, PlanetScale, and Turso.The driver adapters allow Prisma Client to connect to your database using protocols besides TCP, such as HTTP (PlanetScale and Turso) and WebSockets (Neon). You can learn more about the Preview feature from the announcement blog post.
In this release, we focused our efforts on fixing bugs and improving the stability of the Preview feature.
We encourage you to try it out and share your feedback to help us move it to General Availability in either of the following GitHub discussions:
New flags for the
prisma initcommandThis release introduces 3 new flags you can provide when initializing Prisma in your project using the
prisma initcommand:--generator-provider: Defines the default generator to use--preview-features: Specifies the default Preview features to use in your project--output: Specifies the default output location for the generated clientFixes and improvements
Prisma CLI
Prisma Client
prisma.model.countdoes not typedistinctcorrectly….findMany()invocation: The columnj1.iddoes not exist in the current database.Credits
Huge thanks to @ onichandame, @ fqazi, @ KhooHaoYit, @ alencardc, @ Oreilles, @ christianledgard, @ skyzh, @ alula, @ michaelpoellath, @ lukahartwig, @ steebchen, @ icanipa, @ jiashengguo, @ stephenwade for helping!
💼 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.
We're currently hiring for the following roles: