[Snyk] Upgrade prisma from 5.15.1 to 5.16.0

[itscharukadeshan]

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade prisma from 5.15.1 to 5.16.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 81 versions ahead of your current version.

• The recommended version was released on 23 days ago.

Release notes

Package name: prisma

• 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

  • Wrong Parameterized Types Sent for SQL Server Queries
  • Prisma has no exported member named OrderByWithRelationInput. Did you mean OrderByWithAggregationInput?
  • [Driver Adapters]: missing provider compatibility validation
  • Disable "Start using Prisma Client" hint logs on prisma generate
  • Deploying prisma to CloudFlare pages using Nuxt/Nitro and node-postgres (pg) is using the wrong(vercel) wasm path
  • @ prisma/adapter-pg modifies node-postgres global type parsers
  • @prisma/adapter-d1 is failing with an import error when called inside vitest tests
  • db pull fails with [libs\user-facing-errors\src\quaint.rs:136:18] internal error: entered unreachable code on invalid credentials

  Language tools (e.g. VS Code)

  • Make prisma-fmt logs to work with language server
  • Spans and positions get shifted out of sync when schema includes multibyte characters
  • VSCode extension panics when opening an empty prisma schema

  Prisma Engines

  • [DA] Planetscale engine tests: one2m_mix_required_writable_readable
  • [DA] Planetscale engine tests: apply_number_ops

  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

  • internal error: entered unreachable code
  • Got error 'internal error: entered unreachable code' when trying to perform an upsert.
  • Prisma Client errors on SQLite with internal error: entered unreachable code when running 2 concurrent upsert
  • ConnectionError(Timed out during query execution.) during seeding
  • SQLite timeouts after upgrade from prisma 2 to prisma 4
  • ConnectionError(Timed out during query execution.) error when using Promise.all for SQLite
  • Improve the error when SQLite database file is locked
  • sqlite timeout error multiple queries run one after another
  • SQLite times out during query execution when using Promise.all() / concurrent
  • internal error: entered unreachable code

from prisma GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs