liam icon indicating copy to clipboard operation
liam copied to clipboard

fix(deps): update prisma monorepo to v6.8.2

Open renovate[bot] opened this issue 6 months ago • 2 comments

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) 6.7.0 -> 6.8.2 age adoption passing confidence
@prisma/generator-helper (source) 6.7.0 -> 6.8.2 age adoption passing confidence
@prisma/internals (source) 6.7.0 -> 6.8.2 age adoption passing confidence
@prisma/nextjs-monorepo-workaround-plugin (source) 6.7.0 -> 6.8.2 age adoption passing confidence

Release Notes

prisma/prisma (@​prisma/client)

v6.8.2

Compare Source

Today, we are issuing the 6.8.2 patch release. It fully resolves an issue with the prisma init and prisma dev commands for some Windows users who were still facing problems after the previous incomplete fix in version 6.8.1.

Fixes:

v6.8.1

Compare Source

Today, we are issuing the 6.8.1 patch release. It fixes an issue with the prisma init and prisma dev commands on Windows.

Fixes

v6.8.0

Compare Source

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

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

Highlights

Local development with Prisma Postgres via prisma dev (Early Access)

In this release, we're releasing a way to develop against Prisma Postgres locally — no Docker required!

To get started, run the new prisma dev command:

npx prisma dev # starts a local Prisma Postgres server

This command spins up a local Prisma Postgres instance and prints the connection URL that you'll need to set as the url of your datasource block to point to a local Prisma Postgres instance. It looks similar to this:

datasource db {
  provider = "postgresql"
  url      = "prisma+postgres://localhost:51213/?api_key=ey..." 
}

You can then run migrations and execute queries against this local Prisma Postgres instance as with any remote one. Note that you need to keep the prisma dev process running in order to interact with the local Prisma Postgres instance.

📚 Learn more in the docs.

Native Deno support in prisma-client generator (Preview)

In this release, we're removing the deno Preview feature from the prisma-client-js generator. If you want to use Prisma ORM with Deno, you can now do so with the new prisma-client generator:

generator client {
  provider = "prisma-client"
  output   = "../src/generated/prisma"
  runtime = "deno"
}

📚 Learn more in the docs.

VS Code Agent Mode: AI support with your database workflows

Have you tried agent mode in VS Code already?

"The agent acts as an autonomous pair programmer that performs multi-step coding tasks at your command, such as analyzing your codebase, proposing file edits, and running terminal commands."

As of this release, your agent is capable of supporting you with your database workflows more than ever! If you're using VS Code and have the Prisma VS Code extension installed, your agent now is able to help you with your database workflows, such as:

  • checking the status of your migrations (e.g. telling you if migrations haven't been applied)
  • creating and running schema migrations for you
  • authenticating you with the Prisma Console
  • provisioning new Prisma Postgres instances so you can start coding right away

All you need to do is make sure you're using the latest version of Prisma's VS Code extension and your agent is ready to go 🚀

📚 Learn more in the docs.

Other news

You voted, we acted: New Singapore region for Prisma Postgres

We recently ran a poll where we asked you which region you'd like to see next for Prisma Postgres. The majority vote went to Asia Pacific (Singapore), so as of today, you're able to spin up new Prisma Postgres instances in the ap-southeast-1 region.

We're not stopping here — keep an eye out on X for another poll asking for your favorite regions that we should add!


Configuration

📅 Schedule: Branch creation - Only on Sunday and Saturday ( * * * * 0,6 ) (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.

🔕 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[bot] avatar May 29 '25 22:05 renovate[bot]

⚠️ No Changeset found

Latest commit: 09e42191fff3ef0432658b3154e95f4158acbbb9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

changeset-bot[bot] avatar May 29 '25 22:05 changeset-bot[bot]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
liam-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 2, 2025 2:02am
liam-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 2, 2025 2:02am
liam-erd-sample ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 2, 2025 2:02am
liam-storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 2, 2025 2:02am

vercel[bot] avatar May 29 '25 22:05 vercel[bot]

Prisma might not be in use anymore. 👀

junkisai avatar Jun 02 '25 01:06 junkisai

It looks like @prisma/internals and @prisma/generator-helper are being used in the db-structure.

junkisai avatar Jun 02 '25 01:06 junkisai

frontend/packages/prompt-test result:

visit: https://cloud.langfuse.com/project/cm8ii4o5o03fpad078o638g1d/datasets/cm99wciaz070ead07rgjr88ou/runs/cmbefupo000h1ad075jattf4s

run items length
3

github-actions[bot] avatar Jun 02 '25 01:06 github-actions[bot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

renovate[bot] avatar Jun 02 '25 01:06 renovate[bot]