-
Notifications
You must be signed in to change notification settings - Fork 154
fix(deps): update prisma monorepo to v6.8.2 #1821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
2e6e641
to
9842bf6
Compare
9842bf6
to
d6fd977
Compare
d6fd977
to
d6c1a57
Compare
This PR contains the following updates:
6.7.0
->6.8.2
6.7.0
->6.8.2
6.7.0
->6.8.2
6.7.0
->6.8.2
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
andprisma 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
andprisma 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 yourdatasource
block to point to a local Prisma Postgres instance. It looks similar to this: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 theprisma-client-js
generator. If you want to use Prisma ORM with Deno, you can now do so with the newprisma-client
generator:📚 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:
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.
This PR was generated by Mend Renovate. View the repository job log.