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

build(deps-dev): bump @prisma/client from 5.9.1 to 5.10.2 in /app/web #592

Merged

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 23, 2024

Bumps @prisma/client from 5.9.1 to 5.10.2.
Depends on #589

Release notes

Sourced from @​prisma/client's releases.

5.10.2

Today, we are issuing the 5.10.2 patch release.

Fix in Prisma CLI

5.10.1

Today, we are issuing the 5.10.1 patch release.

Fix in Prisma Client / Prisma CLI

5.10.0

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

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

Highlights

Optimized relation queries in MySQL (Preview)

This release brings the optimizations for relation queries from the previous releases to MySQL as well! This means that by enabling the relationJoins Preview feature with the mysql database provider, you now also get access to the relationLoadStrategy option in relation queries that let you choose whether you want to merged relations on the application- or database-level.

If you enable the relationJoins Preview feature, you can choose between the join and query options:

  • join (default): Sends a single query to the database and joins the data on the database-level.
  • query: Sends multiple queries to the database and joins the data on the application-level.

To get started, enable the Preview feature in your Prisma schema:

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

Be sure to re-generate Prisma Client afterwards:

npx prisma generate

And finally, specify the relation loading strategy for your relation query via the relationLoadStrategy option as follows:

await prisma.user.findMany({
</tr></table> 

... (truncated)

Commits
  • 5077f3f fix(client): Fix non-ascii characters handling in DataProxyEngien too
  • af54665 fix(client): Fix non-ascii characters handling in DataProxyEngien too
  • 7575474 fix(client): Fix base64 encoding of non-ascii schemas
  • 95ce26f feat(client): Mention Accelerate in "Too many connections" errors (#23113)
  • 794b61e chore(deps): update engines to 5.10.0-34.5a9203d0590c951969e85a7d07215503f467...
  • e742c67 chore(deps): update engines to 5.10.0-32.811068771a7c08ca615bdbdfea96f56a3d10...
  • 2daf967 feat(adapters): cloudflare-d1 - mapRow (#22750)
  • 758f22a chore(deps): update e2e tests (#23158)
  • 19511a5 chore(deps): update definitelytyped (#23155)
  • 4c57f19 chore(deps): update devdependencies patch (non-major) (#23157)
  • 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)

@dependabot dependabot bot added chore Refactor, clean up, rename, etc. dependencies Dependencies labels Feb 23, 2024
@github-actions github-actions bot added the dependent Depending on other work label Feb 26, 2024
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/app/web/develop/prisma/client-5.10.2 branch from 4f93a7b to 0896083 Compare February 26, 2024 18:57
@tthvo
Copy link
Contributor

tthvo commented Feb 26, 2024

@dependabot rebase

@github-actions github-actions bot removed the dependent Depending on other work label Feb 26, 2024
Copy link

This PR/issue depends on:

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

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/app/web/develop/prisma/client-5.10.2 branch from 0896083 to 8dc0f76 Compare February 26, 2024 22:15
@tthvo tthvo merged commit 4e01020 into develop Feb 26, 2024
12 checks passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/app/web/develop/prisma/client-5.10.2 branch February 26, 2024 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Refactor, clean up, rename, etc. dependencies Dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant