Commit 27710bd
authored
fix(deps): update all non-major dependencies (#108)
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs
from Renovate will soon appear from 'Mend'. Learn more
[here](https://redirect.github.com/renovatebot/renovate/discussions/37842).
This PR contains the following updates:
| Package | Change | Age | Confidence | Type | Update |
|---|---|---|---|---|---|
| [@commitlint/cli](https://commitlint.js.org/)
([source](https://redirect.github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/cli))
| [`^19.8.0` ->
`^19.8.1`](https://renovatebot.com/diffs/npm/@commitlint%2fcli/19.8.0/19.8.1)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | patch |
| [@commitlint/config-conventional](https://commitlint.js.org/)
([source](https://redirect.github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/config-conventional))
| [`^19.8.0` ->
`^19.8.1`](https://renovatebot.com/diffs/npm/@commitlint%2fconfig-conventional/19.8.0/19.8.1)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | patch |
| [@discordjs/builders](https://discord.js.org)
([source](https://redirect.github.com/discordjs/discord.js/tree/HEAD/packages/builders))
| [`^1.10.1` ->
`^1.11.3`](https://renovatebot.com/diffs/npm/@discordjs%2fbuilders/1.10.1/1.11.3)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | minor |
| [@prisma/client](https://www.prisma.io)
([source](https://redirect.github.com/prisma/prisma/tree/HEAD/packages/client))
| [`^6.6.0` ->
`^6.16.2`](https://renovatebot.com/diffs/npm/@prisma%2fclient/6.6.0/6.16.2)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | minor |
|
[@sapphire/decorators](https://redirect.github.com/sapphiredev/utilities/tree/main/packages/decorators)
([source](https://redirect.github.com/sapphiredev/utilities/tree/HEAD/packages/decorators))
| [`^6.1.1` ->
`^6.2.0`](https://renovatebot.com/diffs/npm/@sapphire%2fdecorators/6.1.1/6.2.0)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | minor |
|
[@sapphire/discord.js-utilities](https://redirect.github.com/sapphiredev/utilities/tree/main/packages/discord.js-utilities)
([source](https://redirect.github.com/sapphiredev/utilities/tree/HEAD/packages/discord.js-utilities))
| [`7.3.2` ->
`7.3.3`](https://renovatebot.com/diffs/npm/@sapphire%2fdiscord.js-utilities/7.3.2/7.3.3)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | patch |
|
[@sapphire/eslint-config](https://redirect.github.com/sapphiredev/utilities/tree/main/packages/eslint-config)
([source](https://redirect.github.com/sapphiredev/utilities/tree/HEAD/packages/eslint-config))
| [`^5.0.5` ->
`^5.0.6`](https://renovatebot.com/diffs/npm/@sapphire%2feslint-config/5.0.5/5.0.6)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | patch |
| [@sapphire/framework](https://www.sapphirejs.dev)
([source](https://redirect.github.com/sapphiredev/framework)) | [`5.3.3`
->
`5.3.7`](https://renovatebot.com/diffs/npm/@sapphire%2fframework/5.3.3/5.3.7)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | patch |
|
[@sapphire/plugin-api](https://redirect.github.com/sapphiredev/plugins/tree/main/packages/api)
([source](https://redirect.github.com/sapphiredev/plugins/tree/HEAD/packages/api))
| [`^8.0.0` ->
`^8.3.1`](https://renovatebot.com/diffs/npm/@sapphire%2fplugin-api/8.0.0/8.3.1)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | minor |
|
[@sapphire/plugin-logger](https://redirect.github.com/sapphiredev/plugins/tree/main/packages/logger)
([source](https://redirect.github.com/sapphiredev/plugins/tree/HEAD/packages/logger))
| [`^4.0.2` ->
`^4.1.0`](https://renovatebot.com/diffs/npm/@sapphire%2fplugin-logger/4.0.2/4.1.0)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | minor |
|
[@types/pg](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/pg)
([source](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/pg))
| [`^8.11.13` ->
`^8.15.5`](https://renovatebot.com/diffs/npm/@types%2fpg/8.11.13/8.15.5)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | minor |
| [discord.js](https://discord.js.org)
([source](https://redirect.github.com/discordjs/discord.js/tree/HEAD/packages/discord.js))
| [`~14.18.0` ->
`~14.22.1`](https://renovatebot.com/diffs/npm/discord.js/14.18.0/14.22.1)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | minor |
| [docker/login-action](https://redirect.github.com/docker/login-action)
| `v3.4.0` -> `v3.5.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| action | minor |
|
[eslint-plugin-prettier](https://redirect.github.com/prettier/eslint-plugin-prettier)
| [`^5.2.6` ->
`^5.5.4`](https://renovatebot.com/diffs/npm/eslint-plugin-prettier/5.2.6/5.5.4)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | minor |
| [lint-staged](https://redirect.github.com/lint-staged/lint-staged) |
[`^15.5.1` ->
`^15.5.2`](https://renovatebot.com/diffs/npm/lint-staged/15.5.1/15.5.2)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | patch |
| [node](https://nodejs.org)
([source](https://redirect.github.com/nodejs/node)) | [`22.14.0` ->
`22.20.0`](https://renovatebot.com/diffs/npm/node/v22.14.0/v22.20.0) |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| volta | minor |
| [prettier](https://prettier.io)
([source](https://redirect.github.com/prettier/prettier)) | [`^3.5.3` ->
`^3.6.2`](https://renovatebot.com/diffs/npm/prettier/3.5.3/3.6.2) |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | minor |
| [prisma](https://www.prisma.io)
([source](https://redirect.github.com/prisma/prisma/tree/HEAD/packages/cli))
| [`^6.6.0` ->
`^6.16.2`](https://renovatebot.com/diffs/npm/prisma/6.6.0/6.16.2) |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | minor |
|
[prisma-json-types-generator](https://arthur.run/prisma-json-types-generator)
([source](https://redirect.github.com/arthurfiorette/prisma-json-types-generator))
| [`^3.2.3` ->
`^3.6.1`](https://renovatebot.com/diffs/npm/prisma-json-types-generator/3.2.3/3.6.1)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| devDependencies | minor |
| [yarn](https://redirect.github.com/yarnpkg/berry)
([source](https://redirect.github.com/yarnpkg/berry/tree/HEAD/packages/yarnpkg-cli))
| [`4.9.1` ->
`4.10.3`](https://renovatebot.com/diffs/npm/yarn/4.9.1/4.10.3) |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| packageManager | minor |
| [zlib-sync](https://redirect.github.com/abalabahaha/zlib-sync) |
[`^0.1.9` ->
`^0.1.10`](https://renovatebot.com/diffs/npm/zlib-sync/0.1.9/0.1.10) |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
| dependencies | patch |
---
### Release Notes
<details>
<summary>conventional-changelog/commitlint
(@​commitlint/cli)</summary>
###
[`v19.8.1`](https://redirect.github.com/conventional-changelog/commitlint/blob/HEAD/@​commitlint/cli/CHANGELOG.md#1981-2025-05-08)
[Compare
Source](https://redirect.github.com/conventional-changelog/commitlint/compare/v19.8.0...v19.8.1)
##### Bug Fixes
- update dependency tinyexec to v1
([#​4332](https://redirect.github.com/conventional-changelog/commitlint/issues/4332))
([e49449f](https://redirect.github.com/conventional-changelog/commitlint/commit/e49449fa9452069cdbf194f94d536194d362a299))
</details>
<details>
<summary>conventional-changelog/commitlint
(@​commitlint/config-conventional)</summary>
###
[`v19.8.1`](https://redirect.github.com/conventional-changelog/commitlint/blob/HEAD/@​commitlint/config-conventional/CHANGELOG.md#1981-2025-05-08)
[Compare
Source](https://redirect.github.com/conventional-changelog/commitlint/compare/v19.8.0...v19.8.1)
**Note:** Version bump only for package
[@​commitlint/config-conventional](https://redirect.github.com/commitlint/config-conventional)
</details>
<details>
<summary>discordjs/discord.js (@​discordjs/builders)</summary>
###
[`v1.11.3`](https://redirect.github.com/discordjs/discord.js/releases/tag/%40discordjs/builders%401.11.3)
[Compare
Source](https://redirect.github.com/discordjs/discord.js/compare/@discordjs/builders@1.11.2...@discordjs/builders@1.11.3)
#### Bug Fixes
- **contextMenuCommands:** Remove regular expression validation
([#​10996](https://redirect.github.com/discordjs/discord.js/issues/10996))
([4906aae](https://redirect.github.com/discordjs/discord.js/commit/4906aaea4c0e6e868fa658d3359026eb662fbcb8))
###
[`v1.11.2`](https://redirect.github.com/discordjs/discord.js/compare/@discordjs/builders@1.11.1...@discordjs/builders@1.11.2)
[Compare
Source](https://redirect.github.com/discordjs/discord.js/compare/@discordjs/builders@1.11.1...@discordjs/builders@1.11.2)
###
[`v1.11.1`](https://redirect.github.com/discordjs/discord.js/compare/@discordjs/builders@1.11.0...@discordjs/builders@1.11.1)
[Compare
Source](https://redirect.github.com/discordjs/discord.js/compare/@discordjs/builders@1.11.0...@discordjs/builders@1.11.1)
###
[`v1.11.0`](https://redirect.github.com/discordjs/discord.js/blob/HEAD/packages/builders/CHANGELOG.md#discordjsbuilders1110---2025-04-25)
[Compare
Source](https://redirect.github.com/discordjs/discord.js/compare/@discordjs/builders@1.10.1...@discordjs/builders@1.11.0)
#### Features
- Components v2 in builders v1
([#​10787](https://redirect.github.com/discordjs/discord.js/issues/10787))
([118e682](https://redirect.github.com/discordjs/discord.js/commit/118e6826821b3b90f5923e40f167747e0658cfd1))
</details>
<details>
<summary>prisma/prisma (@​prisma/client)</summary>
###
[`v6.16.2`](https://redirect.github.com/prisma/prisma/releases/tag/6.16.2)
[Compare
Source](https://redirect.github.com/prisma/prisma/compare/6.16.1...6.16.2)
Today, we are issuing a 6.16.2 patch release.
##### Bug fixes
- In Prisma ORM 6.16.0, we've enabled usage of the new `engineType =
client` with Prisma Postgres, but our validation rules permitted invalid
combinations of Prisma Postgres URLs and driver adapters. This now
produces a clear error message indicating Prisma Postgres URLs and
driver adapters are mutually exclusive.
- In the previous minor release, we've included a change that calls
`unref()` on NodeJS timers to prevent them from keeping the NodeJS event
loop active. This change unintentionally affected non-NodeJS runtimes
like `workerd`, where it has resulted in runtime errors. This behavior
has been made conditional to prevent these runtime errors.
###
[`v6.16.1`](https://redirect.github.com/prisma/prisma/releases/tag/6.16.1)
[Compare
Source](https://redirect.github.com/prisma/prisma/compare/6.16.0...6.16.1)
Today, we are issuing a 6.16.1 patch release.
#### Bug fixes
- In Prisma ORM 6.16.0, the `driverAdapters` and `queryCompiler`
features were stabilized, but leftover code in the `prisma-client-ts`
generator required them to still be specified in edge runtimes. This has
now been fixed, runtimes like `workerd` and `vercel-edge` no longer
require these preview features.
###
[`v6.16.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.16.0)
[Compare
Source](https://redirect.github.com/prisma/prisma/compare/6.15.0...6.16.0)
Today, we are excited to share the `6.16.0` stable release 🎉
**🌟 Star this repo for notifications about new releases, bug fixes &
features — or [follow us on X](https://pris.ly/x)!**
#### Prisma ORM
This section contains all the updates made in Prisma ORM v6.16.0.
##### Rust-free ORM and driver adapters are Generally Available
Eight months ago, we published our [ORM
manifesto](https://www.prisma.io/blog/prisma-orm-manifesto) with the
first hint that we're going to remove the Rust-based query engine from
Prisma ORM:
> We're addressing this by migrating Prisma's core logic from Rust to
TypeScript and redesigning the ORM to make customization and extension
easier.
After a lot of hard work and feedback from the community, we're
incredibly excited to share that the migration has been completed and
you can now use Prisma ORM without its Rust engine in your production
apps. 🎉 This is a major milestone in the history of Prisma ORM and comes
with a lot of benefits:
- Reduced bundle size by \~90%
- Faster queries (check out our [latest
benchmarks](https://www.prisma.io/blog/prisma-orm-without-rust-latest-performance-benchmarks))
- Lower CPU footprint
- Less deployment complexity
- Easier to make open-source contributions
… and overall a much better DX since you don't need to worry about the
extra binary in your generated Prisma Client code any more.
While the Rust-free ORM will become the default in Prisma ORM v7 soon,
for now you still need to opt-into using it:
1. Configure the `generator` block in your Prisma schema:
```prisma
generator client {
provider = "prisma-client" // (or "prisma-client-js")
output = "../src/generated/prisma"
engineType = "client"
}
```
Note: If you tried the Rust-free ORM before, you can now also drop the
`queryCompiler` and `driverAdapter` feature flags from the
`previewFeatures` array. And if you used `binaryTargets`, you can also
get rid of these.
2. Install the [driver
adapter](https://www.prisma.io/docs/orm/overview/databases/database-drivers#driver-adapters)
for your database, e.g. to use [`pg`](https://node-postgres.com/) for
PostgreSQL:
```
npm install @​prisma/adapter-pg
```
3. Finally, you can instantiate `PrismaClient` using the `PrismaPg`
driver adapter as follows:
```ts
import { PrismaClient } from './generated/prisma'
import { PrismaPg } from '@​prisma/adapter-pg'
const adapter = new PrismaPg({ connectionString: env.DATABASE_URL })
const prisma = new PrismaClient({ adapter })
// ... send queries using `prisma` like before
```
📚 To learn more and see instructions for all other supported databases,
check out the
[documentation](https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engine).
> The Rust-free version of Prisma ORM has been thoroughly tested with
the `prisma-client` generator (see below), not with `prisma-client-js`.
Use the old generator at your discretion.
##### New ESM-first `prisma-client` generator is Generally Available
Another major milestone has been achieved in this release: The new,
flexible and ESM-first `prisma-client` generator is ready for production
too. Here's a quick overview of its main benefits:
- No more [magic generation into
`node_modules`](https://www.prisma.io/blog/why-prisma-orm-generates-code-into-node-modules-and-why-it-ll-change);
generated code is fully under control by the developer
- ESM-compatible by default
- Flexible configuration for specific runtimes (Node.js, Deno, Bun,
Cloudflare, …)
```prisma
generator client {
// Required
provider = "prisma-client"
output = "../src/generated/prisma"
// Optional
engineType = "client"
runtime = "nodejs"
moduleFormat = "esm"
generatedFileExtension = "ts"
importFileExtension = "ts"
}
```
In addition to making it production-ready, we also made some changes to
the `prisma-client` generator:
- removed `Prisma.validator`; you can use TypeScript native
[`satisfies`](https://www.prisma.io/blog/satisfies-operator-ur8ys8ccq7zb)
keyword instead
- created a new `./generared/prisma/browser` entrypoint for importing
types in browser environments
If you want to try out the new generator with your favorite framework,
check out one of our [ready-to-run
examples](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client)
(e.g. for
[Next.js](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/nextjs-starter-webpack-turborepo),
[Nuxt](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/nuxt3-starter-nodejs)
or [React
Router](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/react-router-starter-nodejs)).
📚 Learn more in the
[docs](https://www.prisma.io/docs/orm/prisma-schema/overview/generators#prisma-client).
##### Type check performance optimizations
Runtime performance is not the only performance category that matters.
In fact, when it comes to DX, type checking performance is equally
important: if your TypeScript types become too complex and the compiler
needs to do too much work (e.g. inferring types), it may slow down your
editor, lead to laggy auto-completion or prevent jump-to-definition from
working.
We've worked with TypeScript expert [David
Blass](https://x.com/ssalbdivad) to find ways for improving the type
checking performance in Prisma ORM and created benchmarks comparing the
type checking performance with Drizzle.
You can read about the results here: [**Why Prisma ORM Checks Types
Faster Than
Drizzle**](https://www.prisma.io/blog/why-prisma-orm-checks-types-faster-than-drizzle)
##### Deprecating the `postgresqlExtensions` Preview feature
We're deprecating the `postgresqlExtensions` Preview feature. Note that
this doesn't mean that you can't use extensions with Prisma ORM any
more. Instead of setting the Preview feature, you can install extensions
manually with a [customized
migration](https://www.prisma.io/docs/orm/prisma-migrate/workflows/customizing-migrations)
via the `--create-only` flag:
```
npx prisma migrate dev --name add-extension --create-only
```
You can then install an extension with plain SQL in the newly created,
empty migration file:
```sql
CREATE EXTENSION IF NOT EXISTS "pgcrypto";
```
#### Prisma Postgres
[Prisma Postgres](https://www.prisma.io/postgres) is our fully managed
Postgres service designed with the same philosophy of great DX that has
guided Prisma for close to a decade. With this release we are
introducing the following improvements:
##### Manage OAuth apps in Prisma Console
[In Prisma Console](https://console.prisma.io), you can now manage all
of the 3rd party applications that you've granted access to perform
actions on behalf of yourself in your Prisma Console account. Find the
🧩 **Integrations** tab in the sidenav to see which applications
currently have access.
##### Rust-free Prisma ORM with Prisma Accelerate and Prisma Postgres
With this release, the Rust-free Prisma ORM (Query Compiler) can now be
used together with Prisma Postgres and also Prisma Accelerate. This
means you can take advantage of connection pooling and caching while
using the new TypeScript-based ORM architecture.
To enable it, update your Prisma schema:
```prisma
generator client {
provider = "prisma-client"
output = "../src/generated/prisma"
engineType = "client"
}
```
We'd love for you to try this out and share your feedback as we prepare
for General Availability. Please [open an issue on
GitHub](https://redirect.github.com/prisma/prisma/issues) if you
encounter any problems or have suggestions.
#### Enterprise support
Thousands of teams use Prisma and many of them already tap into our
Enterprise & Agency Support Program for hands-on help with everything
from schema integrations and performance tuning to security and
compliance.
With this program you also get priority issue triage and bug fixes,
expert scalability advice, and custom training so that your
Prisma-powered apps stay rock-solid at any scale. Learn more or
join: <https://prisma.io/enterprise>.
###
[`v6.15.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.15.0)
[Compare
Source](https://redirect.github.com/prisma/prisma/compare/6.14.0...6.15.0)
Today, we are excited to share the `6.15.0` stable release 🎉
**🌟 Star this repo for notifications about new releases, bug fixes &
features — or [follow us on X](https://pris.ly/x)!**
#### Highlights
##### AI safety guardrails for destructive commands
Prisma ORM now includes built-in safety checks that protect against
destructive commands when triggered by AI coding assistants. The CLI can
recognize when it is being executed by popular AI agents such as Claude
Code, Gemini CLI, Qwen Code, Cursor, Aider and Replit.
If a command like `prisma migrate reset --force` is attempted, Prisma
ORM will prompt for explicit confirmation before proceeding.
This feature ensures that irreversible operations which drop and
recreate the database are not executed automatically by an AI tool.
Prisma ORM is the first ORM to provide this level of protection, making
it safer to use AI-assisted development while working with your
databases.
📚 Learn more [in the
docs](https://www.prisma.io/docs/orm/reference/prisma-cli-reference#ai-safety-guardrails-for-prisma-migrate-reset).
##### `prisma-client`: runtime improvements and schema flexibility
We simplified Prisma ORM by making the runtime options for the Prisma
Client more consistent and easier to understand. Previously there were
several overlapping aliases which created confusion. With this release
we simplified the inputs while keeping support for all the major
environments you might be targeting.
Changes include:
- `node` has been removed, use `runtime = "nodejs"` instead
- `deno-deploy` has been removed, use `runtime = "deno"` instead
- `vercel` has been replaced by the new `runtime = "vercel-edge"`
- `edge-light` is now just an alias for `vercel-edge`
- `nodejs`, `deno`, and `bun` now share the same internal code path,
while still keeping their separate input values for clarity
- The VS Code extension has been updated to reflect these changes
The updated list of supported runtimes is now:
`nodejs`, `deno`, `bun`, `workerd` (alias `cloudflare`), `vercel-edge`
(alias `edge-light`), and `react-native`.
In addition, we fixed an issue where running `prisma generate` would
fail if your schema contained no models. This is now supported with the
new `prisma-client` generator, just like it already worked with the
older `prisma-client-js` generator.
For example, the following schema will now generate a client without
errors:
```prisma
generator client {
provider = "prisma-client"
output = "../generated/client"
}
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
```
Running `prisma generate` with this schema will succeed and create the
client in `./generated/client`.
📚 Learn more [in the
docs](https://www.prisma.io/docs/orm/prisma-schema/overview/generators#prisma-client-preview).
##### Using Prisma ORM with Vercel Fluid
[Fluid compute](https://vercel.com/fluid) is a new compute model from
Vercel that combines the flexibility of serverless with the stability of
servers, making it ideal for dynamic workloads such as streaming data
and AI APIs.
A common challenge in traditional serverless platforms is that when
functions are suspended, database connection pools can’t close idle
connections. This leads to leaked connections that stay open until the
database times them out, which can exhaust the pool.
Vercel provides the
[`attachDatabasePool`](https://vercel.com/blog/the-real-serverless-compute-to-database-connection-problem-solved)
utility to solve this problem. It ensures idle connections in the pool
are properly released before a function is suspended, preventing
connection leaks.
You can use this utility together with Prisma’s driver adapters to
safely manage database connections in Fluid Compute:
```ts
import { Pool } from "pg";
import { attachDatabasePool } from "@​vercel/functions";
import { PrismaPg } from "@​prisma/adapter-pg";
import { PrismaClient } from "./generated/prisma/client";
const pool = new Pool({ connectionString: process.env.POSTGRES_URL });
attachDatabasePool(pool);
const prisma = new PrismaClient({
adapter: new PrismaPg(pool),
});
```
📚 Learn more [in the
docs](https://www.prisma.io/docs/orm/prisma-client/deployment/serverless/deploy-to-vercel#using-prisma-orm-with-vercel-fluid).
#### Other news
##### Prisma Postgres Management API is Generally Available
The Prisma Postgres Management API allows you to
[programmatically](https://www.prisma.io/docs/guides/management-api-basic)
provision and manage Prisma Postgres instances. It’s the perfect way to
spin up a database in your CI/CD workflow, see our GitHub Action
examples for
[creating](https://redirect.github.com/marketplace/actions/create-prisma-postgres-database)
and
[deleting](https://redirect.github.com/marketplace/actions/delete-prisma-postgres-database)
if you’re curious about this use case.
It also enables developers to offer databases to their own users! For
example, did you know that [Co.dev](http://co.dev/) (YC23), a popular
“low-code AI app builder” is [using the Management API to provision
Prisma Postgres instances to people building apps with their
platform](https://www.prisma.io/blog/how-co-dev-uses-prisma-postgres-to-power-ai-driven-app-development-for-non-developers)?
We’re excited to share that the Management API is now fully ready for
production. With it moving into GA, we also added another piece of
functionality where you can now create new projects without a default
database.
We’re looking forward to see what you’re going to build with it!
📚 Learn more [in the
docs](https://www.prisma.io/docs/postgres/introduction/management-api).
##### Prisma Postgres is now available on Pipedream
Prisma Postgres can now be used directly in your Pipedream workflows 🎉
With this integration, you can connect Prisma Postgres to over 2,800+
apps supported on Pipedream, enabling powerful automations and data
workflows. For example, you can:
- Automatically spin up a new Prisma Postgres database when a customer
signs up in Stripe.
- Connect Prisma Postgres with Slack, Notion, Airtable, or any other app
in the Pipedream ecosystem
This makes it easier than ever to use Prisma Postgres in your automation
pipelines, without needing to manage custom scripts or infrastructure.
📚 Learn more [on the Pipedream integration
page](https://pipedream.com/apps/prisma-management-api).
<img width="1624" height="994" alt="Screenshot 2025-08-26 at 3 15 19 PM"
src="https://github.com/user-attachments/assets/f0d98f8f-362d-4887-baeb-019ed9625c66"
/>
##### New `--json` flag for `npx create-db`
The `npx create-db` command lets you spin up a temporary,
production-ready Prisma Postgres database that you can later claim for
continued use. With this release, you can now add the `--json` flag to
return the database details in JSON format.
This makes it straightforward to programmatically use the connection
details, whether you are building custom APIs or integrating database
provisioning into your workflows.
📚 Learn more [in the
docs](https://www.prisma.io/docs/postgres/introduction/npx-create-db).
##### Direct connections to Prisma Postgres are coming close to GA
Direct connections enable you to connect to your database using any ORM
library or tool of your choice (e.g. Drizzle ORM, Kysely but also
database GUIs like Postico or TablePlus).
In this release, we’ve improved the robustness of direct TCP connections
and are close to bringing it to General Availability.
📚 Learn more [in the
docs](https://www.prisma.io/docs/postgres/database/direct-connections).
#### Enterprise support
Thousands of teams use Prisma and many of them already tap into our
Enterprise & Agency Support Program for hands-on help with everything
from schema integrations and performance tuning to security and
compliance.
With this program you also get priority issue triage and bug fixes,
expert scalability advice, and custom training so that your
Prisma-powered apps stay rock-solid at any scale. Learn more or
join: <https://prisma.io/enterprise>.
###
[`v6.14.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.14.0)
[Compare
Source](https://redirect.github.com/prisma/prisma/compare/6.13.0...6.14.0)
Today, we are excited to share the `6.14.0` stable release 🎉
**🌟 Star this repo for notifications about new releases, bug fixes &
features — or [follow us on X](https://pris.ly/x)!**
#### Highlights
##### `@unique` attributes for SQL views (Preview)
[Last release](https://pris.ly/release/6.13.0), we improved the
robustness of [SQL
views](https://www.prisma.io/docs/orm/prisma-schema/data-model/views)
defined in the Prisma schema. Views are *virtual* tables that don't
allows for defining unique constraints, indexes or foreign keys in the
underlying database.
However, as an application developer, it can be convenient to also
define relationships involving views or paginate them using cursors.
We've received this feedback from several people who had been using
views in that way with Prisma ORM, so in this release we're
re-introducing the `@unique` attribute for views. This attribute
enables:
- relationships involving views
- `findUnique` queries, cursor-based pagination & implicit ordering for
views
Here's an example schema using `@unique` and defining a relationship
from a model to a view:
```prisma
model User {
id Int @​id @​default(autoincrement())
email String @​unique
posts Post[]
stats UserPostStats? @​relation(fields: [email], references: [userEmail])
}
model Post {
id Int @​id @​default(autoincrement())
title String
published Boolean @​default(false)
createdAt DateTime @​default(now())
authorId Int?
author User? @​relation(fields: [authorId], references: [id])
}
view UserPostStats {
userEmail String @​unique
totalPosts BigInt?
publishedPosts BigInt?
unpublishedPosts BigInt?
latestPostDate DateTime? @​db.Timestamp(6)
user User?
}
```
<details><summary>Expand to view the SQL code for this view</summary>
```sql
CREATE OR REPLACE VIEW "UserPostStats" AS
SELECT
u.email AS "userEmail",
u.name AS "userName",
COUNT(p.id) AS "totalPosts",
COUNT(CASE WHEN p.published = true THEN 1 END) AS "publishedPosts",
COUNT(CASE WHEN p.published = false THEN 1 END) AS "unpublishedPosts",
MAX(p."createdAt") AS "latestPostDate"
FROM "User" u
LEFT JOIN "Post" p ON u.id = p."authorId"
GROUP BY u.id, u.email, u.name;
```
</details>
You can now query this view and its relationship using `include`:
```ts
const userPostStats = await prisma.userPostStats.findMany({
include: {
user: true,
}
})
```
📚 Learn more in the
[docs](https://www.prisma.io/docs/orm/prisma-schema/data-model/views).
##### Various fixes & stability improvements
- Fixed several issues related to new `prisma-client` generator and
the `queryCompiler` Preview feature (aka “Prisma Client without Rust
engines”). Both will become the default in the upcoming Prisma 7 release
and we're working hard on bringing these features into General
Availability. You can try them out with your favorite stack with our
[ready-to-run
examples](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client).
- Fixed several regressions, e.g. related to Prisma Config
- Removed middleware from Prisma Client (i.e. the `prisma.$use` method),
which was deprecated since v4.16.0. Use [Prisma Client
extensions](https://www.prisma.io/docs/orm/prisma-client/client-extensions)
instead.
- Deprecated `metrics` Preview feature (which will be removed in Prisma
7)
##### Improved type performance
In this release, we also addressed some type performance issues that led
to slower editors and lagging auto-complete. If you're curious about the
details, you can check the description and changes in [this
PR](https://redirect.github.com/prisma/prisma/pull/27777).
#### Other news
##### Increased robustness of Management API (Early Access)
We recently released an [API for programmatically managing Prisma
Postgres
instances](https://www.prisma.io/docs/postgres/introduction/management-api)
that's perfect for CI/CD workflows and scripting.
In this release, we made it more robust and are bringing it closer to
its General Availability release.
##### Revoke OAuth tokens in Prisma Console
If you use OAuth to authorize third-party applications to act on your
behalf in the Prisma Console, you can now revoke any app's access at any
time. The Prisma Console shows a list of your authorized (connected)
apps, and you can easily remove one to immediately block further access.
#### ICYMI
[Last release](https://pris.ly/release/6.14.0) was *huge*, so just in
case you missed it, here's the TLDR of what we put out last time:
- **Prisma ORM**
- **Prisma Config file (`prisma.config.ts`) is Generally Available** –
Native way to configure schema paths, migrations, seeds, and more; no
need for `earlyAccess` flag anymore.
- **Multi-schema support is Generally Available** – Allows assigning
models to different database schemas in Postgres and SQL Server using
`@@​schema`.
- **Improved SQL views support (still in Preview)** – Adds guardrails
for views by disabling unsupported features.
- **Externally managed tables** – Lets you exclude specific tables from
Prisma Migrate while still querying them via Prisma Client.
- **Prisma Postgres**
- **Extension support for Prisma Postgres** – Prisma Postgres now
supports `pgvector`, `pg_search`, `pg_stat_statements`, `citext`, `pg_trgm`, `fuzzystrmatch`,
and `unaccent`. If you don't see the extension you need, you
can [request it here](https://pris.ly/i-want-extensions). Extensions
only work on *new* instances, if you want to use any of them on your
existing instance, [reach out to us](mailto:support@prisma.io).
- **Management API for Prisma Postgres** – REST API to provision,
delete, and manage Prisma Postgres instances programmatically, perfect
for CI/CD and scripting workflows.
- **GitHub Actions for Prisma Postgres** – Actions for creating and
deleting databases in CI/CD workflows, available on GitHub Marketplace.
- **New CLI: `npx create-db`** – Instantly spin up a new Postgres
database—no authentication required.
###
[`v6.13.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.13.0)
[Compare
Source](https://redirect.github.com/prisma/prisma/compare/6.12.0...6.13.0)
Today, we are excited to share the `6.13.0` stable release 🎉
**🌟 Star this repo for notifications about new releases, bug fixes &
features — or [follow us on X](https://pris.ly/x)!**
##### Highlights
In this ORM release, we’re moving the Prisma Config file and the
multi-schema feature into [General
Availability](https://www.prisma.io/docs/orm/more/releases#generally-available-ga).
This means these features now are fully production-ready and we’re
looking forward to seeing what you are going to build with them!
Additionally, support for SQL views is getting an important update to
further stabilize its API.
##### Configuring Prisma via Prisma Config is now Generally Available
The
[`prisma.config.ts`](https://www.prisma.io/docs/orm/reference/prisma-config-reference)
file is Prisma ORM’s native way to provide configuration options for
your project. It currently lets you specify:
- the locations for various Prisma-related assets, such as your:
- Prisma schema file
- migrations
- SQL view definitions
- TypedSQL queries
- a `seed` command to populate your database based on some executable
script
- externally managed tables (see below)
- the driver adapters to be used by the Prisma CLI when interacting with
your database
Here’s an example Prisma Config file that specified custom locations for
various project assets in and a seed script inside a `db` directory:
```tsx
import path from "node:path";
import { defineConfig } from "prisma/config";
export default defineConfig({
schema: path.join("db", "schema.prisma"),
migrations: {
path: path.join("db", "migrations"),
seed: "tsx db/seed.ts"
}
});
```
Note that you’ll also see warning now if you defined a `prisma.seed`
command in `package.json`.
We’re excited to move the
[`prisma.config.ts`](https://www.prisma.io/docs/orm/reference/prisma-config-reference)
file into General Availability. If you used it before in your projects,
you can now drop `earlyAccess` from its options:
```diff
import { defineConfig } from "prisma/config";
export default defineConfig({
- earlyAccess: true,
});
```
There still are and will be fields on the Prisma Config object that are
Early Access or Preview features. To opt-into these, you’ll need to
explicitly declare them via a new `experimental` field.
For example, usage of `adapters` is currently still in Preview:
```tsx
import { defineConfig } from "prisma/config";
export default defineConfig({
experimental: {
adapter: true,
},
// requires `experimental.adapter`
adapter: async () => {
// ...
},
});
```
Finally, the Prisma Config file now also supports various file
extensions so it fits neatly into your individual project setups: `.js`,
`.ts`, `.mjs`, `.cjs`, `.mts`, `.cts`. It also can be defined as
`.config/prisma.${extension}`, where `extension` is the same one as file
extensions above.
📚 Learn more [in the
docs](https://www.prisma.io/docs/orm/reference/prisma-config-reference).
##### Using multiple schemas in now Generally Available
Databases like PostgreSQL or SQL Server provide a way to logically
organize your tables in dedicated namespaces called *schemas*. In Prisma
ORM, you can assign tables to various schemas via the `@@​schema`
attribute:
```tsx
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
schemas = ["base", "shop"]
}
model User {
id Int @​id
orders Order[]
@​@​schema("base")
}
model Order {
id Int @​id
user User @​relation(fields: [userId], references: [id])
userId Int
@​@​schema("shop")
}
```
This feature has moved into General Availability, so if you were using
it before, you can now drop the `multiSchema` feature flag from the
`generator` block in your Prisma schema:
```diff
generator client {
// ...
- previewFeatures = ["multiSchema"]
}
```
📚 Learn more [in the
docs](https://www.prisma.io/docs/orm/prisma-schema/data-model/multi-schema).
##### More robust support for SQL views (Preview)
SQL views are *virtual* tables created by a query. Unlike regular
tables, views do not store data themselves; instead, they represent the
result of a stored SQL query that runs whenever the view is accessed.
We continue to improve support for SQL views, making them more reliable
and better aligned with Prisma’s features. In this release, we ensured
that `@id`, `@index` and `@unique` can’t be used on a `view` block in
the Prisma schema. Without these attributes, several other features in
Prisma Client or the Prisma schema don’t make sense any more either, so
we made sure that they can’t be used with views:
- disabled `findUnique` queries and cursor-based pagination in Prisma
Client
- disallowed writes and implicit ordering for views in Prisma Client
- disallowed relationships involving views in Prisma Schema
This will align the API surface of Prisma ORM with the actual
capabilities of SQL views and adds guardrails so you can use views with
more confidence!
📚 Learn more [in the
docs](https://www.prisma.io/docs/orm/prisma-schema/data-model/views).
##### Externally managed tables
In some situations, you may not want Prisma ORM to be “responsible” for
specific tables in your database because they’re being managed by a
different team in your organization or an external service.
In these cases, you still may want to quert these tables using Prisma
Client but never want Prisma Migrate to make any changes to them.
In this release, we’re introducing externally managed tables that will
be:
- ignored by Prisma Migrate
- queryable via Prisma Client
You can specify which tables should be ignored by Prisma Migrate using
the `tables` option in `prisma.config.ts`:
```tsx
// prisma.config.ts
export default defineConfig({
tables: {
external: [
"users",
]
},
...
})
```
A typical use case for this is the [`users` table from
Supabase](https://supabase.com/docs/guides/auth/managing-user-data)
which you never want be changed by Prisma Migrate but still may want to
query with Prisma Client.
📚 Learn more [in the
docs](https://www.prisma.io/docs/orm/prisma-schema/data-model/externally-managed-tables).
##### Other news
##### [`pgvector`](https://redirect.github.com/pgvector/pgvector)
extension support for Prisma Postgres (Early Access)
In this release, we’ve implemented a highly popular feature request for
Prisma Postgres: [Early
Access](https://www.prisma.io/docs/platform/maturity-levels#early-access)
support for the
[`pgvector`](https://redirect.github.com/pgvector/pgvector) PostgreSQL
extension along with several other popular Postgres extensions!
It enables efficient storage and querying of high-dimensional vector
embeddings directly in a Postgres database and thus is perfect for
building AI-driven applications. `pgvector` essentially allows
developers to perform similarity search (e.g., for recommendation
systems or semantic search) using standard SQL, eliminating the need for
a separate vector database.
Native support for `pgvector` in Prisma ORM is going to follow soon,
until then you can use `pgvector` via [custom
migrations](https://www.prisma.io/docs/orm/prisma-migrate/workflows/customizing-migrations)
and
[TypedSQL](https://www.prisma.io/blog/announcing-typedsql-make-your-raw-sql-queries-type-safe-with-prisma-orm).
> **Note**: For now, `pgvector` is only available on *newly created*
Prisma Postgres instances. It will be rolled out for *existing*
instances soon.
In addition to `pgvector`, Prisma Postgres now includes Early Access
support for `pg_search`, `pg_stat_statements`, `citext`, `pg_trgm`,
`fuzzystrmatch`, and `unaccent`. If you don’t see the extension you
need, you can [request it here](https://pris.ly/i-want-extensions).
📚 Learn more [in the
docs](https://www.prisma.io/docs/postgres/database/postgres-extensions).
##### Manage Prisma Postgres programmatically via an API
Whether you need a way to quickly provision a Prisma Postgres instance
in your CI/CD workflows, want to attach a fresh database to a preview
branch of your app or even want to offer Prisma Postgres to your own
users—our new Management API has you covered!
It’s shaped as a familiar REST API so you can programmatically take care
of your database workflows: Provision or delete Prisma Postgres
instances, retrieve or create connection strings and manage entire
projects in [Prisma Console](https://console.prisma.io/).
📚 Learn more [in the
docs](https://www.prisma.io/docs/postgres/database/api-reference/management-api).
##### CI/CD GitHub Actions for Prisma Postgres available on GitHub
Marketplace
Based on the Management API, we’ve also published two templates for
GitHub Actions that you can use in your own CI/CD setups:
- [**Create Prisma Postgres Database
Action**](https://redirect.github.com/marketplace/actions/create-prisma-postgres-database)
- [**Delete Prisma Postgres Database
Action**](https://redirect.github.com/marketplace/actions/delete-prisma-postgres-database)
These Actions serve as the foundational building blocks for integrating
Prisma Postgres into CI/CD pipelines.
They enable workflows like provisioning databases on every pull request,
running integration tests against real instances, and managing database
lifecycles end-to-end. We’ve included several examples in the README to
help users get started quickly. The setup is straightforward, and these
Actions are designed to plug into user's workflows with minimal effort.
##### Instant Postgres with `npx create-db` — no auth required
We launched a new CLI command that allows you to spin up a new database
within seconds:
```bash
npx create-db # no auth required
```
The command doesn’t require authentication, so you can play around with
your database without any initial hurdles!
Your instance will be automatically deleted after 24 hours *but* you can
claim it and put it into your [Prisma
Console](https://console.prisma.io) account if you want to keep using it
after that period. Visit [the
docs](https://www.prisma.io/docs/postgres/introduction/npx-create-db) to
learn more.
##### New navigation UI for [Prisma Console](https://console.prisma.io/)
The [Prisma Console](https://console.prisma.io) got a little makeover,
including a new design for navigating and managing your projects and
their databases. This makes common workflows like *creating new
projects*, *navigating between projects and databases*, as well as
*accessing project settings* a lot more smooth.
We’re eager to hear your feedback, [let us know on X](https://pris.ly/x)
what you think of the new UI.
##### Enterprise support
Thousands of teams use Prisma and many of them already tap into our
Enterprise & Agency Support Program for hands-on help with everything
from schema integrations and performance tuning to security and
compliance. With this program you also get priority issue triage and bug
fixes, expert scalability advice, and custom training so that your
Prisma-powered apps stay rock-solid at any scale. Learn more or join:
<https://prisma.io/enterprise>.
###
[`v6.12.0`](https://redirect.github.com/prisma/prisma/releases/tag/6.12.0)
[Compare
Source](https://redirect.github.com/prisma/prisma/compare/6.11.1...6.12.0)
Today, we are excited to share the `6.12.0` stable release 🎉
**🌟 Star this repo for notifications about new releases, bug fixes &
features — or [follow us on X](https://pris.ly/x)!**
##### Highlights
##### ESM-compatible `prisma-client` generator now in Preview
We’re excited to share that our new and more flexible `prisma-client`
generator is moving into
[Preview](https://www.prisma.io/docs/orm/more/releases#preview)! As a
reminder, here’s what it looks like:
```prisma
generator client {
// Required
provider = "prisma-client" // no `-js` at the end!
output = "../src/generated/prisma"
// Optional
runtime = "nodejs"
moduleFormat = "esm"
generatedFileExtension = "ts"
importFileExtension = "ts"
}
```
This new generator eliminates any headaches that you may have
experienced due to [magical code generation into
`node_modules`](https://www.prisma.io/blog/why-prisma-orm-generates-code-into-node-modules-and-why-it-ll-change)
and gives you full control over the generated Prisma Client code. With
it moving into Preview, we hope that even more of you will try it out
and share your feedback with us!
> **Note**: The `prisma-client` generator will become the default in
Prisma v7, replacing the current `prisma-client-js` generator.
In addition to moving it into Preview, we also created a couple of new
ready-to-run examples to help you get started with the new generator and
your favorite framework:
- [React Router + Vite +
Cloudflare](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/react-router-starter-cloudflare-workerd)
- [React Router + Vite +
Node.js](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/react-router-starter-nodejs)
- [Nuxt 3 + Vite +
Nitro](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/nuxt3-starter-nodejs)
- [Deno
Deploy](https://redirect.github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/deno-deploy)
📚 Learn more in the
[docs](https://www.prisma.io/docs/orm/prisma-schema/overview/generators#prisma-client-preview).
##### Specify `views` and `migrations` folder locations in
`prisma.config.ts` (Early Access)
As we’re getting closer to the [General
Availability](https://www.prisma.io/docs/orm/more/releases#generally-available-ga)
release of
[`prisma.config.ts`](https://www.prisma.io/docs/orm/reference/prisma-config-reference),
we’re adding more capabilities to it. In previous versions, the Prisma
CLI implicitly used to infer the location for migration and SQL view
definition files based on the location of the Prisma schema. In this
release, we’re adding two new fields (`migrations` and `views`) to give
you more flexibility and clarity on how to locate these files:
```ts
// prisma.config.ts
export default defineConfig({
earlyAccess: true,
migrations: {
path: './db/migrations'
},
views: {
path: './db/views'
}
// ...
})
```
📚 Learn more in the
[docs](https://www.prisma.io/docs/orm/reference/prisma-config-reference).
<!--
##### Other news
##### Manage Prisma Postgres programmatically via an API
Whether you need a way to quickly provision a Prisma Postgres instance
in your CI/CD workflows, want to attach a fresh database to a preview
branch of your app or even want to offer Prisma Postgres to your own
users—our new Management API has you covered!
It’s shaped as a familiar REST API so you can programmatically take care
of your database workflows: Provision or delete Prisma Postgres
instances, retrieve or create connection strings and manage entire
projects in [Prisma Console](https://console.prisma.io).
📚 Learn more in the
[docs](https://www.prisma.io/docs/postgres/database/api-reference/management-api).
##### New navigation UI for Prisma Console
The [Prisma Console](https://console.prisma.io) got a little makeover,
including a new design for navigating and managing your projects and
their databases. This makes common workflows like _creating new
projects_, _navigating between projects and databases_, as well as
_accessing project settings_ a lot more smooth:
We’re eager to hear your feedback, [let us know on X](https://pris.ly/x)
what you think of the new UI!
-->
##### Enterprise support
Thousands of teams use Prisma and many of them already tap into our
Enterprise & Agency Support Program for hands-on help with everything
from schema integrations and performance tuning to security and
compliance. With this program you also get priority issue triage and bug
fixes, expert scalability advice, and custom training so that your
Prisma-powered apps stay rock-solid at any scale. Learn more or join:
<https://prisma.io/enterprise>
###
[`v6.11.1`](https://redirect.github.com/prisma/prisma/releases/tag/6.11.1)
[Compare
Source](https://redirect.github.com/prisma/prisma/compare/6.11.0...6.11.1)
Today, we are issuing a 6.11.1 patch release.
#### Bug fixes
- In Prisma ORM version 6.11.0, we shipped a bug fix for Prisma that
allows using Prisma Postgres with direct TCP connections with Prisma
Driver Adapters. This fix required refactoring the Prisma Client
initialization logic, and while several test cases were added, an edge
case was missing, causing
[#​27569](https://redirect.github.com/prisma/prisma/issues/27569).
Namely, using `@prisma/client` with `@prisma/extension-accelerate` on a
`prisma+postgres://...` connection string, while generating the Prisma
Client definitions via `prisma generate`, resulted in a
`PrismaClientInitializationError`.
This is now fixed, so we highly recommend upgrading to version 6.11.1.
Reminder: when using Prisma Accelerate, we highly encourage you to
generate your Prisma Client de
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "before 12pm on Sunday" (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.
👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config
help](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/wolfstar-project/wolfstar).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC43LjEiLCJ1cGRhdGVkSW5WZXIiOiI0MS4xMzAuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->7 files changed
Lines changed: 1558 additions & 1673 deletions
File tree
- .github/workflows
- .yarn/releases
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
32 | 32 | | |
33 | 33 | | |
34 | 34 | | |
35 | | - | |
| 35 | + | |
36 | 36 | | |
37 | 37 | | |
38 | 38 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
33 | | - | |
| 33 | + | |
34 | 34 | | |
35 | 35 | | |
36 | 36 | | |
| |||
Large diffs are not rendered by default.
This file was deleted.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
13 | | - | |
| 13 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
51 | 51 | | |
52 | 52 | | |
53 | 53 | | |
54 | | - | |
| 54 | + | |
55 | 55 | | |
56 | 56 | | |
57 | 57 | | |
58 | 58 | | |
59 | | - | |
| 59 | + | |
60 | 60 | | |
61 | 61 | | |
62 | | - | |
63 | | - | |
| 62 | + | |
| 63 | + | |
64 | 64 | | |
65 | | - | |
| 65 | + | |
66 | 66 | | |
67 | | - | |
| 67 | + | |
68 | 68 | | |
69 | 69 | | |
70 | | - | |
| 70 | + | |
71 | 71 | | |
72 | 72 | | |
73 | 73 | | |
| |||
84 | 84 | | |
85 | 85 | | |
86 | 86 | | |
87 | | - | |
| 87 | + | |
88 | 88 | | |
89 | | - | |
| 89 | + | |
90 | 90 | | |
91 | 91 | | |
92 | 92 | | |
93 | | - | |
94 | | - | |
95 | | - | |
| 93 | + | |
| 94 | + | |
| 95 | + | |
96 | 96 | | |
97 | 97 | | |
98 | 98 | | |
99 | 99 | | |
100 | 100 | | |
101 | 101 | | |
102 | | - | |
| 102 | + | |
103 | 103 | | |
104 | 104 | | |
105 | 105 | | |
106 | 106 | | |
107 | 107 | | |
108 | 108 | | |
109 | 109 | | |
110 | | - | |
111 | | - | |
112 | | - | |
113 | | - | |
114 | | - | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
115 | 115 | | |
116 | 116 | | |
117 | 117 | | |
| |||
143 | 143 | | |
144 | 144 | | |
145 | 145 | | |
146 | | - | |
| 146 | + | |
147 | 147 | | |
148 | | - | |
| 148 | + | |
149 | 149 | | |
150 | 150 | | |
0 commit comments