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.19.1 to 5.20.0 #216

Merged

Conversation

vigneshshettyin
Copy link
Owner

snyk-top-banner

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

  • The recommended version was released on a month ago.

Release notes
Package name: @prisma/client
  • 5.20.0 - 2024-09-24

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

    Highlights

    strictUndefinedChecks in Preview

    With Prisma ORM 5.20.0, the Preview feature strictUndefinedChecks will disallow any value that is explicitly undefined and will be a runtime error. This change is direct feedback from this GitHub issue and follows our latest proposal on the same issue.

    To demonstrate the change, take the following code snippet:

    prisma.table.deleteMany({
      where: {
        // If `nullableThing` is nullish, this query will remove all data.
        email: nullableThing?.property,
      }
    })

    In Prisma ORM 5.19.0 and below, this could result in unintended behavior. In Prisma ORM 5.20.0, if the strictUndefinedChecks Preview feature is enabled, you will get a runtime error instead:

    Invalid \`prisma.user.findMany()\` invocation in
    /client/tests/functional/strictUndefinedChecks/test.ts:0:0
      XX })
      XX 
      XX test('throws on undefined input field', async () => {
    → XX   const result = prisma.user.deleteMany({
             where: {
               email: undefined
                      ~~~~~~~~~
             }
           })
    Invalid value for argument \`where\`: explicitly \`undefined\` values are not allowed."

    We have also introduced the Prisma.skip symbol, which will allow you to get the previous behavior if desired.

    prisma.table.findMany({
      where: {
        // Use Prisma.skip to skip parts of the query
        email: nullableEmail ?? Prisma.skip
      }
    })

    From Prisma ORM 5.20.0 onward, we recommend enabling strictUndefinedChecks, along with the TypeScript compiler option exactOptionalPropertyTypes, which will help catch cases of undefined values at compile time. Together, these two changes will help protect your Prisma queries from potentially destructive behavior.

    strictUndefinedChecks will be a valid Preview feature for the remainder of Prisma ORM 5. With our next major version, this behavior will become the default and the Preview feature will be “graduated” to Generally Available.

    If you have any questions or feedback about strictUndefinedChecks, please ask/comment in our dedicated Preview feature GitHub discussion.

    typedSql bug fix

    Thank you to everyone who has tried out our typedSql Preview feature and provided feedback! This release has a quick fix for typescript files generated when Prisma Schema enums had hyphens.

    Fixes and improvements

    Prisma

    Prisma Engines

    Credits

    Huge thanks to @ mcuelenaere, @ pagewang0, @ key-moon, @ pranayat, @ yubrot, @ thijmenjk, @ mydea, @ HRM, @ haaawk, @ baileywickham, @ brian-dlee, @ nickcarnival, @ eruditmorina, @ nzakas, and @ gutyerrez for helping!

  • 5.20.0-integration-otel-peer-deps.2 - 2024-09-06
  • 5.20.0-integration-otel-peer-deps.1 - 2024-09-05
  • 5.20.0-integration-fix-driver-adapters-breaking.1 - 2024-09-24
  • 5.20.0-integration-feat-strict-undefined-checks.2 - 2024-09-23
  • 5.20.0-integration-feat-strict-undefined-checks.1 - 2024-09-13
  • 5.20.0-integration-feat-no-nextjs-workaround.2 - 2024-09-06
  • 5.20.0-integration-feat-no-nextjs-workaround.1 - 2024-09-06
  • 5.20.0-integration-engines-5-20-0-9-integration-itx-refactor-51ed793416e8f8bd436b0a4802ba4e44d2c40263.2 - 2024-09-21
  • 5.20.0-integration-engines-5-20-0-9-integration-itx-refactor-51ed793416e8f8bd436b0a4802ba4e44d2c40263.1 - 2024-09-21
  • 5.20.0-integration-engines-5-20-0-6-integration-fix-planetscale-transactions-0deadde8739779d8360ea8c60d2b49693271abcf.2 - 2024-09-03
  • 5.20.0-integration-engines-5-20-0-6-integration-fix-planetscale-transactions-0deadde8739779d8360ea8c60d2b49693271abcf.1 - 2024-09-03
  • 5.20.0-integration-engines-5-20-0-5-integration-fix-planetscale-transactions-7cb8cc9f8e14bd5bde8f8f67c26ccace7c49a53f.2 - 2024-09-03
  • 5.20.0-integration-engines-5-20-0-5-integration-fix-planetscale-transactions-7cb8cc9f8e14bd5bde8f8f67c26ccace7c49a53f.1 - 2024-09-03
  • 5.20.0-integration-engines-5-20-0-2-integration-nested-transactions-70e4e8eaa9b1ca0ec042fa831bc2c81f668215a7.2 - 2024-08-29
  • 5.20.0-integration-engines-5-20-0-2-integration-nested-transactions-70e4e8eaa9b1ca0ec042fa831bc2c81f668215a7.1 - 2024-08-29
  • 5.20.0-integration-engines-5-20-0-13-integration-itx-refactor-412fc8ba6449e41c37627808a172c1f3daa46129.2 - 2024-09-24
  • 5.20.0-integration-engines-5-20-0-13-integration-itx-refactor-412fc8ba6449e41c37627808a172c1f3daa46129.1 - 2024-09-24
  • 5.20.0-dev.21 - 2024-09-24
  • 5.20.0-dev.20 - 2024-09-24
  • 5.20.0-dev.19 - 2024-09-24
  • 5.20.0-dev.18 - 2024-09-24
  • 5.20.0-dev.17 - 2024-09-24
  • 5.20.0-dev.16 - 2024-09-23
  • 5.20.0-dev.15 - 2024-09-13
  • 5.20.0-dev.14 - 2024-09-09
  • 5.20.0-dev.13 - 2024-09-09
  • 5.20.0-dev.12 - 2024-09-06
  • 5.20.0-dev.11 - 2024-09-05
  • 5.20.0-dev.10 - 2024-09-05
  • 5.20.0-dev.9 - 2024-09-05
  • 5.20.0-dev.8 - 2024-09-05
  • 5.20.0-dev.7 - 2024-09-05
  • 5.20.0-dev.6 - 2024-09-04
  • 5.20.0-dev.5 - 2024-09-04
  • 5.20.0-dev.4 - 2024-09-04
  • 5.20.0-dev.3 - 2024-09-02
  • 5.20.0-dev.2 - 2024-08-28
  • 5.20.0-dev.1 - 2024-08-28
  • 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

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:

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

See this package in npm:
@prisma/client

See this project in Snyk:
https://app.snyk.io/org/vigneshshettyin/project/f292640c-2272-4ab3-b7a3-dc7f2f3bba3e?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Oct 27, 2024

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 Oct 27, 2024 1:49am

@vigneshshettyin vigneshshettyin merged commit 5fc0125 into main Nov 3, 2024
7 checks passed
@vigneshshettyin vigneshshettyin deleted the snyk-upgrade-30133eb6fb072afd6c6e8c6c1f644a74 branch November 18, 2024 15:32
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