fix(deps): update prisma monorepo to v6.9.0 #86

Merged

dominik merged 1 commit from renovate/prisma-monorepo into main 2025-06-07 13:31:59 +00:00

Conversation 1 Commits 1 Files changed 2 +338 -293

Renovate commented 2025-06-06 10:01:11 +00:00

Owner

Copy link

This PR contains the following updates:

Package	Type	Update	Change
@prisma/client (source)	dependencies	minor	6.8.2 -> 6.9.0
prisma (source)	devDependencies	minor	6.8.2 -> 6.9.0

---

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

prisma/prisma (@​prisma/client)

v6.9.0

Compare Source

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

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

Highlights

Prisma ORM without Rust engines for PostgreSQL & SQLite (Preview)

If you've been excited about our work of removing the Rust engines from Prisma ORM but hesitated trying it out because it was in an Early Access (EA) phase, now is a great time for you to get your hands on the Rust-free Prisma ORM version.

This major architectural change has moved from EA into Preview in this release, meaning there are no more know major issues. If you want to try it out, add the queryCompiler and driverAdapters preview feature flags to your generator, install the driver adapter for your database, and get going:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["queryCompiler", "driverAdapters"]
  output          = "../generated/prisma"
}

Now run prisma generate to re-generate Prisma Client. If you didn't use a driver adapter before, you'll need to install, e.g. the one for PostgreSQL:

npm install @​prisma/adapter-pg

Once installed, you can instantiate PrismaClient as follows:

import { PrismaClient } from './generated/prisma'
import { PrismaPg } from '@​prisma/adapter-pg'

const adapter = new PrismaPg({ connectionString: env.DATABASE_URL })
const prisma = new PrismaClient({ adapter })

No more hassle with query engines, binary targets and an even smoother experience in serverless and edge environments!

📚 Learn more in the docs.

Major improvements for local Prisma Postgres (Preview)

In the last release, we enabled you to spin up a Prisma Postgres instance locally via the new prisma dev command. Local Prisma Postgres uses PGlite under the hood and gives you an identical experience as you get with a remote Prisma Postgres instance.

This release brings major improvements to this feature:

• Persists your databases across prisma dev invocations.
• Enables you to have multiple local Prisma Postgres instances running at the same time.
• Running prisma init now uses local Prisma Postgres by default.

Try it out and let us know what you think!

📚 Learn more in the docs.

More news

Connect to Prisma Postgres with any ORM (Preview)

Since its GA release, you could only interact with Prisma Postgres using Prisma ORM via a custom connection string.

This has changed now: When setting up a new Prisma Postgres instance, you receive a regular PostgreSQL direct TCP connection string (starting with postgres://...) that lets you connect to it using your favorite tool or database library, including Drizzle, Kysely, TypeORM, and others.

If you want to access Prisma Postgres from a serverless environment, you can also use our new serverless driver (Early Access).

📚 Learn more in the docs.

Automated backup & restore

Prisma Postgres' backup and restore mechanism has seen a major upgrade recently: You can now easily restore any previous backup via the UI in the Prisma Console. Find the new Backups tab when viewing your database and select any backup from the list to restore its state to a previous point in time.

📚 Learn more in the docs.

Prisma's VS Code extension now has a UI to manage Prisma Postgres

If you're using Prisma ORM, chances are that you're using our VS Code extension too. In its latest release, we've added a major new capability to it: A UI for managing databases.

With this new UI, you can:

• Authenticate with the Prisma Console
• Create and delete remote Prisma Postgres instances
• View local Prisma Postgres instances
• View and edit data via an embedded Prisma Studio
• Visualize your database schema

To use the new features, make sure to have the latest version of the Prisma VS Code extension installed and look out for the new Prisma logo in VS Code's Activity Bar.

📚 Learn more in the docs.

New region for Prisma Postgres: San Francisco (us-west-1)

We keep expanding Prisma Postgres availability across the globe! After having added Singapore just a few weeks ago, we're now adding San Francisco based on another poll we ran on X. Here are all the regions where you can spin up Prisma Postgres instances today:

• us-west-1: San Francisco (new!)
• us-east-1: North Virginia
• eu-west-3: Paris
• ap-northeast-1: Tokyo
• ap-southeast-1: Singapore

Keep an eye on our X account to take part in the poll and vote for the next availability zone of Prisma Postgres!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@prisma/client](https://www.prisma.io) ([source](https://github.com/prisma/prisma/tree/HEAD/packages/client)) | dependencies | minor | [`6.8.2` -> `6.9.0`](https://renovatebot.com/diffs/npm/@prisma%2fclient/6.8.2/6.9.0) | | [prisma](https://www.prisma.io) ([source](https://github.com/prisma/prisma/tree/HEAD/packages/cli)) | devDependencies | minor | [`6.8.2` -> `6.9.0`](https://renovatebot.com/diffs/npm/prisma/6.8.2/6.9.0) | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>prisma/prisma (@&#8203;prisma/client)</summary> ### [`v6.9.0`](https://github.com/prisma/prisma/releases/tag/6.9.0) [Compare Source](https://github.com/prisma/prisma/compare/6.8.2...6.9.0) Today, we are excited to share the `6.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%20out%20the%20latest%20@&#8203;prisma%20release%20v6.9.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.9.0) about the release.** ##### Highlights ##### Prisma ORM without Rust engines for PostgreSQL & SQLite (Preview) If you've been excited about our work of removing the Rust engines from Prisma ORM but hesitated trying it out because it was in an [Early Access](https://www.prisma.io/docs/orm/more/releases#early-access) (EA) phase, now is a great time for you to get your hands on the [Rust-free Prisma ORM version](https://www.prisma.io/blog/try-the-new-rust-free-version-of-prisma-orm-early-access). This major architectural change has moved from EA into [Preview](https://www.prisma.io/docs/orm/more/releases#preview) in this release, meaning there are no more know major issues. If you want to try it out, add the `queryCompiler` and `driverAdapters` preview feature flags to your `generator`, install the driver adapter for your database, and get going: ```prisma generator client { provider = "prisma-client-js" previewFeatures = ["queryCompiler", "driverAdapters"] output = "../generated/prisma" } ``` Now run `prisma generate` to re-generate Prisma Client. If you didn't use a [driver adapter](https://www.prisma.io/docs/orm/overview/databases/database-drivers#driver-adapters) before, you'll need to install, e.g. the one for PostgreSQL: npm install @&#8203;prisma/adapter-pg Once installed, you can instantiate `PrismaClient` as follows: ```ts import { PrismaClient } from './generated/prisma' import { PrismaPg } from '@&#8203;prisma/adapter-pg' const adapter = new PrismaPg({ connectionString: env.DATABASE_URL }) const prisma = new PrismaClient({ adapter }) ``` No more hassle with query engines, binary targets and an even smoother experience in serverless and edge environments! 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engine). ##### Major improvements for local Prisma Postgres (Preview) In the last release, we enabled you to spin up a Prisma Postgres instance locally via the new `prisma dev` command. [Local Prisma Postgres](https://www.prisma.io/blog/prisma-6-8-0-release#local-development-for-prisma-postgres-early-access) uses PGlite under the hood and gives you an identical experience as you get with a remote Prisma Postgres instance. This release brings major improvements to this feature: - Persists your databases across `prisma dev` invocations. - Enables you to have multiple local Prisma Postgres instances running at the same time. - Running `prisma init` now uses local Prisma Postgres by default. Try it out and let us know what you think! 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/database/local-development). ##### More news ##### Connect to Prisma Postgres with any ORM (Preview) Since its [GA release](https://www.prisma.io/blog/prisma-postgres-the-future-of-serverless-databases), you could only interact with Prisma Postgres using Prisma ORM via a [custom connection string](https://www.prisma.io/docs/orm/reference/connection-urls#prisma-postgres). This has changed now: When setting up a new Prisma Postgres instance, you receive a regular PostgreSQL direct TCP connection string (starting with `postgres://...`) that lets you connect to it using your favorite tool or database library, including Drizzle, Kysely, TypeORM, and others. If you want to access Prisma Postgres from a serverless environment, you can also use our new [serverless driver](https://www.prisma.io/docs/postgres/database/serverless-driver) (Early Access). 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/database/direct-connections). ##### Automated backup & restore Prisma Postgres' backup and restore mechanism has seen a major upgrade recently: You can now easily restore any previous backup via the UI in the Prisma Console. Find the new **Backups** tab when viewing your database and select any backup from the list to restore its state to a previous point in time. 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/database/backups). ##### Prisma's VS Code extension now has a UI to manage Prisma Postgres If you're using Prisma ORM, chances are that you're using our [VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) too. In its latest release, we've added a major new capability to it: A UI for managing databases. With this new UI, you can: - Authenticate with the [Prisma Console](https://console.prisma.io) - Create and delete remote Prisma Postgres instances - View local Prisma Postgres instances - View and edit data via an embedded Prisma Studio - Visualize your database schema  To use the new features, make sure to have the latest version of the Prisma VS Code extension installed and look out for the new **Prisma logo** in VS Code's *Activity Bar*. 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/integrations/vscode-extension#database-management-ui). ##### New region for Prisma Postgres: San Francisco (`us-west-1`) We keep expanding Prisma Postgres availability across the globe! After having added Singapore just a few weeks ago, we're now adding San Francisco based on another [poll we ran on X](https://x.com/prisma/status/1924494260910612841). Here are all the regions where you can spin up Prisma Postgres instances today: - **`us-west-1`: San Francisco (*new!*)** - `us-east-1`: North Virginia - `eu-west-3`: Paris - `ap-northeast-1`: Tokyo - `ap-southeast-1`: Singapore [Keep an eye on our X account](https://pris.ly/x) to take part in the poll and vote for the next availability zone of Prisma Postgres! </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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 has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC40MS4zIiwidXBkYXRlZEluVmVyIjoiNDAuNDEuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

Renovate added 1 commit 2025-06-06 10:01:12 +00:00

fix(deps): update prisma monorepo to v6.9.0 2202c32404

Renovate force-pushed renovate/prisma-monorepo from 2202c32404 to cc6c75cd66 2025-06-06 11:01:02 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from cc6c75cd66 to 06ae8de64d 2025-06-06 12:01:05 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 06ae8de64d to ebe8deff2b 2025-06-06 13:00:59 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from ebe8deff2b to 9078a7bc84 2025-06-06 14:01:02 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 9078a7bc84 to 481d5a4703 2025-06-06 15:01:06 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 481d5a4703 to 754163f2e3 2025-06-06 16:01:03 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 754163f2e3 to eb20881774 2025-06-06 17:01:03 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from eb20881774 to c85ca06ebe 2025-06-06 18:01:03 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from c85ca06ebe to c4530b9658 2025-06-06 19:01:02 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from c4530b9658 to 532609d925 2025-06-06 20:01:02 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 532609d925 to 84e4b537d9 2025-06-06 21:01:06 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 84e4b537d9 to e94dc81ec1 2025-06-06 22:01:03 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from e94dc81ec1 to 493913fddb 2025-06-06 23:01:00 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 493913fddb to 136cea50f9 2025-06-07 00:01:04 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 136cea50f9 to 709308998d 2025-06-07 01:00:58 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 709308998d to 1de341ef7d 2025-06-07 02:01:03 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 1de341ef7d to 080cc80bef 2025-06-07 03:00:55 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 080cc80bef to 01ce2bec43 2025-06-07 04:01:07 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 01ce2bec43 to 2d256dcf9a 2025-06-07 05:01:02 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 2d256dcf9a to 8ca3382cd6 2025-06-07 06:01:03 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 8ca3382cd6 to d16432f6c7 2025-06-07 07:01:01 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from d16432f6c7 to 8467cf3ab5 2025-06-07 08:01:02 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 8467cf3ab5 to 794676bf50 2025-06-07 09:01:02 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 794676bf50 to 8fde701897 2025-06-07 10:01:04 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 8fde701897 to 4cd6da168f 2025-06-07 11:01:06 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 4cd6da168f to 957538d1d1 2025-06-07 12:01:03 +00:00 Compare

Renovate force-pushed renovate/prisma-monorepo from 957538d1d1 to 75cc684c11 2025-06-07 13:01:04 +00:00 Compare

dominik force-pushed renovate/prisma-monorepo from 75cc684c11 to 5ce147a7f0 2025-06-07 13:05:21 +00:00 Compare

dominik force-pushed renovate/prisma-monorepo from 5ce147a7f0 to c732b3138e 2025-06-07 13:07:24 +00:00 Compare

dominik approved these changes 2025-06-07 13:08:35 +00:00

dominik scheduled this pull request to auto merge when all checks succeed 2025-06-07 13:08:47 +00:00

dominik merged commit cdc0e81e51 into main 2025-06-07 13:31:59 +00:00

dominik deleted branch renovate/prisma-monorepo 2025-06-07 13:32:00 +00:00

dominik referenced this pull request from a commit 2025-06-07 13:32:00 +00:00

Merge pull request 'fix(deps): update prisma monorepo to v6.9.0' (#86)

Sign in to join this conversation.

Reviewers

No reviewers

dominik

Labels

Clear labels   

Compat/Breaking

Breaking change that won't be backward compatible

  

Kind/Bug

Something is not working

  

Kind/Documentation

Documentation changes

  

Kind/Enhancement

Improve existing functionality

  

Kind/Feature

New functionality

  

Kind/Security

This is security issue

  

Kind/Testing

Issue or pull request related to testing

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Reviewed

Confirmed

Issue has been confirmed

  

Reviewed

Duplicate

This issue or pull request already exists

  

Reviewed

Invalid

Invalid issue

  

Reviewed

Won't Fix

This issue won't be fixed

  

Review needed

  

Status

Abandoned

Somebody has started to work on this but abandoned work

  

Status

Blocked

Something is blocking this issue or pull request

  

Status

Need More Info

Feedback is required to reproduce issue or to continue work

No labels

Compat/Breaking

Kind/Bug

Kind/Documentation

Kind/Enhancement

Kind/Feature

Kind/Security

Kind/Testing

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Reviewed

Confirmed

Reviewed

Duplicate

Reviewed

Invalid

Reviewed

Won't Fix

Review needed

Status

Abandoned

Status

Blocked

Status

Need More Info

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DHBW-WE/MeetUp#86

No description provided.