Bump prisma from 6.19.2 to 7.3.0

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps prisma from 6.19.2 to 7.3.0.

Release notes

Sourced from prisma's releases.

7.3.0

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

ORM

• #28976: Fast and Small Query Compilers We've been working on various performance-related bugs since the initial ORM 7.0 release. With 7.3.0, we're introducing a new compilerBuild option for the client generator block in schema.prisma with two options: fast and small. This allows you to swap the underlying Query Compiler engine based on your selection, one built for speed (with an increase in size), and one built for size (with the trade off for speed). By default, the fast mode is used, but this can be set by the user:

generator client {
  provider = "prisma-client"
  output   = "../src/generated/prisma"
  compilerBuild = "fast" // "fast" | "small"
}

We still have more in progress for performance, but this new compilerBuild option is our first step toward addressing your concerns!

• #29005: Bypass the Query Compiler for Raw Queries Raw queries ($executeRaw, $queryRaw) can now skip going through the query compiler and query interpreter infrastructure. They can be sent directly to the driver adapter, removing additional overhead.

• #28965: Update MSSQL to v12.2.0 This community PR updates the @prisma/adapter-mssql to use MSSQL v12.2.0. Thanks Jay-Lokhande!

• #29001: Pin better-sqlite3 version to avoid SQLite bug An underlying bug in SQLite 3.51.0 has affected the better-sqlite3 adapter. We’ve bumped the version that powers @prisma/better-sqlite3 and have pinned the version to prevent any unexpected issues. If you are using @prisma/better-sqlite3 , please upgrade to v7.3.0.

• #29002: Revert @map enums to v6.19.0 behavior In the initial release of v7.0, we made a change with Mapped Enums where the generated enum would get its value from the value passed to the @map function. This was a breaking change from v6 that caused issues for many users. We have reverted this change for the time being, as many different diverging approaches have emerged from the community discussion.

• prisma-engines#5745: Cast BigInt to text in JSON aggregation When using relationJoins with BigInt fields in Prisma 7, JavaScript's JSON.parse loses precision for integers larger than Number.MAX_SAFE_INTEGER (2^53 - 1). This happens because PostgreSQL's JSONB_BUILD_OBJECT returns BigInt values as JSON numbers, which JavaScript cannot represent precisely.

  // Original BigInt ID: 312590077454712834
  // After JSON.parse: 312590077454712830 (corrupted!)
  

  This PR cast BigInt columns to ::text inside JSONB_BUILD_OBJECT calls, similar to how MONEY is already cast to ::numeric.

  -- Before
  JSONB_BUILD_OBJECT('id', "id")
  -- After
  
  JSONB_BUILD_OBJECT('id', "id"::text)
  
  

... (truncated)

Commits

• 32e5614 chore(cli): bump hono and @prisma/dev, resolving hono vulnerability. (#...
• 2a44bb8 chore(cli): bump studio, fixing vitess introspection. (#29045)
• 011b6a6 chore: remove promotions (#29015)
• 90141bb chore(cli): bump studio, add northwind to sandbox. (#28985)
• fd479fd feat(qc): fast and small build modes (#28976)
• 815ba13 chore(cli): bump @prisma/dev, fix init usage following changes. (#28929)
• bebccbd feat(cli): customize prisma init based on the JS runtime (Bun vs other) (#2...
• 09b4a1d fix(cli): make prisma version --json emit JSON only to stdout (#28911)
• ed03287 feat(config): allow undefined urls in e.g. prisma generate (#28895)
• f80a3d3 chore(cli): bump @prisma/dev. (#28924)
• 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 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)

Summary by CodeRabbit

• Chores
  • Updated development dependency "prisma" from ~6.19.0 to ~7.3.0.
  • Internal change only; no user-facing features, UI, or behavior changes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Note

.coderabbit.yaml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized key(s) in object: 'tools'

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Walkthrough

Prisma dev dependency upgraded from ~6.19.0 to ~7.3.0 in packages/app/prisma-utils/package.json. No functional code changes are present in this update.

Changes

Cohort / File(s)	Summary
Dependency version update packages/app/prisma-utils/package.json	Prisma dev dependency bumped from ~6.19.0 to ~7.3.0 (one-line change in devDependencies).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• kibertoad
• CarlosGamero
• dariacm
• github-actions

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is missing required sections from the template: no 'Changes' section describing what was modified, no checklist items marked, and no AI assistance tracking selection.	Add a 'Changes' section describing the update, complete the checklist by marking appropriate items, and select one AI assistance option before merging.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main change: a Prisma dependency version bump from 6.19.2 to 7.3.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dependabot/npm_and_yarn/prisma-7.3.0

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/app/prisma-utils/package.json (1)

42-55: Align Prisma 7 devDependency with peer range and @prisma/client.

devDependencies.prisma is now ~7.3.0, but peerDependencies.prisma still caps <7.0.0 and devDependencies.@prisma/client remains ~6.19.0. Prisma's official guidance recommends upgrading prisma and @prisma/client together to the same version to avoid mismatches. The current configuration creates incompatible constraints that could break for library consumers. Either revert prisma to 6.x, or widen the peer range to <8.0.0 and bump @prisma/client to ~7.3.0.

Option B: align to Prisma 7.x

 "peerDependencies": {
-    "@prisma/client": ">=5.0.0 <7.0.0",
-    "prisma": ">=5.0.0 <7.0.0"
+    "@prisma/client": ">=5.0.0 <8.0.0",
+    "prisma": ">=5.0.0 <8.0.0"
 },
 "devDependencies": {
-    "@prisma/client": "~6.19.0",
+    "@prisma/client": "~7.3.0",
     ...
     "prisma": "~7.3.0",
 }