chore(deps): bump @prisma/generator-helper from 3.12.0 to 4.2.1 in /packages/cpg-template-typescript/template

[dependabot[bot]]

Bumps @prisma/generator-helper from 3.12.0 to 4.2.1.

Release notes

Sourced from @​prisma/generator-helper's releases.

4.2.1

Today, we are issuing the 4.2.1 patch release.

Fix in Prisma Client

• Fixed a cold start performance regression in case of multiple queries starting in parallel right after client creation

4.2.0

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

Major improvements

Prisma Client tracing support (Preview)

We're excited to announce Preview support for tracing in Prisma Client! 🎉

Tracing allows you to track requests as they flow through your application. This is especially useful for debugging distributed systems where each request can span multiple services.

With tracing, you can now see how long Prisma takes and what queries are issued in each operation. You can visualize these traces as waterfall diagrams using tools such as Jaeger, Honeycomb, or DataDog.

Read more about tracing in our announcement post and learn more in our documentation on how to start working with tracing.

Try it out and let us know what you think.

Isolation levels for interactive transactions

We are improving the interactiveTransactions Preview feature with the support for defining the isolation level of an interactive transaction.

Isolation levels describe different types of trade-offs between isolation and performance that databases can make when processing transactions. Isolation levels determine what types of data leaking can occur between transactions or what data anomalies can occur.

To set the transaction isolation level, use the isolationLevel option in the second parameter of the API. For example:

await prisma.$transaction(
  async (prisma) => {
    // Your transaction...
  },
  {
    isolationLevel: Prisma.TransactionIsolationLevel.Serializable,
    maxWait: 5000,
    timeout: 10000,
  }
)

Prisma Client supports the following isolation levels if they're available in your database provider:

• ReadCommitted
• ReadUncommitted

... (truncated)

Commits

• 7b8616f fix(client): error on attempt to generate a package in main client directory ...
• 3641079 chore(deps): update jest
• 118cae0 chore: remove maintainers from package.json (#14123)
• ec8b11c chore(deps): update dependency @​types/jest to v28.1.5
• 1b87fc1 chore(deps): update jest (#14165)
• 24c072b chore: bring engines-wrapper packages back & pnpm 7 (#13769)
• 6d33958 chore(deps): update dependency jest-junit to v14
• da4538d fix(client): support list defaults in DMMF types (#13984)
• df2b10e chore(deps): update devdependencies (non-major)
• eb7d587 chore(deps): update dependency @​types/jest to v28.1.3
• Additional commits viewable in compare view

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)