[Snyk] Upgrade @prisma/client from 5.12.1 to 5.13.0

[vigneshshettyin]

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.12.1 to 5.13.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 58 versions ahead of your current version.

• The recommended version was released on a month ago.

Release notes

Package name: @prisma/client

• 5.13.0 - 2024-04-23
  

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

  🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release.

  Highlights

  omit fields from Prisma Client queries (Preview)

  We’re excited to announce Preview support for the omit option within the Prisma Client query options. The highly-requested omit feature now allows you to exclude fields that you don’t want to retrieve from the database on a per-query basis.

  By default, when a query returns records, the result includes all scalar fields of the models defined in the Prisma schema. select can be used to return specific fields, while omit can now be used to exclude specific fields. omit lives at the same API level and works on all of the same Prisma Client model queries as select. Note, however, that omit and select are mutually exclusive. In other words, you can’t use both in the same query.

  To get started using omit, enable the omitApi Preview feature in your Prisma schema:

  // schema.prisma
  generator client {
    provider        = "prisma-client-js"
    previewFeatures = ["omitApi"]
  }

  Be sure to re-generate Prisma Client afterwards:

  npx prisma generate

  Here is an example of using omit:

  // Includes all fields except password
  await prisma.user.findMany({
    omit: {
     password: true
    },
  })

  Here is an example of using omit with include:

  // Includes all user fields except user's password and title of user's posts
  await prisma.user.findMany({
    omit: {
     password: true
    },
    include: {
      posts: {
        omit: {
          title: true
        },
      },
    },
  })

  Expand to view the example Prisma schema

  model User {
  id Int @ id @ default(autoincrement())
  email String @ unique
  name String?
  password String
  posts Post[]
  }

  model Post {
  id Int @ id @ default(autoincrement())
  title String
  author User @ relation(fields: [authorId], references: [id])
  authorId Int
  }

  Many users have requested a global implementation of omit. This request will be accommodated in the future. In the meantime, you can follow the issue here.

  📣 Share your feedback: omitApi Preview feature

  📚 Documentation: omit - Prisma Client API Reference

  Fixes and improvements

  Prisma Migrate

  • Nicer Datamodel Type validation

  Prisma Client

  • MySQL upsert(): Internal error: Attempted to serialize empty result.
  • Mysql upsert() fails with "Attempted to serialize empty result."
  • Interactive Transaction API timing out after upgrading from 4.7.0 and above
  • MySQL and SQLite upsert(): Internal error: Attempted to serialize empty result.
  • MySQL upsert(): Internal error: Attempted to serialize empty result.
  • MongoDB upsert(): Internal error: Attempted to serialize empty result.
  • MongoDB upsert(): Internal error: Attempted to serialize empty result
  • Relation mode + upsert(): Internal error: Attempted to serialize empty result.
  • Internal error: Attempted to serialize empty result. on upsert() for update case in different databases (when using relationMode=prisma explicitly or implicitly [MongoDB])
  • Postgres upsert(): Internal error: Attempted to serialize empty result when relationMode = "prisma" is used
  • ✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using Powershell)

  Credits

  Huge thanks to @ ospfranco, @ pranayat, @ yubrot, @ skyzh, @ anuraaga, @ yehonatanz, @ arthurfiorette, @ elithrar, @ tockn, @ Kuhave, @ obiwac for helping!

• 5.13.0-integration-help-promo.3 - 2024-04-22
• 5.13.0-integration-help-promo.2 - 2024-04-22
• 5.13.0-integration-help-promo.1 - 2024-04-22
• 5.13.0-integration-exclude.2 - 2024-04-12
• 5.13.0-integration-exclude.1 - 2024-04-12
• 5.13.0-integration-engines-5-13-0-9-integration-multi-prisma-fmt-bfd6805a8c6880cd0161f6e57189b9fb8c6bcc7f.2 - 2024-04-09
• 5.13.0-integration-engines-5-13-0-9-integration-multi-prisma-fmt-bfd6805a8c6880cd0161f6e57189b9fb8c6bcc7f.1 - 2024-04-09
• 5.13.0-integration-engines-5-13-0-8-feat-exclude-selection-4dcfb875515e5fb2f92a6d294ae5a27098f97dd7.1 - 2024-04-09
• 5.13.0-integration-engines-5-13-0-4-integration-c-abi-47890da9156681a133402e7b4a5a3e27b8095ee1.1 - 2024-04-05
• 5.13.0-integration-engines-5-13-0-3-feat-exclude-selection-e76495825e7475c1f31801a6b5e233caa6edebb8.1 - 2024-04-04
• 5.13.0-integration-engines-5-13-0-19-feat-d1-compatible-sqlite-migration-61ede41e91f79e295f2ed2d4734286808784eb2e.1 - 2024-04-12
• 5.13.0-integration-engines-5-13-0-18-feat-exclude-selection-567a3e894bb45c200d072d568ea64adc3d8afb94.1 - 2024-04-11
• 5.13.0-integration-engines-5-13-0-17-feat-get-config-multi-file-be6e6284945aad03ebe0292e0e1aa8174e499d0b.1 - 2024-04-11
• 5.13.0-integration-engines-5-13-0-12-integration-multi-prisma-fmt-be1faff81ac8a57f8b2be5368d18c61807f5a295.2 - 2024-04-10
• 5.13.0-integration-engines-5-13-0-12-integration-multi-prisma-fmt-be1faff81ac8a57f8b2be5368d18c61807f5a295.1 - 2024-04-10
• 5.13.0-integration-engines-5-13-0-10-feat-exclude-selection-0e36efc9f3b5aa64f9d3911568b7280ae9c4505d.1 - 2024-04-09
• 5.13.0-integration-diff-output.8 - 2024-04-04
• 5.13.0-integration-diff-output.7 - 2024-04-04
• 5.13.0-integration-diff-output.6 - 2024-04-03
• 5.13.0-integration-diff-output.3 - 2024-04-03
• 5.13.0-integration-diff-output.2 - 2024-04-03
• 5.13.0-integration-diff-output.1 - 2024-04-03
• 5.13.0-dev.37 - 2024-04-22
• 5.13.0-dev.36 - 2024-04-22
• 5.13.0-dev.35 - 2024-04-22
• 5.13.0-dev.34 - 2024-04-22
• 5.13.0-dev.33 - 2024-04-14
• 5.13.0-dev.31 - 2024-04-12
• 5.13.0-dev.30 - 2024-04-11
• 5.13.0-dev.29 - 2024-04-11
• 5.13.0-dev.28 - 2024-04-11
• 5.13.0-dev.27 - 2024-04-10
• 5.13.0-dev.26 - 2024-04-10
• 5.13.0-dev.25 - 2024-04-10
• 5.13.0-dev.24 - 2024-04-10
• 5.13.0-dev.23 - 2024-04-10
• 5.13.0-dev.22 - 2024-04-09
• 5.13.0-dev.21 - 2024-04-09
• 5.13.0-dev.20 - 2024-04-09
• 5.13.0-dev.19 - 2024-04-08
• 5.13.0-dev.18 - 2024-04-08
• 5.13.0-dev.17 - 2024-04-05
• 5.13.0-dev.16 - 2024-04-05
• 5.13.0-dev.15 - 2024-04-05
• 5.13.0-dev.14 - 2024-04-05
• 5.13.0-dev.13 - 2024-04-04
• 5.13.0-dev.12 - 2024-04-04
• 5.13.0-dev.11 - 2024-04-03
• 5.13.0-dev.10 - 2024-04-03
• 5.13.0-dev.9 - 2024-04-03
• 5.13.0-dev.8 - 2024-04-03
• 5.13.0-dev.6 - 2024-04-03
• 5.13.0-dev.5 - 2024-04-03
• 5.13.0-dev.4 - 2024-04-03
• 5.13.0-dev.3 - 2024-04-03
• 5.13.0-dev.2 - 2024-04-03
• 5.13.0-dev.1 - 2024-04-03
• 5.12.1 - 2024-04-04
  

  Today, we are issuing the 5.12.1 patch release to fix two small problems with our new Cloudflare D1 support.

  Fixes in Prisma CLI

  Windows-only fix for new D1 specific flags for migrate diff and db pull

  The flags --from-local-d1 and --to-local-d1 for migrate diff and --local-d1 to db pull we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.

  📚 Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM

  New option for migrate diff: -o or --output

  We added a new parameter --output to migrate diff that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using > to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply. Using this new option, this problem can be avoided:

  npx prisma migrate diff --script --from-empty --to-schema-datamodel ./prisma/schema.prisma --output ./schema.sql

  Related issues:

  • ✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using PowerShell) #23702
  • prisma migrate resolve --applied not working on new project, migration ... could not be found.

from @prisma/client 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

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
eat-my-url	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 26, 2024 5:22am