fix(deps): update prisma monorepo to v6 (major) #243

renovate · 2024-11-28T22:23:49Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@prisma/client (source)	`^5.16.1` -> `^6.1.0`
prisma (source)	`^5.16.1` -> `^6.1.0`

Release Notes

prisma/prisma (@prisma/client)

`v6.1.0`

Compare Source

Today we're releasing Prisma ORM version 6.1.0

In this version our tracing Preview feature is being graduated to GA!

Highlights

Tracing goes GA

The tracing Preview feature is now stable. You now no longer have to include tracing in your set of enabled preview features.

generator client {
   provider        = "prisma-client-js"
-  previewFeatures = ["tracing"]
}

We have also changed some of the spans generated by Prisma Client. Previously, a trace would report the following spans:

prisma:client:operation
prisma:client:serialize
prisma:engine
prisma:engine:connection
prisma:engine:db_query
prisma:engine:serialize

Now, the following are reported:

prisma:client:operation
prisma:client:serialize
prisma:engine:query
prisma:engine:connection
prisma:engine:db_query
prisma:engine:serialize
prisma:engine:response_json_serialization

Additionally, we have made a few changes to our dependencies:

@opentelemetry/api is now a peer dependency instead of a regular dependency
registerInstrumentations in @opentelemetry/instrumentation is now re-exported by @prisma/instrumentation

After upgrading to Prisma ORM 6.1.0 you will need to add @opentelemetry/api to your dependencies if you haven't already:

npm install @&#8203;opentelemetry/api

You will also no longer need to have @opentelemetry/instrumentation if you only use registerInstrumentations. In this case you can import registerInstrumentations from @prisma/instrumentation

- import { PrismaInstrumentation } from '@&#8203;prisma/instrumentation'
+ import { PrismaInstrumentation, registerInstrumentations } from '@&#8203;prisma/instrumentation'

Bug fixes

Tracing related

As we're moving our tracing preview to GA, a number of issues have been resolved. Here are a few highlights:

Other issues

We also have a number of other issues that were resolved outside of our tracing feature.

Fixes and improvements

Prisma

Prisma Client

`v6.0.1`

Compare Source

`v6.0.0`

Compare Source

We’re excited to share the Prisma ORM v6 release today 🎉

As this is a major release, it includes a few breaking changes that may affect your application. Before upgrading, we recommend that you check out our upgrade guide to understand the impact on your application.

If you want to have an overview of what we accomplished since v5, check out our announcement blog post: Prisma 6: Better Performance, More Flexibility & Type-Safe SQL.

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

Breaking changes

⚠️ This section contains a list of breaking changes. If you upgrade your application to Prisma ORM v6 without addressing these, your application is going to break! For detailed upgrade instructions, check out the upgrade guide. ⚠️

Minimum supported Node.js versions

The new minimum supported Node.js versions for Prisma ORM v6 are:

for Node.js 18 the minimum supported version is 18.18.0
for Node.js 20 the minimum supported version is 20.9.0
for Node.js 22 the minimum supported version is 22.11.0

There is no official support for Node.js <18.18.0, 19, 21, 23.

Minimum supported TypeScript version

The new minimum supported TypeScript version for Prisma ORM v6 is: 5.1.0.

Schema change for implicit m-n relations on PostgreSQL

If you're using PostgreSQL and are defining implicit many-to-many relations in your Prisma schema, Prisma ORM maintains the relation table for you under the hood. This relation table has A and B columns to represent the tables of the models that are part of this relation.

Previous versions of Prisma ORM used to create a unique index on these two columns. In Prisma v6, this unique index is changing to a primary key in order to simplify for the default replica identity behaviour.

If you're defining implicit m-n relations in your Prisma schema, the next migration you'll create will contain ALTER TABLE statements for all the relation tables that belong to these relations.

Full-text search on PostgreSQL

The fullTextSearch Preview feature is promoted to General Availability only for MySQL. This means that if you're using PostgreSQL and currently make use of this Preview feature, you now need to use the new fullTextSearchPostgres Preview feature.

Usage of `Buffer`

Prisma v6 replaces the usage of Buffer with Uint8Array to represent fields of type Bytes. Make sure to replace all your occurrences of the Buffer type with the new Uint8Array.

Removed `NotFoundError`

In Prisma v6, we removed the NotFoundError in favor of PrismaClientKnownRequestError with error code P2025 in findUniqueOrThrow() and findFirstOrThrow(). If you've relied on catching NotFoundError instances in your code, you need to adjust the code accordingly.

New keywords that can't be used as model names: `async`, `await`, `using`

With this release, you can't use async, await and using as model names any more.

⚠️ For detailed upgrade instructions, check out the upgrade guide. ⚠️

Preview features promoted to General Availability

In this release, we are promoting a number of Preview features to General Availability.

`fullTextIndex`

If you use the full-text index feature in your app, you can now remove fullTextIndex from the previewFeatures in your Prisma schema:

generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["fullTextIndex"]
}

`fullTextSearch`

If you use the full-text search feature with MySQL in your app, you can now remove fullTextSearch from the previewFeatures in your Prisma schema:

generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]
}

If you are using it with PostgreSQL, you need to update the name of the feature flag to fullTextSearchPostgres:

generator client {  
  provider        = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]  
+ previewFeatures = ["fullTextSearchPostgres"]
}

New features

We are also releasing new features with this release:

Company news

🚀 Prisma Postgres is free during Early Access

In case you missed it: We recently launched Prisma Postgres, a serverless database with zero cold starts, a generous free tier, connection pooling, real-time events, and a lot more! It’s entirely free during the Early Access phase, try it now!

✨ Let us know what you think of Prisma ORM

We're always trying to improve! If you've recently used Prisma ORM, we'd appreciate hearing your thoughts about your experience via this 2min survey.

`v5.22.0`

Compare Source

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

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

Highlights

Further Tracing Improvements

In our ongoing effort to stabilize the tracing Preview feature, we’ve made our spans compliant with OpenTelemetry Semantic Conventions for Database Client Calls. This should lead to better compatibility with tools such as DataDog and Sentry.

We’ve also included numerous bug fixes that should make this Preview feature easier to work with.

Metrics bug fix

Occasionally, connection pool metrics would become negative or grow unbounded. In this release, connection pool metrics should stay consistent.

Connection Pool Timeout fix

In a specific case, there could be issues where fetching a new connection from the connection pool would time out, regardless of the state of the application and connection pool. If you have experience connection pool issues accessing a PostgreSQL database with TLS encryption in a resource-constrained environment (such as Function-as-a-Service offerings or very small VPS) this should resolve those issues.

Special thanks to @youxq for their pull request and help resolving this issue!

Join us

Looking to make an impact on Prisma in a big way? We're hiring!

Learn more on our careers page: https://www.prisma.io/careers

Fixes and improvements

Prisma Migrate

removing @unique in schema.prisma does not generate SQL to do so

Prisma

Credits

Huge thanks to @tmm1, @Takur0, @hinaloe, @andyjy, and @youxq for helping!

`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

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

Make sure that you have the latest version of prisma and @prisma/client installed:
```
npm install -D prisma@latest
npm install @&#8203;prisma/client@latest
```

Enable the typedSql Preview feature in your Prisma Schema.

   generator client {
     provider = "prisma-client-js"
     previewFeatures = ["typedSql"]
   }

Create a sql subdirectory of your prisma directory.
```
mkdir -p prisma/sql
```
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
```

Import your SQL query into your code with the @prisma/client/sql import:

   import { PrismaClient } from '@&#8203;prisma/client'
   import { getUsersWithPosts } from '@&#8203;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

https://github.com/prisma/prisma/issues/23742 fixes Prisma Client not supporting deeply nested some clauses when the relationJoins Preview feature was enabled.

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!

`v5.18.0`

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Native support for UUIDv7

Previous to this release, the Prisma Schema function uuid() did not accept any arguments and created a UUIDv4 ID. While sufficient in many cases, UUIDv4 has a few drawbacks, namely that it is not temporally sortable.

UUIDv7 attempts to resolve this issue, making it easy to temporally sort your database rows by ID!

To support this, we’ve updated the uuid() function in Prisma Schema to accept an optional, integer argument. Right now, the only valid values are 4 and 7, with 4 being the default.

model User {
  id   String @&#8203;id @&#8203;default(uuid()) // defaults to 4
  name String
}

model User {
  id   String @&#8203;id @&#8203;default(uuid(4)) // same as above, but explicit
  name String
}

model User {
  id   String @&#8203;id @&#8203;default(uuid(7)) // will use UUIDv7 instead of UUIDv4
  name String
}

Bug squashing

We’ve squashed a number of bugs this release, special thanks to everyone who helped us! A few select highlights are:

Fixes and improvements

Prisma

Support UUID v7

Language tools (e.g. VS Code)

Support fetching references for a model

Credits

Huge thanks to @mcuelenaere, @pagewang0, @Druue, @key-moon, @Jolg42, @pranayat, @ospfranco, @yubrot, @skyzh, @haaawk for helping!

`v5.17.0`

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

VSCode extension improvements

We’re happy to introduce some cool new features that will make your experience with the Prisma VSCode extension even better!

Find references across schema files

The ability to hop between references of a given symbol is really useful in application code and now with the introduction of multi-file schema, we think it’s the perfect time to bring this feature to the VSCode extension!

With the 5.17.0 release, you’ll now have the ability to use the native “find references” feature to find any usage of a given symbol

Added context on hover

When hovering over a symbol that references a view, type, enum, or any other block with multiple values, you’ll now see a handy pop out that shows what is in that block at a glance.

Additional quick fixes

We’ve taken some fixes made by the prisma format cli command and made them quick fixes available to the VSCode Extension. Now, when you have forget a back relation or relation scalar field, you’ll now see in real time what is wrong and have the option to fix it via the extension.

QueryRaw performance improvements

We’ve changed the response format of queryRaw to decrease its average size which reduces serialization CPU overhead.

When querying large data sets, we expect you to see improved memory usage and up to 2x performance improvements.

Fixes and improvements

Prisma Client

Remove or change This is the 10th instance of Prisma Client being started. Make sure this is intentional. warning

Prisma

Prisma generate option --allow-no-models doesn't work.

Language tools (e.g. VS Code)

LSP Rename incorrectly maps field name and appends character

Credits

Huge thanks to @key-moon, @pranayat, @yubrot, @skyzh for helping!

`v5.16.2`

Compare Source

Today, we are issuing the 5.16.2 patch release to fix an issue in Prisma client.

Fix in Prisma Client

nextjs app deployed to vercel edge can't import prisma WASM modul

Configuration

📅 Schedule: Branch creation - "before 6am" in timezone Asia/Jakarta, 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 bot added the meta: dependencies label Nov 28, 2024

renovate bot force-pushed the renovate/major-prisma-monorepo branch from 4facf8c to 7382cb1 Compare December 2, 2024 13:36

fix(deps): update prisma monorepo to v6

925b0e9

renovate bot force-pushed the renovate/major-prisma-monorepo branch from 7382cb1 to 925b0e9 Compare December 17, 2024 20:13

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update prisma monorepo to v6 (major) #243

fix(deps): update prisma monorepo to v6 (major) #243

renovate bot commented Nov 28, 2024 •

edited

Loading

fix(deps): update prisma monorepo to v6 (major) #243

Are you sure you want to change the base?

fix(deps): update prisma monorepo to v6 (major) #243

Conversation

renovate bot commented Nov 28, 2024 • edited Loading

Release Notes

Highlights

Tracing goes GA

Bug fixes

Tracing related

Other issues

Fixes and improvements

Prisma

Prisma Client

Breaking changes

Minimum supported Node.js versions

Minimum supported TypeScript version

Schema change for implicit m-n relations on PostgreSQL

Full-text search on PostgreSQL

Usage of Buffer

Removed NotFoundError

New keywords that can't be used as model names: async, await, using

Preview features promoted to General Availability

fullTextIndex

fullTextSearch

New features

Company news

🚀 Prisma Postgres is free during Early Access

✨ Let us know what you think of Prisma ORM

Highlights

Further Tracing Improvements

Metrics bug fix

Connection Pool Timeout fix

Join us

Fixes and improvements

Prisma Migrate

Prisma

Credits

Highlights

Better support for tracing in MongoDB

WebAssembly engine size decrease for edge functions

Fixes and improvements

Prisma Engines

Credits

Highlights

strictUndefinedChecks in Preview

typedSql bug fix

Fixes and improvements

Prisma

Prisma Engines

Credits

What's Changed

Highlights

Introducing TypedSQL

Bug fixes

Driver adapters and D1

Joins

Join us

Credits

Highlights

Native support for UUIDv7

Bug squashing

Fixes and improvements

Prisma

Language tools (e.g. VS Code)

Credits

Highlights

VSCode extension improvements

QueryRaw performance improvements

Fixes and improvements

Prisma Client

Prisma

Language tools (e.g. VS Code)

Credits

Fix in Prisma Client

Configuration

renovate bot commented Nov 28, 2024 •

edited

Loading

Usage of `Buffer`

Removed `NotFoundError`

New keywords that can't be used as model names: `async`, `await`, `using`

`fullTextIndex`

`fullTextSearch`

`strictUndefinedChecks` in Preview

`typedSql` bug fix