⬆️ chore(deps): bump the prisma group across 1 directory with 3 updates

[dependabot]

Bumps the prisma group with 3 updates in the / directory: @prisma/client, @prisma/instrumentation and prisma.

Updates @prisma/client from 5.22.0 to 6.4.1

Release notes

Sourced from @​prisma/client's releases.

6.4.1

Today, we are issuing the 6.4.1 patch release. It fixes a few issues with the NPS survey and makes it respect the --no-hints CLI flag.

Fixes

Prisma CLI

• prisma/prisma#26364

6.4.0

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

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

Highlights

TypeScript-based configuration with prisma.config.ts (Early Access)

In this release, we're introducing an Early Access version of a TypeScript-based configuration file for Prisma ORM: prisma.config.ts.

This file will serve as a central configuration point for Prisma ORM:

import path from 'node:path'
export default {
earlyAccess: true, // required while in Early Access
schema: {
kind: 'single', // use 'multi' if you're using the prismaSchemaFolder preview feature
filePath: path.join('custom', 'prisma', 'schema.prisma')
}
})

With this file you are able to run any arbitrary code needed to get values required by Prisma ORM, such as database URLs from a secret store or fine-grained control of settings. It needs to live in the current working directory from where you're executing Prisma CLI commands (typically, the root of your project).

Note: If you're using prisma.config.ts, the Prisma CLI will not load environment variables from .env files. If you want to use a .env file with prisma.config.ts, you'll need to load the environment variables manually using the dotenv package (see here).

Learn more about the new prisma.config.ts file in the docs.

Case-insensitive mode in JSON filters

You can now do case-insensitive filtering on JSON data.

Just use the new mode option when filtering using string_contains, string_starts_with or string_ends_with in a JSON object and set it to "insensitive":

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

... (truncated)

Commits

• fe8ebbb fix(config): ts(2742) error (#26359)
• 5413f8a chore(deps): update engines to 6.4.0-29.a9055b89e58b4b5bfb59600785423b1db3d0e...
• bf427e3 chore(deps): update engines to 6.4.0-26.7e7c9b8394a8c99732582d1f3b0646e95e351...
• e002705 feat(prisma-config): ORM-628 use schema path from config file (#26333)
• 151a32f chore(deps): update engines to 6.4.0-25.613555cc0d9606bc115972eeb42c9127e09d2...
• 783fb1e fix(client): normalize outputDir (#21577)
• 839f215 refactor: extract reusable parts of the client engine into a new package (#26...
• 16be4b0 chore(deps): update engines to 6.4.0-24.b06b231b59f731b5063a26ba21c36320ce2fe...
• e241cc7 fix(bench): improve huge-schema benchmark stability on CodSpeed (#19327)
• 2c03244 fix(query compiler): add more known failing test (#26314)
• Additional commits viewable in compare view

Updates @prisma/instrumentation from 5.22.0 to 6.4.1

Release notes

Sourced from @​prisma/instrumentation's releases.

6.4.1

Today, we are issuing the 6.4.1 patch release. It fixes a few issues with the NPS survey and makes it respect the --no-hints CLI flag.

Fixes

Prisma CLI

• prisma/prisma#26364

6.4.0

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

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

Highlights

TypeScript-based configuration with prisma.config.ts (Early Access)

In this release, we're introducing an Early Access version of a TypeScript-based configuration file for Prisma ORM: prisma.config.ts.

This file will serve as a central configuration point for Prisma ORM:

import path from 'node:path'
export default {
earlyAccess: true, // required while in Early Access
schema: {
kind: 'single', // use 'multi' if you're using the prismaSchemaFolder preview feature
filePath: path.join('custom', 'prisma', 'schema.prisma')
}
})

With this file you are able to run any arbitrary code needed to get values required by Prisma ORM, such as database URLs from a secret store or fine-grained control of settings. It needs to live in the current working directory from where you're executing Prisma CLI commands (typically, the root of your project).

Note: If you're using prisma.config.ts, the Prisma CLI will not load environment variables from .env files. If you want to use a .env file with prisma.config.ts, you'll need to load the environment variables manually using the dotenv package (see here).

Learn more about the new prisma.config.ts file in the docs.

Case-insensitive mode in JSON filters

You can now do case-insensitive filtering on JSON data.

Just use the new mode option when filtering using string_contains, string_starts_with or string_ends_with in a JSON object and set it to "insensitive":

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

... (truncated)

Commits

• e4aca67 feat(instrumentation): Use versioned global for tracing helper (#26167)
• 2661c45 chore(deps): update dependency @​swc/core to v1.10.11 (#26191)
• d1a12be chore(deps): update devdependencies patch (non-major) (#26141)
• ecee3f5 chore(deps): update dependency @​opentelemetry/instrumentation to ^0.52.0 || ^...
• 218e14b feat(instrumentation): re-export registerInstrumentations (#25878)
• aa35416 chore(client): remove tracing preview feature usage (#25865)
• fd6499b chore(deps): update dependency @​swc/core to v1.10.1 (#25708)
• 0bb2b82 fix: integrate new tracing model (#25828)
• 4a827d4 chore(deps): update jest (#25682)
• See full diff in compare view

Updates prisma from 5.22.0 to 6.4.1

Release notes

Sourced from prisma's releases.

6.4.1

Today, we are issuing the 6.4.1 patch release. It fixes a few issues with the NPS survey and makes it respect the --no-hints CLI flag.

Fixes

Prisma CLI

• prisma/prisma#26364

6.4.0

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

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

Highlights

TypeScript-based configuration with prisma.config.ts (Early Access)

In this release, we're introducing an Early Access version of a TypeScript-based configuration file for Prisma ORM: prisma.config.ts.

This file will serve as a central configuration point for Prisma ORM:

import path from 'node:path'
export default {
earlyAccess: true, // required while in Early Access
schema: {
kind: 'single', // use 'multi' if you're using the prismaSchemaFolder preview feature
filePath: path.join('custom', 'prisma', 'schema.prisma')
}
})

With this file you are able to run any arbitrary code needed to get values required by Prisma ORM, such as database URLs from a secret store or fine-grained control of settings. It needs to live in the current working directory from where you're executing Prisma CLI commands (typically, the root of your project).

Note: If you're using prisma.config.ts, the Prisma CLI will not load environment variables from .env files. If you want to use a .env file with prisma.config.ts, you'll need to load the environment variables manually using the dotenv package (see here).

Learn more about the new prisma.config.ts file in the docs.

Case-insensitive mode in JSON filters

You can now do case-insensitive filtering on JSON data.

Just use the new mode option when filtering using string_contains, string_starts_with or string_ends_with in a JSON object and set it to "insensitive":

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

... (truncated)

Commits

• 4b7b9b1 fix(cli): be more cautious about showing the NPS survey (#26375)
• c69846e fix(cli): handle error event in NPS survey (#26376)
• fc01fa0 fix: do not show NPS survey when --no-hints is provided (#26372)
• 718fffe fix(cli): add esbuild and esbuild-register to runtime dependencies (#26361)
• 3d18405 chore: bumped studio to new version (#26358)
• 7105e05 feat(prisma.config.ts):fix test regex for windows (#26356)
• cd29583 fix(config): fix issue with --config cli arg (#26336)
• e002705 feat(prisma-config): ORM-628 use schema path from config file (#26333)
• 9b8a021 chore(config): cosmetic changes (#26328)
• 5ea7226 feat(config): parse Prisma Config's structure for conformance (#26303)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.35%. Comparing base (b0d6a4c) to head (ba0b32f).
Report is 2 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #1101    +/-   ##
========================================
  Coverage   93.35%   93.35%            
========================================
  Files         243      243            
  Lines       18316    18316            
  Branches     1872     1657   -215     
========================================
  Hits        17098    17098            
  Misses       1213     1213            
  Partials        5        5            

Flag	Coverage Δ
integrationtests	72.54% <ø> (ø)
node	93.35% <ø> (ø)
unittests	50.31% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.