renovate[bot]
commented
2 weeks ago ⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: http-proxy-middleware@2.0.6
npm warn Found: @types/express@5.0.0
npm warn node_modules/@types/express
npm warn dev @types/express@"5.0.0" from the root project
npm warn 1 more (@types/serve-index)
npm warn
npm warn Could not resolve dependency:
npm warn peerOptional @types/express@"^4.17.13" from http-proxy-middleware@2.0.6
npm warn node_modules/http-proxy-middleware
npm warn http-proxy-middleware@"^2.0.3" from webpack-dev-server@4.15.2
npm warn node_modules/@docusaurus/core/node_modules/webpack-dev-server
npm warn
npm warn Conflicting peer dependency: @types/express@4.17.21
npm warn node_modules/@types/express
npm warn peerOptional @types/express@"^4.17.13" from http-proxy-middleware@2.0.6
npm warn node_modules/http-proxy-middleware
npm warn http-proxy-middleware@"^2.0.3" from webpack-dev-server@4.15.2
npm warn node_modules/@docusaurus/core/node_modules/webpack-dev-server
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: prisma-erd-generator@1.11.2
npm error Found: @prisma/client@6.1.0
npm error node_modules/@prisma/client
npm error @prisma/client@"^6.0.0" from the root project
npm error peer @prisma/client@"^2.14.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0" from @casl/prisma@1.5.1
npm error node_modules/@casl/prisma
npm error @casl/prisma@"^1.4.1" from the root project
npm error 1 more (@pothos/plugin-prisma)
npm error
npm error Could not resolve dependency:
npm error peer @prisma/client@"^4.0.0 || ^5.0.0" from prisma-erd-generator@1.11.2
npm error node_modules/prisma-erd-generator
npm error dev prisma-erd-generator@"^1.11.2" from the root project
npm error
npm error Conflicting peer dependency: @prisma/client@5.22.0
npm error node_modules/@prisma/client
npm error peer @prisma/client@"^4.0.0 || ^5.0.0" from prisma-erd-generator@1.11.2
npm error node_modules/prisma-erd-generator
npm error dev prisma-erd-generator@"^1.11.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-07T05_26_43_219Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-07T05_26_43_219Z-debug-0.log
github-actions[bot]
mikeallisonJS
This PR contains the following updates:
^5.2.0->^6.0.0^5.20.0->^6.0.0^5.2.0->^6.0.0Release Notes
prisma/prisma (@prisma/client)
### [`v6.1.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.1.0) [Compare Source](https://redirect.github.com/prisma/prisma/compare/6.0.1...6.1.0) 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. ```diff 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 @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` ```diff - import { PrismaInstrumentation } from '@prisma/instrumentation' + import { PrismaInstrumentation, registerInstrumentations } from '@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: - [Tests for tracing expanded and improved](https://redirect.github.com/prisma/prisma/issues/19224) - [Issues with Elastic APM addressed](https://redirect.github.com/prisma/prisma/issues/24715) - [Issues with Datadog tracer addressed](https://redirect.github.com/prisma/prisma/issues/22450) - [Prisma Client now respects `suppressTracing`](https://redirect.github.com/prisma/prisma/issues/17953) ##### Other issues We also have a number of other issues that were resolved outside of our `tracing` feature. - [Resolved type issues with the `PrismaNeonHTTP` adapter](https://redirect.github.com/prisma/prisma/issues/25514) - [`findUnique` returns `null` when used instead of `Promise.all`](https://redirect.github.com/prisma/prisma/issues/25662) - [Resolved an issue with the latest version of Alpine Linux](https://redirect.github.com/prisma/prisma/issues/25817) ##### Fixes and improvements ##### Prisma - [Tracing: Detailed report and profiling informations](https://redirect.github.com/prisma/prisma/issues/1711) - [Prisma Client Request Tracing Integration](https://redirect.github.com/prisma/prisma/issues/5956) - [Instrumentation error in production: `TypeError: parentTracer.getSpanLimits is not a function`](https://redirect.github.com/prisma/prisma/issues/14887) - [Prisma is using the internal `Span` constructor](https://redirect.github.com/prisma/prisma/issues/16309) - [Prisma Client doesn't put all OTEL trace spans under one parent span](https://redirect.github.com/prisma/prisma/issues/16791) - [Prisma trace has unaccounted time](https://redirect.github.com/prisma/prisma/issues/17853) - [`prisma:engine` spans do not respect `suppressTracing()`](https://redirect.github.com/prisma/prisma/issues/17953) - [`tracing: engine` spans don't pass through `Sampler`](https://redirect.github.com/prisma/prisma/issues/19088) - [Add tests for tracing and different ways to open the first connection (including internal spans)](https://redirect.github.com/prisma/prisma/issues/19224) - [Tracing: Long trailing delay in `prisma:client:operation`](https://redirect.github.com/prisma/prisma/issues/19580) - [`prisma:engine` spans are missing when there are multiple `new PrismaClient()` invocations](https://redirect.github.com/prisma/prisma/issues/20779) - [`parentTracer.getSpanLimits is not a function`](https://redirect.github.com/prisma/prisma/issues/21397) - [Support tracers not derived from `opentelemetry-sdk-trace-base` (e.g. Datadog tracer)](https://redirect.github.com/prisma/prisma/issues/22450) - [`traceparent` comments with multiple SQL statements](https://redirect.github.com/prisma/prisma/issues/24370) - [Make `@prisma/instrumentation` dependencies peer dependencies](https://redirect.github.com/prisma/prisma/issues/24373) - [Make sure `db.statement` attribute doesn't include the `traceparent` comment](https://redirect.github.com/prisma/prisma/issues/24375) - [\[Instrumentation\] `registerInstrumentations` uses the global provider instead of the one passed in](https://redirect.github.com/prisma/prisma/issues/24488) - [Instrumentation: Problems in working with Elastic APM](https://redirect.github.com/prisma/prisma/issues/24715) - [`PrismaNeonHTTP` adapter breaks on some types e.g. timestamp](https://redirect.github.com/prisma/prisma/issues/25514) - [Promise.all() returns null with findUnique()](https://redirect.github.com/prisma/prisma/issues/25662) - [Alpine Linux 3.21: `Prisma failed to detect the libssl/openssl version to use`](https://redirect.github.com/prisma/prisma/issues/25817) ##### Prisma Client - [Tracing operation duration bug under stress test](https://redirect.github.com/prisma/prisma/issues/16980) - [`@prisma/instrumentation` Type Error: `'InstrumentionNodeModuleDefintion' is not generic`](https://redirect.github.com/prisma/prisma/issues/24285) ### [`v6.0.1`](https://redirect.github.com/prisma/prisma/compare/6.0.0...6.0.1) [Compare Source](https://redirect.github.com/prisma/prisma/compare/6.0.0...6.0.1) ### [`v6.0.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.0.0) [Compare Source](https://redirect.github.com/prisma/prisma/compare/5.22.0...6.0.0) 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](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6) 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](https://www.prisma.io/blog/prisma-6-better-performance-more-flexibility-and-type-safe-sql). 🌟 **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%20v6.0.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.0.0) 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](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6).** ⚠️ ##### 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](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/many-to-many-relations#implicit-many-to-many-relations) in your Prisma schema, Prisma ORM maintains the [relation table](https://www.prisma.io/docs/orm/prisma-schema/data-model/relations/many-to-many-relations#relation-tables) 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](https://redirect.github.com/prisma/prisma/issues/25196). 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`](https://nodejs.org/api/buffer.html) with [`Uint8Array`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/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`](https://www.prisma.io/docs/orm/reference/error-reference#p2025) in [`findUniqueOrThrow()`](https://www.prisma.io/docs/orm/reference/prisma-client-reference#finduniqueorthrow) and [`findFirstOrThrow()`](https://www.prisma.io/docs/orm/reference/prisma-client-reference#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](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6).** ⚠️ ##### Preview features promoted to General Availability In this release, we are promoting a number of [Preview](https://www.prisma.io/docs/orm/more/releases#preview) features to [General Availability](https://www.prisma.io/docs/orm/more/releases#generally-available-ga). ##### `fullTextIndex` If you use the [full-text index](https://www.prisma.io/docs/orm/prisma-schema/data-model/indexes#full-text-indexes-mysql-and-mongodb) feature in your app, you can now remove `fullTextIndex` from the `previewFeatures` in your Prisma schema: ```diff generator client { provider = "prisma-client-js" - previewFeatures = ["fullTextIndex"] } ``` ##### `fullTextSearch` If you use the [full-text search](https://www.prisma.io/docs/orm/prisma-client/queries/full-text-search) feature with **MySQL** in your app, you can now remove `fullTextSearch` from the `previewFeatures` in your Prisma schema: ```diff 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`: ```diff generator client { provider = "prisma-client-js" - previewFeatures = ["fullTextSearch"] + previewFeatures = ["fullTextSearchPostgres"] } ``` ##### New features We are also releasing new features with this release: - [cuid2() support](https://redirect.github.com/prisma/prisma-engines/pull/5047) - [Include unused enum definitions in `prisma generate`'s output](https://redirect.github.com/prisma/prisma/pull/25740) - [Improved compatibility with Deno 2](https://redirect.github.com/prisma/prisma/pull/25734) ##### Company news ##### 🚀 Prisma Postgres is free during Early Access In case you missed it: We recently launched [Prisma Postgres](https://www.prisma.io/blog/announcing-prisma-postgres-early-access), 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](https://pris.ly/orm/survey/release-5-22).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR was generated by Mend Renovate. View the repository job log.