Skip to content
This repository has been archived by the owner on Apr 13, 2024. It is now read-only.

build(deps): bump @prisma/client from 5.6.0 to 5.8.1 #53

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jan 16, 2024

Bumps @prisma/client from 5.6.0 to 5.8.1.

Release notes

Sourced from @​prisma/client's releases.

5.8.1

Today, we are issuing the 5.8.1 patch release.

Fix in Prisma Client

5.8.0

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

Highlights

Happy New Year from your friends at Prisma! 🎊

In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉

relationJoins improvements: Relation loading strategy per query (Preview)

In version 5.7.0, we released relationJoins into Preview. The relationJoins feature enables support for JOINs for relation queries.

This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case.

You can now load relation data using either of the following strategies:

  • join — uses JOINs to fetch relation data
  • query — uses separate queries to fetch relation data

When the relationJoins Preview feature is enabled, by default, the relation fetching strategy used is join. You can override the default behavior by using the relationLoadStrategy query option.

To get started, enable the Preview feature:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins"]
}

… and specify the relation loading strategy for your query as follows:

await prisma.user.findMany({
  relationLoadStrategy: 'query',
  include: {
    posts: true,
  },
})

... (truncated)

Commits
  • b70db9b chore(deps): patch 5.8.x 5.8.1-1.78caf6feeaed953168c64e15a249c3e9a033ebe2 (#2...
  • 688a50a feat(client): integrate relationLoadStrategy support (#22483)
  • 468fd2a chore(deps): update engines to 5.8.0-35.98ee70609b272493d461f616accbf44531c21...
  • feec06f chore(deps): update engines to 5.8.0-33.babfd598f1377beef44addb85eb86ac93bdf4...
  • 811f1aa chore(deps): update opentelemetry packages (#22473)
  • e62475d chore(deps): update dependency esbuild to v0.19.10 (#22471)
  • 6604348 chore(deps): update engines to 5.8.0-31.01382e5cb656d1344b51fced95d399caaac3d...
  • 1eacb61 chore(deps): update engines to 5.8.0-30.6363e0950d0b1c496c0219c4289695f6ddc5c...
  • e0935eb chore(deps): update engines to 5.8.0-26.388f03a4b4ce34a3e2039545f4b40bb33c43e...
  • c52c211 chore(deps): update engines to 5.8.0-25.f8ac68b940bcb96a1531920e361ab5fc74000...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@prisma/client](https://github.com/prisma/prisma/tree/HEAD/packages/client) from 5.6.0 to 5.8.1.
- [Release notes](https://github.com/prisma/prisma/releases)
- [Commits](https://github.com/prisma/prisma/commits/5.8.1/packages/client)

---
updated-dependencies:
- dependency-name: "@prisma/client"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 16, 2024
Copy link

vercel bot commented Jan 16, 2024

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

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
party-planner ⬜️ Ignored (Inspect) Visit Preview Jan 16, 2024 0:16am

Copy link
Author

dependabot bot commented on behalf of github Feb 6, 2024

Superseded by #57.

@dependabot dependabot bot closed this Feb 6, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/prisma/client-5.8.1 branch February 6, 2024 00:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants