Commit f797d3f
authored
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4&size=40){kind=avatar}
chore(deps): update prisma to v6.15.0 (#2766)
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| [@prisma/client](https://www.prisma.io)
([source](https://redirect.github.com/prisma/prisma/tree/HEAD/packages/client))
| [`6.13.0` ->
`6.15.0`](https://renovatebot.com/diffs/npm/@prisma%2fclient/6.13.0/6.15.0)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [prisma](https://www.prisma.io)
([source](https://redirect.github.com/prisma/prisma/tree/HEAD/packages/cli))
| [`6.13.0` ->
`6.15.0`](https://renovatebot.com/diffs/npm/prisma/6.13.0/6.15.0) |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
### Release Notes
<details>
<summary>prisma/prisma (@​prisma/client)</summary>
###
[`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:[email protected]).
- **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.
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "on the 2nd through 5th day of the
month" (UTC), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about these
updates again.
---
- [ ] <!-- 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/JabRef/JabRefOnline).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS45MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuOTEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>1 parent 00a9552 commit f797d3f
2 files changed
+48
-111
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
52 | 52 | | |
53 | 53 | | |
54 | 54 | | |
55 | | - | |
| 55 | + | |
56 | 56 | | |
57 | 57 | | |
58 | 58 | | |
| |||
137 | 137 | | |
138 | 138 | | |
139 | 139 | | |
140 | | - | |
| 140 | + | |
141 | 141 | | |
142 | 142 | | |
143 | 143 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments