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.18.0 #92

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

Conversation

pshaddel
Copy link
Owner

snyk-top-banner

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

ℹ️ 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 329 versions ahead of your current version.

  • The recommended version was released on 22 days ago.

Release notes
Package name: @prisma/client
  • 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)

    Prisma Engines

    Credits

    Huge thanks to @ key-moon, @ pranayat, @ yubrot, @ skyzh, @ brian-dlee, @ mydea, @ nickcarnival, @ eruditmorina, @ nzakas, @ gutyerrez, @ avallete, @ ceddy4395, @ Kayoshi-dev, @ yehonatanz for helping!

  • 5.16.0-integration-vitest-workaround.2 - 2024-06-25
  • 5.16.0-integration-vitest-workaround.1 - 2024-06-17
  • 5.16.0-integration-sqlite-fix.1 - 2024-06-11
  • 5.16.0-integration-optimize-login-v2.5 - 2024-06-19
  • 5.16.0-integration-optimize-login-v2.4 - 2024-06-18
  • 5.16.0-integration-optimize-login-v2.3 - 2024-06-18
  • 5.16.0-integration-optimize-login-v2.2 - 2024-06-18
  • 5.16.0-integration-optimize-login-v2.1 - 2024-06-18
  • 5.16.0-integration-joel-repro-gh-11789.2 - 2024-06-18
  • 5.16.0-integration-joel-repro-gh-11789.1 - 2024-06-18
  • 5.16.0-integration-janpio-studio-prisma-config.3 - 2024-06-14
  • 5.16.0-integration-janpio-studio-prisma-config.2 - 2024-06-14
  • 5.16.0-integration-janpio-studio-prisma-config.1 - 2024-06-14
  • 5.16.0-integration-fix-empty-schema.1 - 2024-06-10
  • 5.16.0-integration-engines-5-16-0-15-fix-fts-relation-input-name-9388ddb70ab6bc6cba66ec9b351906f857af5d3f.1 - 2024-06-17
  • 5.16.0-integration-engines-5-16-0-1-fix-sqlite-concurrent-writes-74a48e9f33b0a8b403045af35430ce444541be88.1 - 2024-06-05
  • 5.16.0-integration-crypto-client-vercel.2 - 2024-06-05
  • 5.16.0-integration-crypto-client-vercel.1 - 2024-06-05
  • 5.16.0-dev.64 - 2024-06-25
  • 5.16.0-dev.63 - 2024-06-25
  • 5.16.0-dev.62 - 2024-06-24
  • 5.16.0-dev.61 - 2024-06-24
  • 5.16.0-dev.60 - 2024-06-24
  • 5.16.0-dev.59 - 2024-06-21
  • 5.16.0-dev.58 - 2024-06-21
  • 5.16.0-dev.57 - 2024-06-20
  • 5.16.0-dev.56 - 2024-06-20
  • 5.16.0-dev.55 - 2024-06-20
  • 5.16.0-dev.54 - 2024-06-20
  • 5.16.0-dev.53 - 2024-06-19
  • 5.16.0-dev.51 - 2024-06-19
  • 5.16.0-dev.50 - 2024-06-19
  • 5.16.0-dev.49 - 2024-06-18
  • 5.16.0-dev.48 - 2024-06-18
  • 5.16.0-dev.47 - 2024-06-18
  • 5.16.0-dev.46 - 2024-06-18
  • 5.16.0-dev.45 - 2024-06-17
  • 5.16.0-dev.44 - 2024-06-17
  • 5.16.0-dev.43 - 2024-06-17
  • 5.16.0-dev.42 - 2024-06-17
  • 5.16.0-dev.41 - 2024-06-17
  • 5.16.0-dev.40 - 2024-06-14
  • 5.16.0-dev.39 - 2024-06-14
  • 5.16.0-dev.38 - 2024-06-14
  • 5.16.0-dev.37 - 2024-06-14
  • 5.16.0-dev.36 - 2024-06-13
  • 5.16.0-dev.35 - 2024-06-12
  • 5.16.0-dev.34 - 2024-06-12
  • 5.16.0-dev.33 - 2024-06-12
  • 5.16.0-dev.32 - 2024-06-12
  • 5.16.0-dev.31 - 2024-06-12
  • 5.16.0-dev.30 - 2024-06-12
  • 5.16.0-dev.29 - 2024-06-12
  • 5.16.0-dev.28 - 2024-06-12
  • 5.16.0-dev.27 - 2024-06-11
  • 5.16.0-dev.26 - 2024-06-11
  • 5.16.0-dev.25 - 2024-06-10
  • 5.16.0-dev.24 - 2024-06-10
  • 5.16.0-dev.23 - 2024-06-10
  • 5.16.0-dev.22 - 2024-06-10
  • 5.16.0-dev.21 - 2024-06-10
  • 5.16.0-dev.20 - 2024-06-10
  • 5.16.0-dev.19 - 2024-06-10
  • 5.16.0-dev.18 - 2024-06-10
  • 5.16.0-dev.17 - 2024-06-10
  • 5.16.0-dev.16 - 2024-06-07
  • 5.16.0-dev.15 - 2024-06-07
  • 5.16.0-dev.14 - 2024-06-07
  • 5.16.0-dev.13 - 2024-06-06
  • 5.16.0-dev.12 - 2024-06-06
  • 5.16.0-dev.11 - 2024-06-06
  • 5.16.0-dev.9 - 2024-06-05
  • 5.16.0-dev.8 - 2024-06-05
  • 5.16.0-dev.7 - 2024-06-05
  • 5.16.0-dev.6 - 2024-06-05
  • 5.16.0-dev.5 - 2024-06-05
  • 5.16.0-dev.4 - 2024-06-04
  • 5.16.0-dev.3 - 2024-06-04
  • 5.16.0-dev.2 - 2024-06-04
  • 5.16.0-dev.1 - 2024-06-04
  • 5.15.1 - 2024-06-18

    Today, we are issuing the 5.15.1 patch release.

    Fixes in Prisma Client

  • 5.15.1-dev.1 - 2024-06-17
  • 5.15.0 - 2024-06-04

    Today, we are excited to share the 5.15.0 stable release 🎉

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

    Highlights

    Multi-File Prisma Schema support

    Prisma ORM 5.15.0 features support for multi-file Prisma Schema in Preview.

    This closes a long standing issue and does so in a clean and easy to migrate way.

    To get started:

    1. Enable the prismaSchemaFolder Preview feature by including it in the previewFeatures field of your generator.
      datasource db {
      provider = "postgresql"
      url = env("DATABASE_URL")
      }

      generator client {
      provider = "prisma-client-js"
      previewFeatures = ["prismaSchemaFolder"]
      }

    2. Create a schema subdirectory under your prisma directory.
    3. Move your schema.prisma into this directory.

    You are now set up with a multi-file Prisma Schema! Add as many or as few .prisma files to the new prisma/schema directory.

    When running commands where a Prisma Schema file is expected to be provided, you can now define a Prisma Schema directory. This includes Prisma CLI commands that use the --schema option as well as defining schema via package.json

    Our tooling has also been updated to handle multiple Prisma Schema files. This includes our Visual Studio Code extension and tools like database introspection, which will deposit new models in a introspected.prisma file. Existing models will be updated in the file they are found.

    To learn more, please refer to our official documentation and announcement blog post. If you try out prismaSchemaFolder, please let us know!

    Interesting Bug Fixes

    Fix for PostgreSQL prepared statement caching for raw queries

    This release fixes a nasty bug with the caching of prepared statements in raw Prisma Client queries that affected PostgreSQL when you ran the same SQL statement with differently typed paramters. This should not fail any more.

    Fix for SQL Server introspection of (deprecated) CREATE DEFAULT

    Our Introspection logic crashed on encountering certain multi-line CREATE DEFAULT, a deprecated way to define defaults in SQL Server. As many SQL Server users are working with established databases, this happened frequently enough that we now explicitly ignore these defaults instead of crashing.

    Fix for Cloudflare D1’s lower parameter limit

    Cloudflare’s D1 has a lower parameter limit than local SQLite, which caused bigger queries to fail. We adapted that limit to the D1 default for @ prisma/adapter-d1, which will avoid such failures.

    Fix for Cloudflare D1’s different PRAGMA support

    Our generated migration SQL for SQLite did not always work for Cloudflare D1, because of differences in the supported pragmas. We adapted the SQL to work in both local SQLite and Cloudflare D1.

    Fixes and improvements

    Prisma Migrate

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

See this package in npm:
@prisma/client

See this project in Snyk:
https://app.snyk.io/org/pshaddel/project/a92b9b01-9263-495d-9d66-d73912d132b0?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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for splitting Prisma schema into multiple files
2 participants