Skip to content

fix(deps): update prisma monorepo to v6.5.0#7689

Merged
renovate[bot] merged 1 commit intolatestfrom
renovate/prisma-monorepo
Mar 14, 2025
Merged

fix(deps): update prisma monorepo to v6.5.0#7689
renovate[bot] merged 1 commit intolatestfrom
renovate/prisma-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 13, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/adapter-d1 (source) 6.4.1 -> 6.5.0 age adoption passing confidence
@prisma/adapter-libsql (source) 6.4.1 -> 6.5.0 age adoption passing confidence
@prisma/client (source) 6.4.1 -> 6.5.0 age adoption passing confidence
prisma (source) 6.4.1 -> 6.5.0 age adoption passing confidence

Release Notes

prisma/prisma (@​prisma/adapter-d1)

v6.5.0

Compare Source

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

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

Highlights
Databases can only be reset manually and explicitly

In previous versions, if Prisma ORM determined that a migrate command could not be applied cleanly to the underlying database, you would get a message like this one:

? We need to reset the "public" schema at "db.url.com:5432"
Do you want to continue? All data will be lost. (y/N)

While "no" was the default, we've determined that having this prompt in the first place was a mistake. In this version we're removing the prompt entirely and instead exiting with an appropriate error message.

To get the previous behavior, you will need to run prisma migrate reset directly.

Support for prisma.config.ts in Prisma Studio

We've expanded support for our prisma.config.ts file to include Prisma Studio!

To use the new config file, including the ability to connect to driver adapter enabled databases with Prisma Studio, add a studio block to your prisma.config.ts file:

import path from 'node:path'
import type { PrismaConfig } from 'prisma'
import { PrismaLibSQL } from '@​prisma/adapter-libsql'
import { createClient } from '@​libsql/client'

export default {
  earlyAccess: true,
  schema: {
    kind: 'single',
    filePath: './prisma/schema.prisma',
  },
  studio: {
    adapter: async (env: unknown) => {
      const connectionString = `file:./dev.db'
      const libsql = createClient({
        url: connectionString,
      })
      return new PrismaLibSQL(libsql)
    },
  },
} satisfies PrismaConfig

Notice how this looks a little different from last release! Instead of an @prisma/config package there’s now two different options:

  1. Using the defineConfig helper exported by prisma/config.
  2. Using the PrismaConfig utility type exported by Prisma.

All the relevant info for the prisma.config.ts file, including these new ways of defining your config, can be found in our docs.

Allow for chaining $on and $extends.

In previous versions of Prisma ORM, the return type of the $on client method was void. This did not allow for chaining $on() and $extends() calls, as $on is not available on extended clients.

In this version we've resolved this issue and $on will now return the modified Prisma Client.

Community fixes

We have a number of community-submitted fixes that improve Prisma ORM:

Prisma is hiring

Join us at Prisma and work on our TypeScript ORM (now faster than ever) and our Cloud products like Prisma Postgres (now in GA!)

We currently have two open roles in our Engineering team:

If these don’t fit, you can still check out our jobs page and send a general application.

Enterprise support

Prisma offers an enterprise support plan for Prisma ORM. Get direct help from our team and a joint slack channel! With Prisma ORM 7 on the horizon this is a great time to upgrade your support today.

Credits

Thank you to @​overbit, @​RaHehl, @​toniopelo, and @​de-novo for your contributions to this release!


Configuration

📅 Schedule: Branch creation - "before 8am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/prisma-monorepo branch from 218c728 to 925eddf Compare March 14, 2025 15:45
@renovate renovate Bot force-pushed the renovate/prisma-monorepo branch from 925eddf to a05f99d Compare March 14, 2025 19:12
@renovate renovate Bot merged commit f47907e into latest Mar 14, 2025
39 checks passed
@renovate renovate Bot deleted the renovate/prisma-monorepo branch March 14, 2025 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants