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.0 to 5.19.1 #38

Merged
merged 1 commit into from
Sep 24, 2024

Conversation

zntb
Copy link
Owner

@zntb zntb commented Sep 24, 2024

snyk-top-banner

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

  • The recommended version was released on 22 days 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!

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.0 to 5.19.1.

See this package in npm:
@prisma/client

See this project in Snyk:
https://app.snyk.io/org/zntb/project/5acc0edc-ccc6-4106-a123-86f5e9182059?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Sep 24, 2024

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

Name Status Preview Comments Updated (UTC)
next-auth-v5-tutorial ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 24, 2024 2:54am

@zntb zntb merged commit 061ff72 into main Sep 24, 2024
3 checks passed
@zntb zntb deleted the snyk-upgrade-7a122d246a8a7b1de05cf6dacf02a6ab branch September 24, 2024 10:31
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