Skip to content
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

fix(deps): update prisma monorepo to v6.3.0 #770

Merged
merged 1 commit into from
Jan 31, 2025
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 28, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) 6.2.1 -> 6.3.0 age adoption passing confidence
prisma (source) 6.2.1 -> 6.3.0 age adoption passing confidence

Release Notes

prisma/prisma (@​prisma/client)

v6.3.0

Compare Source

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

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

Highlights
Add limit to updateMany() and deleteMany()

Previously, limit has not existed as a valid option in top level updateMany() and deleteMany() queries. In 6.3.0 limit is now available in these queries, bringing their features more in line with other query types.

You can use limit like the following:

await prisma.user.deleteMany({
  where: { column: 'value' },
  limit: 100,
});

This will limit the number of deleted users to 100 at maximum.

Sort generator fields deterministically

In previous version of Prisma ORM, the fields inside of a generator block in your Prisma Schema were not deterministically sorted. This could lead to cases where prisma db pull could lead to re-ordering of fields.

In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first prisma db pull after you upgrade, but it will remain consistent afterwards.

Replace NOT IN with NOT EXISTS for PostgreSQL relation filters

In previous versions of Prisma ORM, when using the none or some relation filters, the SQL queries generated used NOT IN. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of IN with EXISTS in order to improve query performance.

A special thank you

We'd like to extend our heartfelt thanks to @​loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #​19249 and #​17303. Their insights and partnership have been invaluable in improving our product.

If your team could benefit from dedicated support and tailored solutions, learn more about our enterprise support plan.

Fixes and improvements
Prisma Client
Prisma
Credits

Huge thanks to @​WhyAsh5114 for their contributions to this release!


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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Jan 28, 2025
@renovate renovate bot requested a review from a team as a code owner January 28, 2025 18:15
Copy link

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@prisma/[email protected] 🔁 npm/@prisma/[email protected] None 0 13.7 MB aqrln, pirix-gh, prismabot
npm/[email protected] 🔁 npm/[email protected] None +5 13.7 MB prismabot

View full report↗︎

@renovate renovate bot merged commit 4d9f343 into main Jan 31, 2025
2 checks passed
@renovate renovate bot deleted the renovate/prisma-monorepo branch January 31, 2025 01:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants