chore(deps): update prisma monorepo to v6.19.2#21
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
8b0a620 to
b9c701e
Compare
b9c701e to
ed4ef44
Compare
ed4ef44 to
0eea023
Compare
0eea023 to
0dc84b1
Compare
0dc84b1 to
a8add89
Compare
a8add89 to
f6d7925
Compare
f6d7925 to
f2bafdf
Compare
f2bafdf to
3d04cd3
Compare
3d04cd3 to
666778b
Compare
666778b to
e78ec77
Compare
e78ec77 to
22f2db6
Compare
22f2db6 to
5ec400c
Compare
5ec400c to
e12bf56
Compare
e12bf56 to
23a43eb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.17.1→6.19.26.17.1→6.19.2Release Notes
prisma/prisma (@prisma/client)
v6.19.2Compare Source
Today, we are issuing a 6.19.2 patch release in the Prisma 6 release line. It fixes an issue with Prisma Accelerate support in some edge runtime configurations when the
@prisma/client/edgeentrypoint is not being used.Changes:
v6.19.1Compare Source
v6.19.0Compare Source
v6.18.0Compare Source
Today, we are excited to share the
6.18.0stable release 🎉🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!
Prisma ORM
Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:
prisma initnow creates aprisma.config.tsautomaticallyWhen creating a new project with 6.18.0,
prisma initwill now create aprisma.config.tsfile automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in theschema.prismafile are now able to be set in theprisma.config.ts, and we encourage people to migrate over to the new structure before the release of version 7, where this file will become a requirement.datasourceinprisma.config.tsIf you’re adopting the new
prisma.config.tssetup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in yourschema.prismawill be ignored. To set the datasource, we also must include the newenginekey which we can set to"classic", which will be required for Prisma v7envhelper functionjsorclassicas engine types inprisma.configBytestoUint8Arraydepending on Typescript versionPreparing for Prisma v7
While it has been mentioned a few times already, many of the changes in this release are here to prepare folks for the upcoming release of Prisma v7. It’s worth repeating that these changes and the migration to
prisma.config.tswill be required for Prisma v7, so we’re releasing this as opt-in features for developers. But come Prisma v7, they will be the new way of configuring your project.Prisma Postgres
Prisma Postgres is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements:
Database Metric in Console
Inside of your database console, you can now view metrics on your database usage and interactions. You can get insights into the follow:
In addition, you can also get insights into how to improve your query caching and gain better performance.
Open roles at Prisma
Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.
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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.