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

fix(deps): update prisma monorepo to v5.21.1 #201

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 6, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) 5.18.0 -> 5.21.1 age adoption passing confidence
prisma (source) 5.18.0 -> 5.21.1 age adoption passing confidence

Release Notes

prisma/prisma (@​prisma/client)

v5.21.1

Compare Source

  • Fixed a bug where migrations were not using shadow database correctly in some edge cases

v5.21.0

Compare Source

Today, we are excited to share the 5.21.0 release 🎉

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

Highlights
Better support for tracing in MongoDB

The tracing Preview feature now has full support for MongoDB with previously missing functionality now implemented. This is a part of the ongoing effort to stabilize this Preview feature and release it in General Availability.

tracing is a Preview feature that enables built-in support for OpenTelemetry instrumentation inside the Prisma Client and provides deep insights into the performance and timing of your queries. See our documentation for more information.

For an easy to use and zero-configuration tracing instrumentation tool with a dashboard that provides an overview of your queries, statistics, and AI-powered recommendations, try Prisma Optimize.

WebAssembly engine size decrease for edge functions

Due to recent changes, some users experienced a steep increase of the bundle size in Prisma 5.20 when using the driverAdapters Preview feature, going over the 1 MB limit on the free tier of Cloudflare Workers. This has now been fixed.

Fixes and improvements
Prisma Engines
Credits

Huge thanks to @​austin-tildei, @​LucianBuzzo, @​mcuelenaere, @​pagewang0, @​key-moon, @​pranayat, @​yubrot, @​skyzh for helping!

v5.20.0

Compare Source

🌟 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!

v5.19.1

Compare Source

Today, we are issuing the 5.19.1 patch release.

What's Changed

We've fixed the following issues:

Full Changelog: prisma/prisma@5.19.0...5.19.x, prisma/prisma-engines@5.19.0...5.19.x

v5.19.0

Compare Source

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 https://github.com/prisma/prisma-engines/pull/4970 and https://github.com/prisma/prisma/pull/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

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!


Configuration

📅 Schedule: Branch creation - "after 12pm and before 6pm on Saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.12.1 fix(deps): update prisma monorepo to v5.13.0 Apr 23, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.13.0 fix(deps): update prisma monorepo to v5.14.0 May 14, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.14.0 fix(deps): update prisma monorepo to v5.15.0 Jun 4, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.15.0 fix(deps): update prisma monorepo to v5.15.1 Jun 18, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.15.1 fix(deps): update prisma monorepo to v5.16.0 Jun 25, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.16.0 fix(deps): update prisma monorepo to v5.16.0 - autoclosed Jun 27, 2024
@renovate renovate bot closed this Jun 27, 2024
@renovate renovate bot deleted the renovate/prisma-monorepo branch June 27, 2024 09:24
@renovate renovate bot restored the renovate/prisma-monorepo branch June 27, 2024 16:13
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.16.0 - autoclosed fix(deps): update prisma monorepo to v5.16.0 Jun 27, 2024
@renovate renovate bot reopened this Jun 27, 2024
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from f332ca1 to 58fcee2 Compare June 27, 2024 19:37
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.16.0 fix(deps): update prisma monorepo to v5.16.1 Jun 27, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.16.1 fix(deps): update prisma monorepo to v5.16.2 Jul 9, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.16.2 fix(deps): update prisma monorepo to v5.17.0 Jul 16, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.17.0 fix(deps): update prisma monorepo to v5.17.0 - autoclosed Aug 4, 2024
@renovate renovate bot closed this Aug 4, 2024
@renovate renovate bot deleted the renovate/prisma-monorepo branch August 4, 2024 18:07
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.17.0 - autoclosed fix(deps): update prisma monorepo to v5.17.0 Aug 6, 2024
@renovate renovate bot reopened this Aug 6, 2024
@renovate renovate bot restored the renovate/prisma-monorepo branch August 6, 2024 16:47
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 58fcee2 to 06b1808 Compare August 6, 2024 19:33
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.17.0 fix(deps): update prisma monorepo to v5.18.0 Aug 6, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.18.0 fix(deps): update prisma monorepo to v5.18.0 - autoclosed Aug 26, 2024
@renovate renovate bot closed this Aug 26, 2024
@renovate renovate bot deleted the renovate/prisma-monorepo branch August 26, 2024 20:45
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.18.0 - autoclosed fix(deps): update prisma monorepo to v5.18.0 Aug 27, 2024
@renovate renovate bot reopened this Aug 27, 2024
@renovate renovate bot restored the renovate/prisma-monorepo branch August 27, 2024 16:26
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 06b1808 to c77980d Compare August 27, 2024 18:39
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.18.0 fix(deps): update prisma monorepo to v5.19.0 Aug 27, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.19.0 fix(deps): update prisma monorepo to v5.19.1 Sep 2, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.19.1 fix(deps): update prisma monorepo to v5.20.0 Sep 24, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.20.0 fix(deps): update prisma monorepo to v5.21.0 Oct 15, 2024
@renovate renovate bot changed the title fix(deps): update prisma monorepo to v5.21.0 fix(deps): update prisma monorepo to v5.21.1 Oct 17, 2024
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.

0 participants