Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @prisma/client from 5.14.0 to 5.19.1 #1

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

davidebukali
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @prisma/client from 5.14.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 410 versions ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: @prisma/client
  • 5.19.1 - 2024-09-02

    Today, we are issuing the 5.19.1 patch 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

  • 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

    Today, we are excited to share the 5.19.0 stable 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 typedSql Preview feature, you’re able to write SQL queries in a new sql subdirectory of your prisma directory. These queries are then checked by Prisma during using the new --sql flag of prisma generate and added to your client for use in your code.

    To get started with TypedSQL:

    1. Make sure that you have the latest version of prisma and @ prisma/client installed:

      npm install -D prisma@latest
      npm install @ prisma/client@latest
      
    2. Enable the typedSql Preview feature in your Prisma Schema.

         generator client {
           provider = "prisma-client-js"
           previewFeatures = ["typedSql"]
         }
      
    3. Create a sql subdirectory of your prisma directory.

      mkdir -p prisma/sql
      
    4. You can now add .sql files to the sql directory! Each file can contain one sql query and the name must be a valid JS identifier. For this example, say you had the file getUsersWithPosts.sql with the following contents:

      SELECT u.id, u.name, COUNT(p.id) as "postCount"
      FROM "User" u
      LEFT JOIN "Post" p ON u.id = p."authorId"
      GROUP BY u.id, u.name
    5. Import your SQL query into your code with the @ prisma/client/sql import:

      import { PrismaClient } from '@ prisma/client'
      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 driverAdapters Preview feature and Cloudflare D1 support were resolved via prisma/prisma-engines#4970 and #24922

    • Mathematic operations such as max, min, eq, etc in queries when using Cloudflare D1.
    • Resolved issues when comparing BigInt IDs when relationMode="prisma" was enabled and Cloudflare D1 was being used.

    Joins

    • #23742 fixes Prisma Client not supporting deeply nested some clauses when the relationJoins Preview 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!

    • 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 prisma-engines Rust 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!

  • 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

    🌟 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 are 4 and 7, with 4 being the default.

    model User {
    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:

    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!

  • 5.18.0-integration-revert-24949-fix-ts-version.1 - 2024-08-06
  • 5.18.0-integration-fix-config-dir-client.5 - 2024-07-19
  • 5.18.0-integration-fix-config-dir-client.4 - 2024-07-19
  • 5.18.0-integration-fix-config-dir-client.3 - 2024-07-19
  • 5.18.0-integration-fix-config-dir-client.2 - 2024-07-17
  • 5.18.0-integration-fix-config-dir-client.1 - 2024-07-17
  • 5.18.0-integration-feat-typed-sql.9 - 2024-08-05
  • 5.18.0-integration-feat-typed-sql.8 - 2024-08-05
  • 5.18.0-integration-feat-typed-sql.7 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.6 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.5 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.4 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.3 - 2024-08-02
  • 5.18.0-integration-feat-typed-sql.2 - 2024-07-29
  • 5.18.0-integration-feat-typed-sql.1 - 2024-07-29
  • 5.18.0-integration-engines-5-18-0-9-feat-gh-actions-0b3765edade679247b3c9856bcabbcdc1736853e.1 - 2024-07-19
  • 5.18.0-integration-engines-5-18-0-7-feat-gh-actions-462cf67beffd0cc97802a8034d58a38ec9c58b99.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-6-feat-gh-actions-19bafc70f9e564e8f5792bd8a9cd4bad4df5748e.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-5-feat-gh-actions-5f2a1d1133b515a5b4cbf1b17ef011a9fe22b559.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-4-feat-gh-actions-db4307dd3283e239e498436ea27707d22af180f3.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-3-feat-gh-actions-3d6f612a21393259032d9b8630f4b621b4f3c32f.1 - 2024-07-17
  • 5.18.0-integration-engines-5-18-0-26-feat-introspect-sql-4dcdf8b8304815e12f4af0e41837efb42c98e9b7.1 - 2024-08-02
  • 5.18.0-integration-engines-5-18-0-24-integration-fix-d1-int64-46841fc537adb365fc503b23779c98a19ac9835d.2 - 2024-07-31
  • 5.18.0-integration-engines-5-18-0-24-integration-fix-d1-int64-46841fc537adb365fc503b23779c98a19ac9835d.1 - 2024-07-31
  • 5.18.0-integration-engines-5-18-0-20-feat-introspect-sql-b2b600c154792b1859dfb09b93d383681a1b2bf0.1 - 2024-07-29
  • 5.18.0-integration-engines-5-18-0-2-feat-gh-actions-5ed0cbc35ff1fdd02f7d09f7819a213f9b5e6b9f.1 - 2024-07-16
  • 5.18.0-integration-engines-5-18-0-14-integration-test-gh-branch-555baf1ea1fca8f73cebed665b226cf3b8c4798b.2 - 2024-07-22
  • 5.18.0-integration-engines-5-18-0-14-integration-test-gh-branch-555baf1ea1fca8f73cebed665b226cf3b8c4798b.1 - 2024-07-22
  • 5.18.0-integration-engines-5-18-0-12-improve-quaint-column-type-331a7dd91f2553e6a77b58649b55472bca4fa225.1 - 2024-07-22
  • 5.18.0-integration-engines-5-17-0-4-feat-remove-actors-attempt-2-e7f608ab076eda9e1264e600ce3a140f0bc06bbe.1 - 2024-07-31
  • 5.18.0-dev.14 - 2024-08-06
  • 5.18.0-dev.13 - 2024-08-05
  • 5.18.0-dev.12 - 2024-08-05
  • 5.18.0-dev.11 - 2024-08-02
  • 5.18.0-dev.10 - 2024-07-24
  • 5.18.0-dev.9 - 2024-07-24
  • 5.18.0-dev.8 - 2024-07-23
  • 5.18.0-dev.7 - 2024-07-23
  • 5.18.0-dev.6 - 2024-07-22
  • 5.18.0-dev.5 - 2024-07-22
  • 5.18.0-dev.4 - 2024-07-22
  • 5.18.0-dev.3 - 2024-07-22
  • 5.18.0-dev.2 - 2024-07-19
  • 5.18.0-dev.1 - 2024-07-17
  • 5.17.0 - 2024-07-16

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Highlights

    VSCode extension improvements

    We’re happy to introduce some cool new features that will make your experience with the Prisma VSCode extension even better!

    Find references across schema files

    The ability to hop between references of a given symbol is really useful in application code and now with the introduction of multi-file schema, we think it’s the perfect time to bring this feature to the VSCode extension!

    With the 5.17.0 release, you’ll now have the ability to use the native “find references” feature to find any usage of a given symbol

    references

    Added context on hover

    When hovering over a symbol that references a view, type, enum, or any other block with multiple values, you’ll now see a handy pop out that shows what is in that block at a glance.

    image

    Additional quick fixes

    We’ve taken some fixes made by the prisma format cli command and made them quick fixes available to the VSCode Extension. Now, when you have forget a back relation or relation scalar field, you’ll now see in real time what is wrong and have the option to fix it via the extension.

    image (1)

    QueryRaw performance improvements

    We’ve changed the response format of queryRaw to decrease its average size which reduces serialization CPU overhead.

    When querying large data sets, we expect you to see improved memory usage and up to 2x performance improvements.

    Fixes and improvements

    Prisma Client

    Prisma

    Language tools (e.g. VS Code)

    Credits

    Huge thanks to @ key-moon, @ pranayat, @ yubrot, @ skyzh for helping!

  • 5.17.0-integration-tmp-revert-vitest-work.2 - 2024-07-08
  • 5.17.0-integration-tmp-revert-vitest-work.1 - 2024-07-08
  • 5.17.0-integration-show-platform-auth-token.8 - 2024-07-10
  • 5.17.0-integration-show-platform-auth-token.7 - 2024-07-10
  • 5.17.0-integration-show-platform-auth-token.6 - 2024-07-10
  • 5.17.0-integration-show-platform-auth-token.5 - 2024-07-10
  • 5.17.0-integration-show-platform-auth-token.4 - 2024-07-10
  • 5.17.0-integration-show-platform-auth-token.3 - 2024-07-10
  • 5.17.0-integration-show-platform-auth-token.2 - 2024-07-09
  • 5.17.0-integration-show-platform-auth-token.1 - 2024-07-09
  • 5.17.0-integration-remove-useless-clone.1 - 2024-07-09
  • 5.17.0-integration-fix-wasm-nextjs.2 - 2024-07-05
  • 5.17.0-integration-fix-wasm-nextjs.1 - 2024-07-05
  • 5.17.0-integration-fix-vitest-edgemw.1 - 2024-07-08
  • 5.17.0-integration-es2021.5 - 2024-07-01
  • 5.17.0-integration-es2021.4 - 2024-07-01
  • 5.17.0-integration-es2021.3 - 2024-07-01
  • 5.17.0-integration-es2021.2 - 2024-06-28
  • 5.17.0-integration-es2021.1 - 2024-06-26
  • 5.17.0-integration-engines-5-17-0-9-integration-dmmf-indexes-d1e2e9a2a0de2bfcf127b78ffed1231707668674.2 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-9-integration-dmmf-indexes-d1e2e9a2a0de2bfcf127b78ffed1231707668674.1 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-6-integration-schema-wasm-datamodel-e7f10528e9f51ad6040a30bd82ee9d220aa4ee93.2 - 2024-07-09
  • 5.17.0-integration-engines-5-17-0-6-integration-schema-wasm-datamodel-e7f10528e9f51ad6040a30bd82ee9d220aa4ee93.1 - 2024-07-09
  • 5.17.0-integration-engines-5-17-0-4-feat-remove-actors-attempt-2-e7f608ab076eda9e1264e600ce3a140f0bc06bbe.2 - 2024-07-12
  • 5.17.0-integration-engines-5-17-0-4-feat-remove-actors-attempt-2-e7f608ab076eda9e1264e600ce3a140f0bc06bbe.1 - 2024-07-09
  • 5.17.0-integration-engines-5-17-0-3-integration-schema-wasm-datamodel-5aa1a0e22cad4693587f2d5f697e6c57d4f224c3.2 - 2024-07-09
  • 5.17.0-integration-engines-5-17-0-3-integration-schema-wasm-datamodel-5aa1a0e22cad4693587f2d5f697e6c57d4f224c3.1 - 2024-07-09
  • 5.17.0-integration-engines-5-17-0-27-feat-gh-actions-fca92037687d6fca891ea8bc636c3dba78b58bde.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-26-feat-gh-actions-71087f50f90400fd1ff10da7b187b0c8a1aef11a.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-25-feat-gh-actions-1d704f7d660b56cc6488a2e5fcf0b1b35bb84375.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-24-feat-gh-actions-6e5cfca055d17aa12c815c6f99786f9134095cc7.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-23-feat-gh-actions-be53ad1270793f135da1ae7b7c645cea39bf7fcb.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-22-feat-gh-actions-81995eb238f5fd4c5584112804fcf79f18e89cc6.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-21-feat-gh-actions-cfdd9eef8da5705405ffc9e94fc6d61c04cb7f2c.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-20-feat-gh-actions-2753dcb458557dd4f28b596f7506c17e93d5e0dd.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-18-feat-gh-actions-c1e7a626dcb1ad75dad12236150d482a53b0cdb5.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-17-4947-merge-1d8598a84efca2279183a81bdaf04bbae7f87cd2.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-16-integration-dmmf-indexes-d964e5cfdd8811d32218d9bfa6c83522e0a1ddde.2 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-16-integration-dmmf-indexes-d964e5cfdd8811d32218d9bfa6c83522e0a1ddde.1 - 2024-07-11
  • 5.17.0-integration-engines-5-17-0-13-integration-dmmf-indexes-ac9a360f4cd7cd3d8bdd5716853e22eb3332e3aa.2 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-13-integration-dmmf-indexes-ac9a360f4cd7cd3d8bdd5716853e22eb3332e3aa.1 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-12-integration-dmmf-indexes-653fb43bd2ac7b562d889188c08703c30dae272f.2 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-12-integration-dmmf-indexes-653fb43bd2ac7b562d889188c08703c30dae272f.1 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-11-integration-dmmf-indexes-f04e601986ba13c9e6df6b4f1032f40c5bdcaa81.2 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-11-integration-dmmf-indexes-f04e601986ba13c9e6df6b4f1032f40c5bdcaa81.1 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-10-integration-dmmf-indexes-f36d20503d1dec368c81ffbc9706a57df2250b8a.2 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-10-integration-dmmf-indexes-f36d20503d1dec368c81ffbc9706a57df2250b8a.1 - 2024-07-10
  • 5.17.0-integration-engines-5-17-0-1-perf-query-raw-serialization-e47383c417b1d157566b509938893a9b8ada2aad.7 - 2024-07-02
  • 5.17.0-integration-engines-5-17-0-1-perf-query-raw-serialization-e47383c417b1d157566b509938893a9b8ada2aad.6 - 2024-07-02
  • 5.17.0-integration-engines-5-17-0-1-perf-query-raw-serialization-e47383c417b1d157566b509938893a9b8ada2aad.5 - 2024-07-02
  • 5.17.0-integration-engines-5-17-0-1-perf-query-raw-serialization-e47383c417b1d157566b509938893a9b8ada2aad.4 - 2024-07-02
  • 5.17.0-integration-engines-5-17-0-1-perf-query-raw-serialization-e47383c417b1d157566b509938893a9b8ada2aad.3 - 2024-07-02
  • 5.17.0-integration-engines-5-17-0-1-perf-query-raw-serialization-e47383c417b1d157566b509938893a9b8ada2aad.2 - 2024-07-01
  • 5.17.0-integration-engines-5-17-0-1-perf-query-raw-serialization-e47383c417b1d157566b509938893a9b8ada2aad.1 - 2024-07-01
  • 5.17.0-integration-dmmf-indexes.6 - 2024-07-11
  • 5.17.0-integration-dmmf-indexes.5 - 2024-07-11
  • 5.17.0-integration-dmmf-indexes.4 - 2024-07-11
  • 5.17.0-integration-dmmf-indexes.3 - 2024-07-11
  • 5.17.0-integration-dmmf-indexes.2 - 2024-07-11
  • 5.17.0-integration-dmmf-indexes.1 - 2024-07-11
  • 5.17.0-integration-avoid-using-process-in-debug.3 - 2024-07-09
  • 5.17.0-integration-avoid-using-process-in-debug.2 - 2024-07-09
  • 5.17.0-integration-avoid-using-process-in-debug.1 - 2024-07-02
  • 5.17.0-dev.39 - 2024-07-16
  • 5.17.0-dev.38 - 2024-07-15
  • 5.17.0-dev.37 - 2024-07-15
  • 5.17.0-dev.36 - 2024-07-15
  • 5.17.0-dev.35 - 2024-07-15
  • 5.17.0-dev.34 - 2024-07-12
  • 5.17.0-dev.33 - 2024-07-12
  • 5.17.0-dev.32 - 2024-07-12
  • 5.17.0-dev.31 - 2024-07-12
  • 5.17.0-dev.30 - 2024-07-11
  • 5.17.0-dev.29 - 2024-07-11
  • 5.17.0-dev.28 - 2024-07-11
  • 5.17.0-dev.27 - 2024-07-11
  • 5.17.0-dev.26 - 2024-07-10
  • 5.17.0-dev.25 - 2024-07-10
  • 5.17.0-dev.24 - 2024-07-10
  • 5.17.0-dev.23 - 2024-07-09
  • 5.17.0-dev.22 - 2024-07-09
  • 5.17.0-dev.21 - 2024-07-09
  • 5.17.0-dev.20 - 2024-07-09
  • 5.17.0-dev.19 - 2024-07-09
  • 5.17.0-dev.18 - 2024-07-05
  • 5.17.0-dev.17 - 2024-07-03
  • 5.17.0-dev.16 - 2024-07-03
  • 5.17.0-dev.15 - 2024-07-03
  • 5.17.0-dev.14 - 2024-07-03
  • 5.17.0-dev.13 - 2024-07-03
  • 5.17.0-dev.12 - 2024-07-03
  • 5.17.0-dev.11 - 2024-07-03
  • 5.17.0-dev.10 - 2024-06-28
  • 5.17.0-dev.9 - 2024-06-28
  • 5.17.0-dev.8 - 2024-06-28
  • 5.17.0-dev.7 - 2024-06-28
  • 5.17.0-dev.6 - 2024-06-28
  • 5.17.0-dev.5 - 2024-06-28
  • 5.17.0-dev.4 - 2024-06-28
  • 5.17.0-dev.2 - 2024-06-27
  • 5.17.0-dev.1 - 2024-06-26
  • 5.16.2 - 2024-07-09

    Today, we are issuing the 5.16.2 patch release to fix an issue in Prisma client.

    Fix in Prisma Client

  • 5.16.2-dev.1 - 2024-07-09
  • 5.16.1 - 2024-06-27

    Today, we are issuing the 5.16.1 patch release to fix an issue in Prisma client.

    Fix in Prisma Client

  • 5.16.1-dev.1 - 2024-06-27
  • 5.16.0 - 2024-06-25

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Highlights

    Omit model fields globally

    With Prisma ORM 5.16.0 we’re more than happy to announce that we’re expanding the omitApi Preview feature to also include the ability to omit fields globally.

    When the Preview feature is enabled, you’re able to define fields to omit when instantiating Prisma Client.

    const prisma = new PrismaClient({
      omit: {
        user: {
          // make sure that password is never queried.
          password: true,
        },
      },
    });

    You’re also able to omit fields from multiple models and multiple fields from the same model

    const prisma = new PrismaClient({
      omit: {
        user: { 
          // make sure that password and internalId are never queried.
          password: true,
          internalId: true,
        },
        post: {
          secretkey: true,
        },
      },
    });

    With both local and global omit, you now have the flexibility to completely remove sensitive fields while also tailoring individual queries. If you need the ability to generally omit a field except in a specific query, you can also overwrite a global omit locally

    const prisma = new PrismaClient({
    omit: {
    user: {
    // password is omitted globally.
    password: true,
    },
    },
    });

    const userWithPassword = await prisma.user.findUnique({
    omit: { password: false }, // omit now false, so password is returned
    where: { id: 1 },
    });

    Changes to prismaSchemaFolder

    In 5.15.0 we released the prismaSchemaFolder Preview feature, allowing you to create multiple Prisma Schema files in a prisma/schema directory. We’ve gotten a lot of great feedback and are really excited with how the community has been using the feature.

    To continue improving our multi-file schema support, we have a few breaking changes to the prismaSchemaFolder feature:

    • When using relative paths in Prisma Schema files with the prismaSchemaFolder feature, a path is now relative to the file it is defined in rather than relative to the prisma/schema folder. This means that if you have a generator block in /project/prisma/schema/config/generator.prisma with an output of ./foo the output will be resolved to /project/prisma/schema/config/foo rather than /project/prisma/foo. The path to a SQLite file will be resolved in the same manner.
    • We realized that during migration many people would have prisma/schema as well as prisma/schema.prisma. Our initial implementation looked for a .prisma file first and would ignore the schema folder if it exists. This is now an error.

    Changes to fullTextSearch

    In order to improve our full-text search implementation we have made a breaking change to the fullTextSearch Preview feature.

    Previously, when the feature was enabled we updated the <Model>OrderByWithRelationInput TypeScript type with the <Model>OrderByWithRelationAndSearchRelevanceInput type. However, we have noted that there are no cases where relational ordering is needed but search relevance is not. Thus, we have decided to remove the <Model>OrderByWithRelationAndSearchRelevanceInput naming and only use the <Model>OrderByWithRelationInput naming.

    Fixes and improvements

    Prisma

    Language tools (e.g. VS Code)

Snyk has created this PR to upgrade @prisma/client from 5.14.0 to 5.19.1.

See this package in npm:
@prisma/client

See this project in Snyk:
https://app.snyk.io/org/davidebukali/project/7fafc13f-5878-4b06-a9a1-ab176fcbc864?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Oct 3, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
ai-powered-nextjs-app ❌ Failed (Inspect) Oct 3, 2024 10:17am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants