search

RWTH-TIME / shoutout

Open transcription platform with scheduled audio processing
GNU General Public License v3.0
20 stars 2 forks source link

fix(deps): update all major npm dependencies (major) #56

Closed renovate[bot] closed 7 months ago

renovate[bot] commented 7 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) ^4.14.0 -> ^5.0.0 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) ^5.59.7 -> ^7.0.0 age adoption passing confidence
@typescript-eslint/parser (source) ^5.59.7 -> ^7.0.0 age adoption passing confidence
eslint-config-next (source) 13.4.2 -> 14.1.0 age adoption passing confidence
eslint-config-prettier ^8.8.0 -> ^9.0.0 age adoption passing confidence
eslint-plugin-prettier ^4.2.1 -> ^5.0.0 age adoption passing confidence
next (source) 13.4.2 -> 14.1.0 age adoption passing confidence
prettier (source) ^2.8.8 -> ^3.0.0 age adoption passing confidence
prisma (source) ^4.14.0 -> ^5.0.0 age adoption passing confidence

Release Notes

prisma/prisma (@​prisma/client) ### [`v5.9.1`](https://togithub.com/prisma/prisma/releases/tag/5.9.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.9.0...5.9.1) Today, we are issuing the `5.9.1` patch release. ##### Fixes in Prisma Client In `5.9.0` we have changed our conditional exports in `@prisma/client`. This resulted in broken types for TypesScript users using certain combinations of `module`/`moduleResolution` settings. Additionally, it also caused a regression for Next.js users which have encountered invalid error messages from our side. You can now try out `5.9.1` and let us know if you find a bug at https://pris.ly/prisma-prisma-bug-report - [\[5.9.0\] Getting strange types after generating #​22903](https://togithub.com/prisma/prisma/issues/22903) - [v5.9.0 / Don't generate type. And the error from the previous version is still there #​22896](https://togithub.com/prisma/prisma/issues/22896) - [\[5.9.0\] Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate. #​22893](https://togithub.com/prisma/prisma/issues/22893) - [`Error: Prisma Client is unable to run in an edge runtime. As an alternative, try Accelerate: https://pris.ly/d/accelerate.` #​22889](https://togithub.com/prisma/prisma/issues/22889) - [\[5.9.0\] All queries result in any type #​22888](https://togithub.com/prisma/prisma/issues/22888) - [Prisma edge runtime error #​22886](https://togithub.com/prisma/prisma/issues/22886) - [please how i cant fix this message issues #​22885](https://togithub.com/prisma/prisma/issues/22885) - [\[v5.9.0\] $extends always return any #​22884](https://togithub.com/prisma/prisma/issues/22884) - [\[5.9.0\] @​prisma/client in Next.js middleware #​22877](https://togithub.com/prisma/prisma/issues/22877) - [Error after Upgrading from 5.8.1 to 5.9.0 #​22875](https://togithub.com/prisma/prisma/issues/22875) - [\[5.9.0 Bug\] Prisma.TransactionClient appears to be missing types #​22870](https://togithub.com/prisma/prisma/issues/22870) Note: many issues are duplicates. ### [`v5.9.0`](https://togithub.com/prisma/prisma/releases/tag/5.9.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.8.1...5.9.0) Today, we are excited to share the `5.9.0` stable release 🎉  🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check) about the release.** This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks: - Improve the performance of relation queries by introducing JOINs (see [last release](https://togithub.com/prisma/prisma/releases/tag/5.8.0)). - Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our [survey](https://pris.ly/survey/edge-functions-release-notes-5-9-0)). ##### Highlights ##### Optimized result sets for more efficient queries We continue our efforts of the performance of Prisma Client queries. In [`5.1.0`](https://togithub.com/prisma/prisma/releases/tag/5.1.0), we introduced the `RETURNING` keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of `RETURNING` to SQLite and a broader range of queries for existing databases (e.g. `delete` on PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs: - [feat(qe): avoid extra select on delete queries](https://togithub.com/prisma/prisma-engines/pull/4595) - [feat(qe): enable queries with returning for sqlite](https://togithub.com/prisma/prisma-engines/pull/46) ##### SQL Server: Return proper error for unreachable database When trying migrate/introspect a SQL server instance that’s unreachable, Prisma ORM now returns the correct `P1001` error instead of failing without an error. Learn more in this PR: [SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url](https://togithub.com/prisma/prisma/issues/11407). ##### Fixes and improvements ##### Prisma Client - [Skip unnecessary `select` queries on create/update/delete](https://togithub.com/prisma/prisma/issues/8069) - [.prisma/client: Name can't start with a dot](https://togithub.com/prisma/prisma/issues/17685) - [Nested json is transformed to string when used “$type” key in object](https://togithub.com/prisma/prisma/issues/21454) - [Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit](https://togithub.com/prisma/prisma/issues/22610) ##### Prisma Migrate - [SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url](https://togithub.com/prisma/prisma/issues/11407) - [Prisma errors fetching table 'CHECK_CONSTRAINTS' (which only exists in MySQL 8.0.16+) in MySQL 8.0.14](https://togithub.com/prisma/prisma/issues/19775) - [`ERROR: column "..." being dropped, try again later` when applying migrations with CRDB 23.1](https://togithub.com/prisma/prisma/issues/20851) ##### Language tools (e.g. VS Code) - [Extension wrongfully suggests Json as a valid type completion on Sqlite](https://togithub.com/prisma/language-tools/issues/1638) ##### Company news ##### Test edge functions support in Early Access Today, the only way how to use Prisma ORM in edge functions (e.g. Cloudflare Workers or Vercel Edge Functions) is by using [Prisma Accelerate](https://www.prisma.io/data-platform/accelerate). However, we are actively working on making Prisma ORM compatible with edge functions natively as well. If you want to become an early tester, you can apply for the private Early Accessing program by taking this [survey](https://pris.ly/survey/edge-functions-release-notes-5-9-0). ##### We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing Last year, AWS announced the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on IPv6. [Learn more in this technical deep dive](https://www.prisma.io/blog/accelerate-ipv6-first) into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate. ##### Credits Huge thanks to [@​laplab](https://togithub.com/laplab), [@​Druue](https://togithub.com/Druue), [@​anuraaga](https://togithub.com/anuraaga), [@​onichandame](https://togithub.com/onichandame), [@​LucianBuzzo](https://togithub.com/LucianBuzzo), [@​RobertCraigie](https://togithub.com/RobertCraigie), [@​almeidx](https://togithub.com/almeidx), [@​victorgdb](https://togithub.com/victorgdb), [@​tinola](https://togithub.com/tinola), [@​sampolahtinen](https://togithub.com/sampolahtinen), [@​AikoRamalho](https://togithub.com/AikoRamalho), [@​petradonka](https://togithub.com/petradonka) for helping! ### [`v5.8.1`](https://togithub.com/prisma/prisma/releases/tag/5.8.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.8.0...5.8.1) Today, we are issuing the `5.8.1` patch release. ##### Fix in Prisma Client - [Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit](https://togithub.com/prisma/prisma/issues/22610). ### [`v5.8.0`](https://togithub.com/prisma/prisma/releases/tag/5.8.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.7.1...5.8.0) 🌟 **Help us spread the word about Prisma by starring the repo or [posting on X](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@​prisma%20release%20v5.8.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.8.0) about the release.** 🌟 ##### Highlights Happy New Year from your friends at Prisma! 🎊 In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉 ##### `relationJoins` improvements: Relation loading strategy per query (Preview) In version [5.7.0](https://togithub.com/prisma/prisma/releases/tag/5.7.0), we released `relationJoins` into Preview. The `relationJoins` feature enables support for `JOIN`s for relation queries. This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case. You can now load relation data using either of the following strategies: - `join` — uses `JOIN`s to fetch relation data - `query` — uses sub-queries to fetch relation data When the `relationJoins` Preview feature is enabled, by default, the relation fetching strategy used is `join`. You can override the default behavior by using the `relationLoadStrategy` query option. To get started, enable the Preview feature: ```tsx // schema.prisma generator client { provider = "prisma-client-js" previewFeatures = ["relationJoins"] } ``` … and specify the relation loading strategy for your query as follows: ```tsx await prisma.user.findMany({ relationLoadStrategy: 'query', include: { posts: true, }, }) ``` Try it out and [share your feedback](https://togithub.com/prisma/prisma/discussions/22288) and create a [bug report](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&projects=\&template=bug_report.yml) if you encounter any issues. ##### Survey: Edge functions support We’re working on bringing Edge function support to Prisma ORM and we would appreciate your input by [submitting a response to our survey](https://pris.ly/survey/edge-functions-release-notes). By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out. ##### Fixes and improvements ##### Prisma Client - [Log output of Node-API library engine is different](https://togithub.com/prisma/prisma/issues/9039) - [`target` and `timestamp` are undefined in `info` events in Data Proxy client](https://togithub.com/prisma/prisma/issues/18479) - [Wrong types of `timestamp` and `duration` in query events with Data Proxy](https://togithub.com/prisma/prisma/issues/18482) - [Using `citext` fields with neon database driver causes conversion error](https://togithub.com/prisma/prisma/issues/21807) - [Add FreeBSD 14 as a new platform](https://togithub.com/prisma/prisma/issues/22228) - [PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }](https://togithub.com/prisma/prisma/issues/22298) - [Int\[\] return as null](https://togithub.com/prisma/prisma/issues/22303) ##### Prisma Migrate - [Prisma Migrate errors with `Environment is non-interactive` when `VERCEL` env var is defined](https://togithub.com/prisma/prisma/issues/22380) ##### Language tools (e.g. VS Code) - [Add quickfix for `Error validating field 'id' in model 'Post': MongoDB '@​default(auto())' fields must have 'ObjectId' native type.`](https://togithub.com/prisma/language-tools/issues/1548) - [Append mention of update to "preview feature not known" error message](https://togithub.com/prisma/language-tools/issues/1612) ##### Credits Huge thanks to [@​anuraaga](https://togithub.com/anuraaga), [@​onichandame](https://togithub.com/onichandame), [@​LucianBuzzo](https://togithub.com/LucianBuzzo), [@​RobertCraigie](https://togithub.com/RobertCraigie), [@​fqazi](https://togithub.com/fqazi), [@​KhooHaoYit](https://togithub.com/KhooHaoYit), [@​alencardc](https://togithub.com/alencardc), [@​Oreilles](https://togithub.com/Oreilles), [@​tinola](https://togithub.com/tinola), [@​AikoRamalho](https://togithub.com/AikoRamalho), [@​luxaritas](https://togithub.com/luxaritas) for helping! ##### Company news ##### 🎉 A billion queries and counting: Prisma Accelerate [Prisma Accelerate](https://pris.ly/accelerate-home-orm-release-1), our global database cache has served over 1 billion queries since its General Availability launch. We’d like to give a shoutout to our team and everyone who’s been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024! ##### 🔮 Prisma ORM Ecosystem Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? [Let us know](https://prisma-data.typeform.com/to/DYEjFIVx). We would like to learn about it and feature it on our [Ecosystem page](https://www.prisma.io/ecosystem). ##### 💼 We’re hiring If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. Check out our [Careers page](https://prisma.io/careers) for open positions. ### [`v5.7.1`](https://togithub.com/prisma/prisma/releases/tag/5.7.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.7.0...5.7.1) Today, we are issuing the `5.7.1` patch release. This patch fixes multiple small problems in our `relationJoins` preview feature. If you ran into problems when testing `relationJoins` before, please give it another go with 5.7.1 and [share your feedback](https://togithub.com/prisma/prisma/discussions/22288) or create a [bug report](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&projects=\&template=bug_report.yml) if you encounter any issues. ##### Fixes in Prisma Client - [`relationJoins`: Int\[\] return as null](https://togithub.com/prisma/prisma/issues/22303) - [`relationJoins`: fails when filtering includes by isNot: null](https://togithub.com/prisma/prisma/issues/22311) - [`relationJoins`: "The table (not available) does not exist in the current database."](https://togithub.com/prisma/prisma/issues/22299) - [`relationJoins`: PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }](https://togithub.com/prisma/prisma/issues/22298) - [`relationJoins`: Inconsistent column data: Unexpected conversion failure from String to datetime. Reason: $trailing input](https://togithub.com/prisma/prisma/issues/22293) ### [`v5.7.0`](https://togithub.com/prisma/prisma/releases/tag/5.7.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.6.0...5.7.0) 🌟 **Help us spread the word about Prisma by starring the repo or [posting on X (formerly Twitter)](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@​prisma%20release%20v5.7.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.7.0) about the release.** ##### Highlights ✨ In this release, we improved the SQL queries Prisma Client generates for you with two new [Preview](https://www.prisma.io/docs/about/prisma/releases#preview) features, the [driver adapters](https://www.prisma.io/docs/concepts/components/database-drivers#driver-adapters), and support for the database drivers we currently support. 5.7.0 will be the last release of the year. Stay tuned for the next one in January! ✨ ##### Preview support for `JOIN`s for relation queries for PostgreSQL and CockroachDB We’re excited to announce Preview support for `JOIN`s in Prisma Client when querying relations. Support for `JOIN`s has been a [long-standing feature request](https://togithub.com/prisma/prisma/issues/5184), and this release adds support for PostgreSQL and CockroachDB. The upcoming releases will expand support for other databases Prisma supports. To get started using `JOIN`s, enable the Preview feature in your Prisma schema: ```prisma // schema.prisma generator client { provider = "prisma-client-js" previewFeatures = ["relationJoins"] } ``` Run `prisma generate` to regenerate Prisma Client and enable the Preview feature. Prisma Client will use a `JOIN` in your query to fetch relation data for a majority of the cases. **Example queries**
1-1 relation queries example **Prisma Client query** ```tsx await prisma.user.findUnique({ where: { id: 1 }, include: { profile: true } }) ``` **SQL** ```sql SELECT "t1"."id", "t1"."name", "User_profile"."__prisma_data__" AS "profile" FROM "public"."User" AS "t1" LEFT JOIN LATERAL ( SELECT COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__" FROM ( SELECT "t4"."__prisma_data__" FROM ( SELECT JSON_BUILD_OBJECT( 'id', "t3"."id", 'bio', "t3"."bio", 'userId', "t3"."userId" ) AS "__prisma_data__" FROM ( SELECT "t2".* FROM "public"."Profile" AS "t2" WHERE "t1"."id" = "t2"."userId" ) AS "t3" ) AS "t4" ) AS "t5" ) AS "User_profile" ON TRUE WHERE "t1"."id" = $1 LIMIT $2 ```
1-m relation queries example **Prisma Client query** ```tsx await prisma.user.findUnique({ where: { id: 1 }, include: { posts: true } }) ``` **SQL** ```sql SELECT "t1"."id", "t1"."name", "User_posts"."__prisma_data__" AS "posts" FROM "public"."User" AS "t1" LEFT JOIN LATERAL ( SELECT COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__" FROM ( SELECT "t4"."__prisma_data__" FROM ( SELECT JSON_BUILD_OBJECT( 'id', "t3"."id", 'title', "t3"."title", 'content', "t3"."content", 'published', "t3"."published", 'authorId', "t3"."authorId" ) AS "__prisma_data__" FROM ( SELECT "t2".* FROM "public"."Post" AS "t2" WHERE "t1"."id" = "t2"."authorId" /* root select */ ) AS "t3" /* inner select */ ) AS "t4" /* middle select */ ) AS "t5" /* outer select */ ) AS "User_posts" ON TRUE WHERE "t1"."id" = $1 LIMIT $2 ```
m-n relation queries example **Prisma Client query** ```tsx await prisma.post.findUnique({ where: { id: 1 }, include: { tags: true } }) ``` **SQL** ```sql SELECT "t1"."id", "t1"."title", "t1"."content", "t1"."published", "t1"."authorId", "Post_tags_m2m"."__prisma_data__" AS "tags" FROM "public"."Post" AS "t1" LEFT JOIN LATERAL ( SELECT COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__" FROM ( SELECT "Post_tags"."__prisma_data__" FROM "public"."_PostToTag" AS "t2" LEFT JOIN LATERAL ( SELECT JSON_BUILD_OBJECT('id', "t4"."id", 'name', "t4"."name") AS "__prisma_data__", "t4"."id" FROM ( SELECT "t3".* FROM "public"."Tag" AS "t3" WHERE "t2"."B" = "t3"."id" /* root select */ ) AS "t4" ) AS "Post_tags" ON TRUE WHERE "t2"."A" = "t1"."id" ) AS "Post_tags_m2m_1" ) AS "Post_tags_m2m" ON TRUE WHERE "t1"."id" = $1 LIMIT $2 ```
[Share your feedback](https://togithub.com/prisma/prisma/discussions/22288) and create a [bug report](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&projects=\&template=bug_report.yml) if you encounter any issues. ##### Prisma’s `distinct` option now uses SQL queries (Preview) From this release, Prisma Client’s `distinct` option now uses the native SQL `DISTINCT ON` for unordered queries with PostgreSQL and CockroachDB. The upcoming releases will expand support for the other databases that Prisma supports. Prisma Client already supports [querying for distinct records](https://www.prisma.io/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#select-distinct). However, Prisma Client took care of the post-processing for distinct records in memory. To get started, enable the Preview feature in your Prisma schema: ```prisma // schema.prisma generator client { provider = "prisma-client-js" previewFeatures = ["nativeDistinct"] } ``` Regenerate your Prisma Client to get started using the Preview feature. Given the following Prisma Client query: ```tsx await prisma.user.findMany({ distinct: ['role'], select: { role: true, }, }) ``` **Before 5.7.0** Previously, Prisma Client handled the post-processing to select distinct records in-memory. Therefore, the following query was generated and executed against your database: ```sql SELECT "public"."User"."id", "public"."User"."role"::text FROM "public"."User" WHERE 1 = 1 OFFSET $1 ``` **After 5.7.0** ```sql SELECT DISTINCT ON ("public"."User"."role") "public"."User"."id", "public"."User"."role"::text FROM "public"."User" WHERE 1 = 1 OFFSET $1 ``` [Share your feedback](https://togithub.com/prisma/prisma/discussions/22287) and create a [bug report](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&projects=\&template=bug_report.yml) if you encounter any issues. ##### Improved support for Netlify using Node.js v20 In this release, we improved Prisma support when deploying to Netlify on Node.js v20. Previously, the Prisma Client could not resolve the location of the Query Engine after deploying to Netlify when using Node.js v20. If you run into this issue, we recommend updating to Prisma v5.7.0. We recommend giving [this comment](https://togithub.com/prisma/prisma/issues/22244#issuecomment-1842847194) on GitHub a read if you are not yet able to upgrade Prisma, to learn how to get around the error. ##### Fixes and improvements ##### Prisma Client - [Update: `InterpretationError("Unable to convert expression result into a set of selection results", None)` (starting with 5.2.0)](https://togithub.com/prisma/prisma/issues/21182) - [Error when inserting record with array enum column after `TRUNCATE`ing the table on CockroachDB: `placeholder $1 already has type string, cannot assign Color`](https://togithub.com/prisma/prisma/issues/21901) - [Netlify deployment with Node 20 break Prisma (`Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x"`)](https://togithub.com/prisma/prisma/issues/22244) ##### Prisma - [Planetscale Driver doesn't work anymore after updating to 5.6.0 ](https://togithub.com/prisma/prisma/issues/21956) ##### Prisma Migrate - [`prisma debug` command does not show env variables declared in `.env` file](https://togithub.com/prisma/prisma/issues/21968) ##### Credits Huge thanks to [@​anuraaga](https://togithub.com/anuraaga), [@​onichandame](https://togithub.com/onichandame), [@​LucianBuzzo](https://togithub.com/LucianBuzzo), [@​RobertCraigie](https://togithub.com/RobertCraigie), [@​fqazi](https://togithub.com/fqazi), [@​KhooHaoYit](https://togithub.com/KhooHaoYit), [@​alencardc](https://togithub.com/alencardc), [@​Oreilles](https://togithub.com/Oreilles), [@​christianledgard](https://togithub.com/christianledgard), [@​skyzh](https://togithub.com/skyzh), [@​alula](https://togithub.com/alula), [@​AikoRamalho](https://togithub.com/AikoRamalho), [@​petradonka](https://togithub.com/petradonka) for helping! ##### Company news ##### 💼 We’re hiring! If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. We're hiring for the following roles: - [Manager: Developer Advocacy](https://boards.greenhouse.io/prisma/jobs/7051313002) - [Software Engineer](https://boards.greenhouse.io/prisma/jobs/7034499002) ### [`v5.6.0`](https://togithub.com/prisma/prisma/releases/tag/5.6.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.5.2...5.6.0) 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@​prisma%20release%20v5.6.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.6.0) about the release.** 🌟 ##### Highlights ##### Driver adapters improvements (Preview) In version [5.4.0](https://togithub.com/prisma/prisma/releases/tag/5.4.0), we released `driverAdapters` into Preview. The `driverAdapters` feature enables Prisma Client to access your database using JavaScript or Serverless database drivers. In this release, we fixed many bugs for the existing driver adapters. We appreciate all the community feedback that has helped us improve this feature! ##### PlanetScale serverless driver adapter improvements This release also introduces a small breaking change to the `@prisma/adapter-planetscale` package to improve its stability and performance. The serverless driver adapter will now use a connection pool instead of a single connection from PlanetScale’s serverless driver. In case you’re using the `@prisma/adapter-planetscale`, update your Prisma Client instance with the following: ```diff -import { connect } from '@​planetscale/database' +import { Client } from '@​planetscale/database' import { PrismaPlanetScale } from '@​prisma/adapter-planetscale' import { PrismaClient } from '@​prisma/client' import { fetch as undiciFetch } from 'undici'; -const connection = connect({ url: connectionString, fetch: undiciFetch }) +const client = new Client({ url: connectionString, fetch: undiciFetch }) -const adapter = new PrismaPlanetScale(connection) +const adapter = new PrismaPlanetScale(client) const prisma = new PrismaClient({ adapter }) ``` ##### Request for feedback We encourage you to try out the driver adapters and share your feedback to help us move it to General Availability in either of the following GitHub discussions: - [Neon](https://togithub.com/prisma/prisma/discussions/21346) - [PlanetScale](https://togithub.com/prisma/prisma/discussions/21347) - [Turso](https://togithub.com/prisma/prisma/releases#:~:text=Let%20us%20know%20what%20you%20think) Refer to [our docs](https://www.prisma.io/docs/concepts/components/database-drivers#driver-adapters) to learn more about driver adapters. ##### New `prisma debug` command This release introduces a new command: `prisma debug`. The command provides debugging information such as environment variables that Prisma Client, Prisma Migrate, Prisma CLI, and Prisma Studio use. The command is also useful when creating a bug report as the information complements the output of the `prisma -v` command. You can learn more about the command in our [docs](https://www.prisma.io/docs/reference/api-reference/command-reference#debug). ##### Read replicas extension improvements We also released [version 0.3.0](https://togithub.com/prisma/extension-read-replicas/releases/tag/v0.3.0) of the `@prisma/extension-read-replicas` package that contains the following improvements: - A new `$replica()` method that explicitly enables you to use a replica for your query. For example, by default, the `queryRaw` and `executeRaw` methods are forwarded to the primary database, as they could try to write to the database. You can use the `$replica()` method with either of the `*Raw` methods to explicitly execute your query against a replica instead of your primary database. - Validation for when there’s an empty list of replicas. - Webpack bundling fixes We want to thank you, our community members, for your contributions! 🙏 You can find additional information on the changes in the [extension’s release](https://togithub.com/prisma/extension-read-replicas/releases/tag/v0.3.0). You can learn more about the extension in the [announcement blog post](https://www.prisma.io/blog/read-replicas-prisma-client-extension-f66prwk56wow). ##### Package provenance npm has introduced [provenance statements](https://docs.npmjs.com/generating-provenance-statements) to improve supply-chain security and transparency of packages. This allows developers to verify where and how packages are built. Starting with the 5.6.0 release, all npm packages for Prisma ORM will be published with provenance statements. If you maintain a Prisma Client extension or generator, we encourage you to enable provenance statements when publishing to npm. ##### Fixes and improvements ##### Prisma Migrate - [Weird error message on `db push` with invalid connection string: Connection string redacted, weird grammar](https://togithub.com/prisma/prisma/issues/20230) - [Regression for MongoDB introspection in 5.4.0](https://togithub.com/prisma/prisma/issues/21441) - [Inconsistent datetime column data importing to Turso](https://togithub.com/prisma/prisma/issues/21552) - [`db pull --url=...` logs full connection string on `P4001 The introspected database was empty`](https://togithub.com/prisma/prisma/issues/21733) ##### Prisma Client - [`prisma_pool_connections_idle` reports misleading number](https://togithub.com/prisma/prisma/issues/21221) - [Update and read issues with `@prisma/adapter-planetscale`](https://togithub.com/prisma/prisma/issues/21592) - [5.5.0 regression: typescript error when trying to pass `PrismaPlanetScale` adapter to the constructor](https://togithub.com/prisma/prisma/issues/21613) - [5.5.0/1: `Error: sha256 checksum of https://binaries.prisma.sh/all_commits/475c616176945d72f4330c92801f0c5e6398dc0f/windows/query_en gine.dll.node.gz (zipped) should be 748d039badd0919d022fff7d554b66b6937b79035861a6ae9a80c5a95eee76f5 but is b867ad335ee6f58c6a38f665dd641c95e6adff3061f92b7613c62cae1c3362bb`](https://togithub.com/prisma/prisma/issues/21616) ##### Prisma CLI - [`prisma debug`](https://togithub.com/prisma/prisma/issues/21619) ##### Credits Huge thanks to [@​onichandame](https://togithub.com/onichandame), [@​LucianBuzzo](https://togithub.com/LucianBuzzo), [@​RobertCraigie](https://togithub.com/RobertCraigie), [@​fqazi](https://togithub.com/fqazi), [@​KhooHaoYit](https://togithub.com/KhooHaoYit), [@​alencardc](https://togithub.com/alencardc), [@​Oreilles](https://togithub.com/Oreilles), [@​christianledgard](https://togithub.com/christianledgard), [@​skyzh](https://togithub.com/skyzh), [@​alula](https://togithub.com/alula), [@​luxaritas](https://togithub.com/luxaritas), [@​Nasfame](https://togithub.com/Nasfame), [@​lukahartwig](https://togithub.com/lukahartwig), [@​steebchen](https://togithub.com/steebchen), [@​icanipa](https://togithub.com/icanipa) for helping! ##### Miscellaneous ##### Prisma Accelerate is now Generally Available We're excited to share that [Prisma Accelerate](https://pris.ly/accelerate-home-orm-release) is now Generally Available. Prisma Accelerate is a global database cache that's available in over 280 locations and provides scalable connection pooling for serverless and edge applications. Learn more in the [announcement blog post](https://pris.ly/accelerate-ga-post-orm-release). Sign up and try out [Prisma Accelerate](https://pris.ly/pdp-console-orm-release) ##### 💼 We’re hiring! If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. We're hiring for an [Engineering Manager: Prisma Data Platform](https://boards.greenhouse.io/prisma/jobs/7009408002). ### [`v5.5.2`](https://togithub.com/prisma/prisma/releases/tag/5.5.2) [Compare Source](https://togithub.com/prisma/prisma/compare/5.5.1...5.5.2) Today, we are issuing the `5.5.2` patch release. ##### Fix in Prisma CLI - [Error: sha256 checksum of https://binaries.prisma.sh/all_commits/475c616176945d72f4330c92801f0c5e6398dc0f/windows/query_en gine.dll.node.gz (zipped) should be 748d039badd0919d022fff7d554b66b6937b79035861a6ae9a80c5a95eee76f5 but is b867ad335ee6f58c6a38f665dd641c95e6adff3061f92b7613c62cae1c3362bb](https://togithub.com/prisma/prisma/issues/21616) ### [`v5.5.1`](https://togithub.com/prisma/prisma/releases/tag/5.5.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.5.0...5.5.1) Today, we are issuing the `5.5.1` patch release. ##### Fix in Prisma Client - [5.5.0 regression: typescript error when trying to pass PrismaPlanetScale adapter to the constructor](https://togithub.com/prisma/prisma/issues/21613) ### [`v5.5.0`](https://togithub.com/prisma/prisma/releases/tag/5.5.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.4.2...5.5.0) 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@​prisma%20release%20v5.5.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.5.0) about the release.** 🌟 ##### Highlights ##### Serverless database drivers improvements and request for feedback (Preview) In version [5.4.0](https://togithub.com/prisma/prisma/releases/tag/5.4.0), we released `driverAdapters` into Preview. The `driverAdapter` feature enables Prisma Client to access your database using other JavaScript or Serverless database drivers such as Neon, PlanetScale, and Turso. The driver adapters allow Prisma Client to connect to your database using protocols besides TCP, such as HTTP (PlanetScale and Turso) and WebSockets (Neon). You can learn more about the Preview feature from the [announcement blog post](https://www.prisma.io/blog/serverless-database-drivers-KML1ehXORxZV). In this release, we focused our efforts on fixing bugs and improving the stability of the Preview feature. We encourage you to try it out and share your feedback to help us move it to General Availability in either of the following GitHub discussions: - [Neon](https://togithub.com/prisma/prisma/discussions/21346) - [PlanetScale](https://togithub.com/prisma/prisma/discussions/21347) - [Turso](https://togithub.com/prisma/prisma/discussions/21345) ##### New flags for the `prisma init` command This release introduces 3 new flags you can provide when initializing Prisma in your project using the [`prisma init`](https://www.prisma.io/docs/reference/api-reference/command-reference#init) command: - `--generator-provider`: Defines the default generator to use - `--preview-features`: Specifies the default Preview features to use in your project - `--output`: Specifies the default output location for the generated client ##### Fixes and improvements ##### Prisma CLI - [Prisma init: allow setting generator provider value](https://togithub.com/prisma/prisma/issues/17737) ##### Prisma Client - [`prisma.model.count` does not type `distinct` correctly](https://togithub.com/prisma/prisma/issues/19598) - [Generate fails on 5.2 with unsupported type](https://togithub.com/prisma/prisma/issues/20993) - [Invalid `….findMany()` invocation: The column `j1.id` does not exist in the current database.](https://togithub.com/prisma/prisma/issues/21352) - [5.4.0 subquery has too many columns](https://togithub.com/prisma/prisma/issues/21356) - [One-to-Many relationship does not join on the specified field](https://togithub.com/prisma/prisma/issues/21366) - [Planetscale driver: unsupported column type NULL](https://togithub.com/prisma/prisma/issues/21369) ##### Credits Huge thanks to [@​onichandame](https://togithub.com/onichandame), [@​fqazi](https://togithub.com/fqazi), [@​KhooHaoYit](https://togithub.com/KhooHaoYit), [@​alencardc](https://togithub.com/alencardc), [@​Oreilles](https://togithub.com/Oreilles), [@​christianledgard](https://togithub.com/christianledgard), [@​skyzh](https://togithub.com/skyzh), [@​alula](https://togithub.com/alula), [@​michaelpoellath](https://togithub.com/michaelpoellath), [@​lukahartwig](https://togithub.com/lukahartwig), [@​steebchen](https://togithub.com/steebchen), [@​icanipa](https://togithub.com/icanipa), [@​jiashengguo](https://togithub.com/jiashengguo), [@​stephenwade](https://togithub.com/stephenwade) for helping! ##### 💼 We're hiring! If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. We're currently hiring for the following roles: - [Software Engineer](https://boards.greenhouse.io/prisma/jobs/6948042002) - [Senior Software Engineer (Rust)](https://boards.greenhouse.io/prisma/jobs/6940273002) - [Engineering Manager: Prisma Data Platform](https://boards.greenhouse.io/prisma/jobs/6927046002) ### [`v5.4.2`](https://togithub.com/prisma/prisma/releases/tag/5.4.2) [Compare Source](https://togithub.com/prisma/prisma/compare/5.4.1...5.4.2) Today, we are issuing the `5.4.2` patch release. #### Fix in Prisma Client - [5.4.0 subquery has too many columns](https://togithub.com/prisma/prisma/issues/21356) - [One-to-Many relationship does not join on the specified field](https://togithub.com/prisma/prisma/issues/21366) ### [`v5.4.1`](https://togithub.com/prisma/prisma/releases/tag/5.4.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.4.0...5.4.1) Today, we are issuing the `5.4.1` patch release. ##### Fix in Prisma Client - [Invalid `….findMany()` invocation: The column `j1.id` does not exist in the current database.](https://togithub.com/prisma/prisma/issues/21352) ##### Fix in `@prisma/adapter-planetscale` - [Planetscale driver: unsupported column type NULL](https://togithub.com/prisma/prisma/issues/21369) ### [`v5.4.0`](https://togithub.com/prisma/prisma/releases/tag/5.4.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.3.1...5.4.0) 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@​prisma%20release%20v5.4.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.4.0) about the release.** 🌟 ### **Highlights** #### Preview support for PlanetScale and Neon serverless database drivers We’re excited to announce [Preview](https://www.prisma.io/docs/about/prisma/releases#preview) support for the Neon and PlanetScale serverless database drivers. The PlanetScale and Neon serverless database drivers allow Prisma to connect to your database using protocols besides TCP — HTTP (PlanetScale) or WebSockets (Neon). To get started with the serverless database drivers, first enable the `driverAdapters` Preview feature flag in your Prisma schema: ```prisma // schema.prisma generator client { provider = "prisma-client-js" previewFeatures = ["driverAdapters"] } ``` Next, to set up Prisma Client to use the serverless database drivers: ##### **PlanetScale** Install the Prisma adapter for PlanetScale and [PlanetScale serverless database driver](https://togithub.com/planetscale/database-js), and undici: ```bash npm install @​prisma/adapter-planetscale @​planetscale/database undici ``` > Prisma ORM supports Node 16 and up. In Node 18 and up, `undici` is not needed. Ensure you update the host value in your connection string to `aws.connect.psdb.cloud`. You can learn more about this [here](https://planetscale.com/docs/tutorials/planetscale-serverless-driver#add-and-use-the-planetscale-serverless-driver-for-javascript-to-your-project). ```bash DATABASE_URL='mysql://johndoe:strongpassword@aws.connect.psdb.cloud/clear_nightsky?sslaccept=strict' ``` Update your Prisma Client instance to use the PlanetScale database driver: ```tsx // Import required dependencies import { connect } from '@​planetscale/database'; import { PrismaPlanetScale } from '@​prisma/adapter-planetscale'; import { PrismaClient } from '@​prisma/client'; import { fetch as undiciFetch } from 'undici'; // Initialize Prisma Client with the PlanetScale serverless database driver const connection = connect({ url: connectionString, fetch: undiciFetch }); const adapter = new PrismaPlanetScale(connection); const prisma = new PrismaClient({ adapter }); ``` ##### **Neon** Install the Prisma adapter for Neon, [Neon serverless database driver](https://togithub.com/neondatabase/serverless) and undici (WebSockets): ```bash npm install @​prisma/adapter-neon @​neondatabase/serverless undici ``` Update your Prisma Client instance to use the Neon serverless database driver: ```tsx // Import required dependencies import { Pool, neonConfig } from '@​neondatabase/serverless'; import { PrismaNeon } from '@​prisma/adapter-neon'; import { PrismaClient } from '@​prisma/client'; import { WebSocket } from 'undici' neonConfig.webSocketConstructor = WebSocket; // Initialize Prisma Client with the Neon serverless database driver const pool = new Pool({ connectionString: process.env.DATABASE_URL }); const adapter = new PrismaNeon(pool); const prisma = new PrismaClient({ adapter }); ``` Let us know your feedback about the [Neon](https://togithub.com/prisma/prisma/discussions/21346) or [Planetscale](https://togithub.com/prisma/prisma/discussions/21347) serverless database drivers in the linked GitHub discussions. Create a [bug report](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&projects=\&template=bug_report.yml) if you run into any issues. #### Early Access support for Turso [Turso](https://turso.tech/) is an edge-hosted, distributed database that's based on [libSQL](https://turso.tech/libsql), an open-source and open-contribution fork of SQLite, enabling you to bring data closer to your application and minimize query latency. Since support for Turso is in Early Access, there may be some rough edges which we’re still working on it to improve the API and overall support. Additionally, it is behind the `driverAdapters` Preview feature flag. Enable it to get started using Turso in your project: ```groovy // schema.prisma generator client { provider = "prisma-client-js" previewFeatures = ["driverAdapters"] } ``` Next, install the Prisma Client adapter for Turso and the `libSQL` database client ```bash npm install @​prisma/adapter-libsql @​libsql/client ``` Update your Prisma Client instance: ```tsx // Import required dependencies import { PrismaClient } from '@​prisma/client' import { PrismaLibSQL } from '@​prisma/adapter-libsql' import { createClient } from '@​libsql/client' // Create a new instance of the libSQL database client const libsql = createClient({ // @​ts-expect-error url: process.env.TURSO_DATABASE_URL, authToken: process.env.TURSO_AUTH_TOKEN }) // Create a Prisma "adapter" for libSQL const adapter = new PrismaLibSQL(libsql) // Pass the adapter option to the Prisma Client instance const prisma = new PrismaClient({ adapter }) ``` You can learn more on how to use Prisma together with Turso in the [announcement blog post](https://www.prisma.io/blog/prisma-turso-ea-support-rXGd_Tmy3UXX). Try it out! [Let us know what you think](https://togithub.com/prisma/prisma/discussions/21345) and create a [bug report](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&projects=\&template=bug_report.yml) if you run into any issues. #### Query performance improvements In our continued efforts to make Prisma Client faster, we identified and improved the performance of different types of queries. ##### Relation filters improvements We made the following improvements to relation filters: - Removed an unnecessary `INNER JOIN` used in relation filter queries (Big thank you to [@​KhooHaoYit](https://togithub.com/KhooHaoYit) for helping out) - Use of `LEFT JOIN`'s for to-one relations. Previously, Prisma made use of sub-queries to fetch data. **Example Prisma Client query** ```tsx prisma.comment.findMany({ where: { post: { author: { name: "John" } } } }) ``` **Before 5.4.0** ```sql SELECT "Comment"."id" FROM "Comment" WHERE ("Comment"."id") IN ( SELECT "t0"."id" FROM "Comment" AS "t0" INNER JOIN "Post" AS "j0" ON ("j0"."id") = ("t0"."postId") WHERE ( ("j0"."id") IN ( SELECT "t1"."id" FROM "Post" AS "t1" INNER JOIN "User" AS "j1" ON ("j1"."id") = ("t1"."userId") WHERE ( "j1"."name" = $ 1 AND "t1"."id" IS NOT NULL ) ) AND "t0"."id" IS NOT NULL ) ); ``` **After 5.4.0** ```sql SELECT "Comment"."id" FROM "Comment" LEFT JOIN "Post" AS "j1" ON ("j1"."id") = ("Comment"."postId") LEFT JOIN "User" AS "j2" ON ("j2"."id") = ("j1"."userId") WHERE ( "j2"."name" = $ 1 AND ("j2"."id" IS NOT NULL) AND ("j1"."id" IS NOT NULL) ); ``` If you’re interested in more details on the relation query filter improvements, you can take a look at [this pull request](https://togithub.com/prisma/prisma-engines/pull/4235). ##### Enum improvements on PostgreSQL and CockroachDB Previously, when an enum value was used in a query, our Postgres driver would make additional queries to resolve the enum types that were used. In this release, we’re making improvements by casting enums to `TEXT` to avoid the additional roundtrips when resolving the types. This change should have the most impact if you’re using `pgBouncer` or if you’re running Prisma in a serverless environment, where our Postgres driver can’t cache enum types information. **Prisma schema** ```groovy model User { id Int @​id @​default(cuid()) role Role } enum Role { User Admin } ``` **Prisma Client query** ```tsx await prisma.user.findMany({ where: { role: "Admin" } }) ``` **Before 5.4.0** ```sql -- Internal driver query SELECT t.typname, t.typtype, t.typelem, r.rngsubtype, t.typbasetype, n.nspname, t.typrelid FROM pg_catalog.pg_type t LEFT OUTER JOIN pg_catalog.pg_range r ON r.rngtypid = t.oid INNER JOIN pg_catalog.pg_namespace n ON t.typnamespace = n.oid WHERE t.oid = $1; -- Internal driver query SELECT enumlabel FROM pg_catalog.pg_enum WHERE enumtypid = $1 ORDER BY enumsortorder; -- Prisma Client query SELECT id, role FROM "User" WHERE role = $1; ``` **After 5.4.0** ```sql -- Prisma Client query SELECT id, role::text FROM "User" WHERE role = CAST($1::text AS "Role); ``` ##### Bulk delete improvements We optimized the `deleteMany` operation by: - Removing all `SELECT` queries used to fetch data that would be used as input for the `DELETE` operation. In some cases, this also improves index usage. - Removing the transaction previously used as it’s now a single atomic operation. **Prisma Client query** ```tsx await prisma.post.deleteMany({ where: { id: { gt: 1, lt: 10, } } }) ``` **Before 5.4.0** ```sql BEGIN SELECT id FROM "Post" WHERE id > 1 AND id < 10; SELECT id FROM "Post" WHERE id > 1 AND id < 10 AND id IN (<...select ids>); DELETE FROM "Post" WHERE id IN (<...select ids>) AND id > 1 AND id < 10; COMMIT ``` **After 5.4.0** ```sql DELETE FROM "Post" WHERE id > 1 AND id < 10; ``` ##### Upsert improvements We improved the `upsert` operation ([non-native database upsert](https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#database-upserts)) by removing a redundant `SELECT` query: **Prisma Client query** ```tsx await prisma.user.upsert({ where: { email: "john@doe.com" }, create: { email: "john@doe.com", firstName: "John" }, update: { firstName: "Johnny" }, }) ``` **Before 5.4.0** ```sql SELECT `User`.`id` FROM `User` WHERE `User`.`email` = ?; SELECT `User`.`id` FROM `User` WHERE `User`.`email` = ?; UPDATE `prisma`.`User` SET `firstName` = ? WHERE `prisma`.`User`.`id` IN (?) AND `prisma`.`User`.`email` = ?; SELECT `User`.`id` FROM `User` WHERE `User`.`id` = ?; ``` **After 5.4.0** ```sql SELECT `User`.`id` FROM `User` WHERE `User`.`email` = ?; UPDATE `prisma`.`User` SET `firstName` = ? WHERE `prisma`.`User`.`id` IN (?) AND `prisma`.`User`.`email` = ?; SELECT `User`.`id` FROM `User` WHERE `User`.`id` = ?; ``` #### Fixes and improvements ##### Prisma Client - [Unnecessary `SELECT` may be generated by `upsert()`](https://togithub.com/prisma/prisma/issues/5686) - [Inefficient deleteMany query generation](https://togithub.com/prisma/prisma/issues/7232) - [Prisma can generate an overly complex and inefficient query in some cases](https://togithub.com/prisma/prisma/issues/7894) - [`deleteMany` optimisation](https://togithub.com/prisma/prisma/issues/8239) - [CockroachDB: Highly Variable Query Response Times](https://togithub.com/prisma/prisma/issues/11317) - [Extremely poor relation where clause query](https://togithub.com/prisma/prisma/issues/14688) - [Enums loaded as part of transaction after `UPDATE`, slowing down transaction.](https://togithub.com/prisma/prisma/issues/14955) - [ MongoDB `deleteMany` seems to send 2 identical read queries first before triggering the actual delete](https://togithub.com/prisma/prisma/issues/15085) - [Query validation messages reference color output even if colors are not enabled](https://togithub.com/prisma/prisma/issues/17706) - [Prisma generates unnecessary subquery, which is inefficient](https://togithub.com/prisma/prisma/issues/17879) - [Unnecessary INNER JOIN when doing nested queries](https://togithub.com/prisma/prisma/issues/18343) - [Semver checks for yarn and typescript could potentially fail](https://togithub.com/prisma/prisma/issues/18751) - [Prisma overrides type caching when in PGBouncer mode, causing 9,000 enum queries per second on a production system](https://togithub.com/prisma/prisma/issues/19325) - [deleteMany generates double WHERE filter](https://togithub.com/prisma/prisma/issues/19950) - [Prisma generate command crashes with `RustPanic: RuntimeError: panicked at 'internal error: entered unreachable code', query-engine/prisma-models/src/field/scalar.rs:93:50`](https://togithub.com/prisma/prisma/issues/20037) - [Duplicated keys in `metrics` properties](https://togithub.com/prisma/prisma/issues/21069) - [Prisma Client extension with method override and `jest-mock-extended` or `vitest-mock-extended` expects `never` input ](https://togithub.com/prisma/prisma/issues/21136) ##### Language tools (e.g. VS Code) - [Auto-completion suggests attributes already present ](https://togithub.com/prisma/language-tools/issues/1326) - [Quick Fix: when `@@​schema` is defined in a block without the `schemas` attribute](https://togithub.com/prisma/language-tools/issues/1333) ##### Prisma Engines - [CockroachDB: get_columns can hit inefficiency inside pg_class](https://togithub.com/prisma/prisma-engines/issues/4250) #### Credits Huge thanks to [@​onichandame](https://togithub.com/onichandame), [@​fqazi](https://togithub.com/fqazi), [@​KhooHaoYit](https://togithub.com/KhooHaoYit), [@​alencardc](https://togithub.com/alencardc), [@​Oreilles](https://togithub.com/Oreilles), [@​christianledgard](https://togithub.com/christianledgard), [@​skyzh](https://togithub.com/skyzh), [@​alula](http

Configuration

📅 Schedule: Branch creation - " 18-21 * 5" in timezone Europe/Berlin, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

This PR has been generated by Mend Renovate. View repository job log here.