⬆️ Bump @prisma/client from 2.14.0 to 2.29.1

[dependabot]

Bumps @prisma/client from 2.14.0 to 2.29.1.

Release notes

Sourced from @​prisma/client's releases.

2.29.1

Today, we are issuing the 2.29.1 patch release.

Fixes

Prisma Client

• Cannot find namespace 'debug' in 2.29.0
• Interactive transactions not working with $queryRaw and $executeRaw in 2.29.0
• Calling .catch() or .finally() on a prisma client model query does not fire the request in 2.29.0

2.29.0

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

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

Major improvements & new features

Interactive Transactions are now in Preview

Today we’re introducing Interactive Transactions – one of our most debated feature requests.

Interactive Transactions are a double-edged sword. While they allow you to ignore a class of errors that could otherwise occur with concurrent database access, they impose constraints on performance and scalability.

While we believe there are better alternative approaches, we certainly want to ensure people who absolutely need them have the option available.

You can opt-in to Interactive Transactions by setting the interactiveTransactions preview feature in your Prisma Schema:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["interactiveTransactions"]
}

Note that the interactive transactions API does not support controlling isolation levels or locking for now.

You can find out more about implementing use cases with transactions in the docs, and share your feedback.

Named Constraints are now in Preview

Named Constraints allow you to represent (when using introspection) and specify (when using Prisma Migrate) the names of constraints of the underlying database schema in your Prisma schema.

Before this release, you could only specify the underlying database constraint names for @@unique and @@index. This meant that you didn't have control over all constraint names in the database schema. In projects that adopted Prisma with introspection, some constraint names from the database were not represented in the Prisma schema. This could lead to the database schema across environments getting out of sync when one environment was introspected, and another was created with Prisma Migrate and had different constraint names.

Starting with this release, you can specify the underlying database constraint names for @id, @@id, @unique, and @relation constraints.

You can opt-in to Named Constraints by adding the namedConstraints preview feature to your Prisma Schema:

... (truncated)

Commits

• 88a9abe fix(studio): add pnpm override for sdk version to 2.29.0
• 5e2f220 fix: publish script for patch-dev
• 16e5876 fix(client): 2.29.1 fixes (#8720)
• 866cf2d fix(migrate): sql server database creation if needed (#8669)
• bf92279 chore(deps): update engines to 2.29.0-34.1be4cd60b89afa04b192acb1ef47758a3981...
• 9c8c80f chore(deps): update engines to 2.29.0-33.3e95e2ce1b5d175188d62c5e4b51db471bb0...
• fe3d63c feat(client): interactive transactions (#8384)
• e8ef374 chore(deps): update engines to 2.29.0-32.36af3f44e00e1f6ae2ef08ebf105fb0120b4...
• 0e1d530 test(client): @@​unique add namedConstraints test without flag (#8659)
• e9f6a3f chore(deps): update engines to 2.29.0-30.aaf86a8e39c1fd471bf24f732dab3d7b7496...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by prismabot, a new releaser for @​prisma/client since your current version.

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 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]

Superseded by #1830.