Bump @prisma/client from 6.19.2 to 7.3.0 #839
Conversation
Bumps [@prisma/client](https://github.com/prisma/prisma/tree/HEAD/packages/client) from 6.19.2 to 7.3.0. - [Release notes](https://github.com/prisma/prisma/releases) - [Commits](https://github.com/prisma/prisma/commits/7.3.0/packages/client) --- updated-dependencies: - dependency-name: "@prisma/client" dependency-version: 7.3.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
requested review from
a team,
CarlosGamero,
dariacm and
kibertoad
as code owners
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Prisma Dependency Update packages/app/prisma-utils/package.json |
Version bump: @prisma/client from ~6.19.0 to ~7.3.0 in devDependencies |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~2 minutes
Suggested reviewers
- kibertoad
- CarlosGamero
- dariacm
- github-actions
🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | ❓ Inconclusive | The description includes comprehensive release notes and change details but is missing required checklist items: no label selection confirmation and no explicit statements about documentation and test updates. | Complete the checklist by confirming which label applies (major/minor/patch/skip-release) and whether documentation and tests have been updated or determined unnecessary. |
✅ Passed checks (2 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title clearly and specifically describes the main change: bumping @prisma/client from version 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.
Comment @coderabbitai help to get the list of available commands and usage tips.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
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-45: Update peerDependencies to include Prisma 7.x support.The peerDependencies still specify
<7.0.0for both@prisma/clientandprisma, but devDependencies now uses@prisma/client7.3.0. This inconsistency will cause peer dependency warnings for consumers and signals that Prisma 7.x is unsupported when you're actually developing against it.🔧 Proposed fix
"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" },
🤖 Fix all issues with AI agents
In `@packages/app/prisma-utils/package.json`:
- Around line 52-55: The package.json has mismatched Prisma versions:
"@prisma/client" is "~7.3.0" while "prisma" is "~6.19.0"; update the "prisma"
dependency to the exact same version specifier as "@prisma/client" (e.g., change
the "prisma" entry to "~7.3.0") so both "@prisma/client" and "prisma" match
exactly and then run install/generate to ensure schema and client are
regenerated.
| "@prisma/client": "~7.3.0", | ||
| "@vitest/coverage-v8": "^4.0.15", | ||
| "cross-env": "^10.0.0", | ||
| "prisma": "~6.19.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Prisma @prisma/client prisma CLI version alignment requirements
💡 Result:
- Rule: Keep
prisma(the CLI) and@prisma/clientat the exact same version (same major/minor/patch). Prisma’s upgrade docs explicitly say to “upgrade both … packages to the same version,” and the version-specific upgrade guides show installing them together (e.g.,prisma@5with@prisma/client@5). [1] [2] - Why: The
prismapackage contains the CLI and the generators;prisma generate,migrate,db push, etc. can emit warnings and may behave unexpectedly if the CLI (prisma) and runtime client (@prisma/client) don’t match. A typical warning is: “Versions of prisma@X and@prisma/client@y don't match … Please make sure they have the same version.” [1] [3] - What to do in practice: Pin them to the same version in
package.json(often easiest is installing both in one command), then re-runprisma generate. [1] [2]
Sources: Prisma upgrade guide (same-version requirement) [1], Prisma “Upgrade to Prisma ORM 5” install commands [2], example mismatch warning from Prisma repo issue [3].
Update prisma CLI to match @prisma/client version.
@prisma/client is being updated to ~7.3.0 while the prisma CLI remains at ~6.19.0. Prisma requires these packages to be at the exact same version. Mismatches can cause schema generation warnings, failures in migrations and database operations, and unexpected runtime behavior.
🔧 Proposed fix
"@prisma/client": "~7.3.0",
"@vitest/coverage-v8": "^4.0.15",
"cross-env": "^10.0.0",
- "prisma": "~6.19.0",
+ "prisma": "~7.3.0",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "@prisma/client": "~7.3.0", | |
| "@vitest/coverage-v8": "^4.0.15", | |
| "cross-env": "^10.0.0", | |
| "prisma": "~6.19.0", | |
| "@prisma/client": "~7.3.0", | |
| "@vitest/coverage-v8": "^4.0.15", | |
| "cross-env": "^10.0.0", | |
| "prisma": "~7.3.0", |
🤖 Prompt for AI Agents
In `@packages/app/prisma-utils/package.json` around lines 52 - 55, The
package.json has mismatched Prisma versions: "@prisma/client" is "~7.3.0" while
"prisma" is "~6.19.0"; update the "prisma" dependency to the exact same version
specifier as "@prisma/client" (e.g., change the "prisma" entry to "~7.3.0") so
both "@prisma/client" and "prisma" match exactly and then run install/generate
to ensure schema and client are regenerated.
Bumps @prisma/client from 6.19.2 to 7.3.0.
Release notes
Sourced from
@prisma/client's releases.... (truncated)
Commits
b6fd1bdchore(deps): update engines to 7.3.0-16.9d6ad21cbbceab97458517b147a6a09ff43aa...223b6eachore: make the interpreter reusable (#29016)9d44eccfeat: compile raw queries in the client engine (#29005)272b176fix: revert "feat(client-generator-ts): [breaking] add support for ma… (#29002)c03d384fix: pin better sqlite for exists bug (#29001)8f69196chore(deps): update engines to 7.3.0-8.aee8f579c2872ad0cedd6fd7e9070704fdb361...768cd82fix: fix QC benchmark (#28987)fd479fdfeat(qc): fast and small build modes (#28976)a60094aperf: add query compilation and performance benchmarks (#28954)bebccbdfeat(cli): customizeprisma initbased on the JS runtime (Bun vs other) (#2...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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
✏️ Tip: You can customize this high-level summary in your review settings.