[Snyk] Upgrade @prisma/client from 5.18.0 to 5.19.1 #75
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/client from 5.18.0 to 5.19.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.
The recommended version is 81 versions ahead of your current version.
The recommended version was released on 23 days ago.
Release notes
Package name: @prisma/client
-
5.19.1 - 2024-09-02
- #25103
- #25137
- #25104
- #25101
-
5.19.1-dev.4 - 2024-09-02
-
5.19.1-dev.3 - 2024-09-02
-
5.19.1-dev.2 - 2024-09-02
-
5.19.1-dev.1 - 2024-09-02
-
5.19.0 - 2024-08-27
-
-
-
-
-
import { PrismaClient } from '@ prisma/client'
- Mathematic operations such as
- Resolved issues when comparing
- #23742 fixes Prisma Client not supporting deeply nested
- Senior Engineer (TypeScript): This person will be primarily working on the TypeScript side and evolving our Prisma client. Rust knowledge (or desire to learn Rust) is a plus.
- Senior Engineer (Rust): This person will be focused on the
-
5.19.0-integration-feat-typed-sql.26 - 2024-08-23
-
5.19.0-integration-feat-typed-sql.25 - 2024-08-23
-
5.19.0-integration-feat-typed-sql.24 - 2024-08-23
-
5.19.0-integration-feat-typed-sql.23 - 2024-08-23
-
5.19.0-integration-feat-typed-sql.22 - 2024-08-23
-
5.19.0-integration-feat-typed-sql.21 - 2024-08-22
-
5.19.0-integration-feat-typed-sql.20 - 2024-08-22
-
5.19.0-integration-feat-typed-sql.19 - 2024-08-22
-
5.19.0-integration-feat-typed-sql.18 - 2024-08-22
-
5.19.0-integration-feat-typed-sql.17 - 2024-08-22
-
5.19.0-integration-feat-typed-sql.16 - 2024-08-22
-
5.19.0-integration-feat-typed-sql.15 - 2024-08-22
-
5.19.0-integration-feat-typed-sql.14 - 2024-08-22
-
5.19.0-integration-feat-typed-sql.13 - 2024-08-21
-
5.19.0-integration-feat-typed-sql.12 - 2024-08-21
-
5.19.0-integration-feat-typed-sql.11 - 2024-08-21
-
5.19.0-integration-feat-typed-sql.10 - 2024-08-21
-
5.19.0-integration-feat-typed-sql.9 - 2024-08-21
-
5.19.0-integration-feat-typed-sql.8 - 2024-08-20
-
5.19.0-integration-feat-typed-sql.7 - 2024-08-20
-
5.19.0-integration-feat-typed-sql.6 - 2024-08-08
-
5.19.0-integration-feat-typed-sql.5 - 2024-08-07
-
5.19.0-integration-feat-typed-sql.4 - 2024-08-07
-
5.19.0-integration-feat-typed-sql.3 - 2024-08-07
-
5.19.0-integration-feat-typed-sql.2 - 2024-08-07
-
5.19.0-integration-feat-typed-sql.1 - 2024-08-07
-
5.19.0-integration-engines-5-19-0-9-integration-fix-planetscale-transactions-6b0a78a8af3fae4debef82ff443972dff0807722.2 - 2024-08-12
-
5.19.0-integration-engines-5-19-0-9-integration-fix-planetscale-transactions-6b0a78a8af3fae4debef82ff443972dff0807722.1 - 2024-08-12
-
5.19.0-integration-engines-5-19-0-32-integration-fix-planetscale-transactions-c83aea2de749622725d37b2125922e2b83ac349c.2 - 2024-08-26
-
5.19.0-integration-engines-5-19-0-32-integration-fix-planetscale-transactions-c83aea2de749622725d37b2125922e2b83ac349c.1 - 2024-08-26
-
5.19.0-integration-engines-5-19-0-3-integration-fix-d1-int64-3fe108cb35159b6838b9365ea06876b999e37136.2 - 2024-08-08
-
5.19.0-integration-engines-5-19-0-3-integration-fix-d1-int64-3fe108cb35159b6838b9365ea06876b999e37136.1 - 2024-08-08
-
5.19.0-integration-engines-5-19-0-29-integration-build-rs-version-34ac31986ed851ada6e3c142e76db8fdb839a8f0.2 - 2024-08-24
-
5.19.0-integration-engines-5-19-0-29-integration-build-rs-version-34ac31986ed851ada6e3c142e76db8fdb839a8f0.1 - 2024-08-24
-
5.19.0-integration-engines-5-19-0-28-integration-enum-mapped-values-ba87944c8b88a1e7b2255a110274d540df6bb831.2 - 2024-08-24
-
5.19.0-integration-engines-5-19-0-28-integration-enum-mapped-values-ba87944c8b88a1e7b2255a110274d540df6bb831.1 - 2024-08-24
-
5.19.0-integration-engines-5-19-0-25-feat-typed-sql-nullability-860858bb818708261f36cd05bc915e603aae5004.1 - 2024-08-20
-
5.19.0-integration-engines-5-19-0-22-integration-mongodb-ipv6-fix-a6fed372778795b60d9899578c11319bc19597ac.2 - 2024-08-20
-
5.19.0-integration-engines-5-19-0-22-integration-mongodb-ipv6-fix-a6fed372778795b60d9899578c11319bc19597ac.1 - 2024-08-20
-
5.19.0-integration-engines-5-19-0-21-feat-typed-sql-nullability-e696c9149500a73fbefedf5b0edb3f085ff90515.1 - 2024-08-19
-
5.19.0-integration-engines-5-19-0-20-integration-mongodb-ipv6-fix-52a7684de6884ddf5b7e91ac5f37254a02a69774.2 - 2024-08-15
-
5.19.0-integration-engines-5-19-0-20-integration-mongodb-ipv6-fix-52a7684de6884ddf5b7e91ac5f37254a02a69774.1 - 2024-08-15
-
5.19.0-integration-engines-5-19-0-2-integration-fix-d1-int64-e5ebd17c4a7f6a855bd0d3594e1c593542db3061.2 - 2024-08-07
-
5.19.0-integration-engines-5-19-0-2-integration-fix-d1-int64-e5ebd17c4a7f6a855bd0d3594e1c593542db3061.1 - 2024-08-07
-
5.19.0-integration-engines-5-19-0-18-feat-typed-sql-nullability-c4dc3c5083115b65abe4436e4ec6e1c8c2afbecd.1 - 2024-08-14
-
5.19.0-integration-engines-5-19-0-17-feat-typed-sql-nullability-4b818550ffc9da4e66541525cca08569a58a78e2.1 - 2024-08-14
-
5.19.0-integration-engines-5-19-0-16-feat-typed-sql-nullability-c79c3569f88658b971ff948a55aff64ff3a4e4bf.1 - 2024-08-14
-
5.19.0-integration-engines-5-19-0-15-integration-fix-planetscale-transactions-cc0baab23c1961e4f06f2114b9cf252e99ac90f5.2 - 2024-08-14
-
5.19.0-integration-engines-5-19-0-15-integration-fix-planetscale-transactions-cc0baab23c1961e4f06f2114b9cf252e99ac90f5.1 - 2024-08-14
-
5.19.0-integration-engines-5-19-0-14-feat-typed-sql-nullability-29abebce25f4e6c26673d18598de307337325b86.1 - 2024-08-13
-
5.19.0-integration-engines-5-19-0-13-feat-typed-sql-nullability-7d01fb5b13f6e0f51384fe689b7e9ace5a504565.1 - 2024-08-13
-
5.19.0-integration-engines-5-19-0-11-integration-fix-planetscale-transactions-5154993b5b25464fff0c724fe47c547aa076c73a.2 - 2024-08-12
-
5.19.0-integration-engines-5-19-0-11-integration-fix-planetscale-transactions-5154993b5b25464fff0c724fe47c547aa076c73a.1 - 2024-08-12
-
5.19.0-integration-engines-5-19-0-10-integration-fix-planetscale-transactions-630e1df957c8431ec5989ee7188545730681ae49.2 - 2024-08-12
-
5.19.0-integration-engines-5-19-0-10-integration-fix-planetscale-transactions-630e1df957c8431ec5989ee7188545730681ae49.1 - 2024-08-12
-
5.19.0-integration-engines-5-19-0-1-integration-fix-d1-int64-61431bbd9716f47de3f303a09ece9b370da04142.2 - 2024-08-06
-
5.19.0-integration-engines-5-19-0-1-integration-fix-d1-int64-61431bbd9716f47de3f303a09ece9b370da04142.1 - 2024-08-06
-
5.19.0-dev.18 - 2024-08-26
-
5.19.0-dev.17 - 2024-08-24
-
5.19.0-dev.16 - 2024-08-23
-
5.19.0-dev.15 - 2024-08-23
-
5.19.0-dev.14 - 2024-08-23
-
5.19.0-dev.13 - 2024-08-21
-
5.19.0-dev.12 - 2024-08-20
-
5.19.0-dev.11 - 2024-08-19
-
5.19.0-dev.10 - 2024-08-16
-
5.19.0-dev.9 - 2024-08-16
-
5.19.0-dev.8 - 2024-08-13
-
5.19.0-dev.7 - 2024-08-12
-
5.19.0-dev.6 - 2024-08-12
-
5.19.0-dev.5 - 2024-08-12
-
5.19.0-dev.4 - 2024-08-12
-
5.19.0-dev.3 - 2024-08-09
-
5.19.0-dev.2 - 2024-08-09
-
5.19.0-dev.1 - 2024-08-07
-
5.18.0 - 2024-08-06
model User {
- SQLite db will now be created and read from the correct location when using
- Empty
- Support UUID v7
- Support fetching references for a model
from @prisma/client GitHub release notesToday, we are issuing the
5.19.1patch release.What's Changed
We've fixed the following issues:
Full Changelog: 5.19.0...5.19.x, prisma/prisma-engines@5.19.0...5.19.x
Today, we are excited to share the
5.19.0stable release 🎉🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release. 🌟
Highlights
Introducing TypedSQL
TypedSQL is a brand new way to interact with your database from Prisma Client. After enabling the
typedSqlPreview feature, you’re able to write SQL queries in a newsqlsubdirectory of yourprismadirectory. These queries are then checked by Prisma during using the new--sqlflag ofprisma generateand added to your client for use in your code.To get started with TypedSQL:
Make sure that you have the latest version of
prismaand@ prisma/clientinstalled:Enable the
typedSqlPreview feature in your Prisma Schema.Create a
sqlsubdirectory of yourprismadirectory.You can now add
.sqlfiles to thesqldirectory! Each file can contain one sql query and the name must be a valid JS identifier. For this example, say you had the filegetUsersWithPosts.sqlwith the following contents:Import your SQL query into your code with the
@ prisma/client/sqlimport:import { getUsersWithPosts } from '@prisma/client/sql'
const prisma = new PrismaClient()
const usersWithPostCounts = await prisma.$queryRawTyped(getUsersWithPosts)
console.log(usersWithPostCounts)
There’s a lot more to talk about with TypedSQL. We think that the combination of the high-level Prisma Client API and the low-level TypedSQL will make for a great developer experience for all of our users.
To learn more about behind the “why” of TypedSQL be sure to check out our announcement blog post.
For docs, check out our new TypedSQL section.
Bug fixes
Driver adapters and D1
A few issues with our
driverAdaptersPreview feature and Cloudflare D1 support were resolved via prisma/prisma-engines#4970 and #24922max,min,eq, etc in queries when using Cloudflare D1.BigIntIDs whenrelationMode="prisma"was enabled and Cloudflare D1 was being used.Joins
someclauses when therelationJoinsPreview feature was enabled.MongoDB
The MongoDB driver for Rust (that our query engine users under the hood) had behavior that prioritized IPv4 connections over IPv6 connections. In IPv6-only environments, this could lead to significant "cold starts" where the query engine had to wait for IPv4 to fail before the driver would try IPv6.
With help from the MongoDB team, this has been resolved. The driver will now try IPv4 and IPv6 connections in parallel and then move forward with the first response. This should prevent cold start issues that have been seen with MongoDB in Prisma Accelerate.
Thank you to the MongoDB team!
Join us
Looking to make an impact on Prisma in a big way? We're now hiring engineers for the ORM team!
prisma-enginesRust codebase. TypeScript knowledge (or, again, a desire to learn) is a plus.Credits
Huge thanks to @ mcuelenaere, @ pagewang0, @ Druue, @ key-moon, @ Jolg42, @ pranayat, @ ospfranco, @ yubrot, @ skyzh for helping!
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Native support for UUIDv7
Previous to this release, the Prisma Schema function
uuid()did not accept any arguments and created a UUIDv4 ID. While sufficient in many cases, UUIDv4 has a few drawbacks, namely that it is not temporally sortable.UUIDv7 attempts to resolve this issue, making it easy to temporally sort your database rows by ID!
To support this, we’ve updated the
uuid()function in Prisma Schema to accept an optional, integer argument. Right now, the only valid values are4and7, with4being the default.id String @id @default(uuid()) // defaults to 4
name String
}
model User {
id String @id @default(uuid(4)) // same as above, but explicit
name String
}
model User {
id String @id @default(uuid(7)) // will use UUIDv7 instead of UUIDv4
name String
}
Bug squashing
We’ve squashed a number of bugs this release, special thanks to everyone who helped us! A few select highlights are:
prismaSchemaFolder.Json[]fields will now return[]instead ofnullwhen accessed through a join using therelationJoinsPreview feature.Fixes and improvements
Prisma
Language tools (e.g. VS Code)
Share your feedback about Prisma ORM
We want to know how you like working with Prisma ORM in your projects! Please take our 2min survey and let us know what you like or where we can improve 🙏
Credits
Huge thanks to @ mcuelenaere, @ pagewang0, @ Druue, @ key-moon, @ Jolg42, @ pranayat, @ ospfranco, @ yubrot, @ skyzh, @ haaawk for helping!
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: