chore(deps-dev): bump prisma from 5.22.0 to 7.8.0#176
Conversation
Bumps [prisma](https://github.com/prisma/prisma/tree/HEAD/packages/cli) from 5.22.0 to 7.8.0. - [Release notes](https://github.com/prisma/prisma/releases) - [Commits](https://github.com/prisma/prisma/commits/7.8.0/packages/cli) --- updated-dependencies: - dependency-name: prisma dependency-version: 7.8.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
📝 WalkthroughWalkthroughThe ChangesPrisma Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![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
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 45: The Prisma upgrade is incomplete: update `@prisma/client` to ^7.8.0 to
match prisma, add the required DB driver adapter dependency (e.g., add
"@prisma/adapter-pg": "^7.8.0"), modify prisma/schema.prisma generator from
provider = "prisma-client-js" to provider = "prisma-client" and add an output
path (e.g., output = "./generated/client"), add a new prisma.config.ts at the
repo root and move datasource configuration there, and update all instantiations
of PrismaClient (new PrismaClient(...)) to pass the adapter instance per v7
driver API; ensure Node.js and TypeScript versions meet the v7 requirements.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 50390b5e-5fe4-4c04-98c2-a1a9a88349b8
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "pino-pretty": "^13.1.3", | ||
| "prettier": "^3.8.3", | ||
| "prisma": "^5.14.0", | ||
| "prisma": "^7.8.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Prisma 7 breaking changes and migration guide from version 5
💡 Result:
Prisma ORM 7, released in November 2025 [1][2], introduces several breaking changes primarily from the shift to a Rust-free, ESM-based Prisma Client, mandatory driver adapters, and a new configuration model. The official migration guide covers upgrades from earlier versions like v5 or v6 [3][4][5]. Since v5 to v6 and v6 to v7 each have their guides, apply them sequentially, but v7 changes dominate. Key breaking changes and migration steps from v5 (Node 14+ in v5 [6]) to v7 (requires Node 20.19+ and TypeScript 5.4+ [5]): 1. Update packages: npm install prisma@latest @prisma/client@latest (and database-specific adapter, e.g., @prisma/adapter-pg for Postgres) [3][7]. 2. Schema changes [3][4]: - Replace generator provider 'prisma-client-js' with 'prisma-client' (Rust-free client for faster queries, smaller bundles). - Make 'output' required in generator block (e.g., output = './generated/client'), no longer defaults to node_modules/. Update imports after prisma generate [3]. - Remove/deprecate url, directUrl, shadowDatabaseUrl from datasource; move to prisma.config.ts [8]. 3. Create prisma.config.ts at root for CLI config (migrations, datasource url=env('DATABASE_URL'), etc.) [8][9][7]. Explicitly load env vars with import 'dotenv/config' [1]. 4. PrismaClient instantiation requires driver adapter [3][4]: Before (v5/6): const prisma = new PrismaClient After: import { PrismaClient } from '@prisma/client'; import { PrismaPg } from '@prisma/adapter-pg'; import { PrismaD1 } from '@prisma/adapter-d1'; // etc. const adapter =... // e.g., PrismaPg.fromPgString(process.env.DATABASE_URL) const prisma = new PrismaClient({ adapter }) [3]. 5. Removed features [3][1]: - Client middleware -> use extensions. - Metrics from client extensions. - Automatic seeding in prisma migrate dev/reset; run prisma db seed separately. - CLI flags: --skip-generate, --skip-seed, --schema, --url from db execute [3]. 6. Other: SSL cert validation stricter (node-pg) [3]. MongoDB not supported yet [1]. Run npx prisma generate after changes. Create baseline migration post-upgrade [10]. For full details, follow official guide: https://www.prisma.io/docs/orm/more/upgrades/to-v7 [3][4]. Test thoroughly, especially Client creation and CLI commands. Intermediate v6 upgrade if needed (e.g., full-text search changes [10]).
Citations:
- 1: https://github.com/prisma/prisma/releases/tag/7.0.0
- 2: https://www.prisma.io/blog/announcing-prisma-orm-7-0-0
- 3: https://www.prisma.io/docs/orm/v6/more/upgrades/to-v7
- 4: https://www.prisma.io/docs/guides/upgrade-prisma-orm/v7
- 5: https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions
- 6: https://www.prisma.io/docs/guides/upgrade-prisma-orm/v5
- 7: https://www.prisma.io/docs/ai/prompts/prisma-7
- 8: Prisma 7 breaking changes to Prisma config file, and prisma schema prisma/prisma#28573
- 9: https://medium.com/@gargdev010300/how-i-configured-prisma-7-new-changes-issues-and-how-i-solved-them-d5ca728c5b9f
- 10: https://prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6
🏁 Script executed:
#!/bin/bash
# Check if there's a Prisma schema file that might need updates for v7 compatibility
fd -e prisma -x echo "Found Prisma schema: {}"
# Check for any Prisma-related configuration or generated files
fd -t d -g "prisma" -x echo "Found Prisma directory: {}"Repository: JonasBaeumer/AgentWallet
Length of output: 145
🏁 Script executed:
# Check package.json around line 21 for `@prisma/client` and other context
sed -n '15,30p' package.json
# Also check line 45 context
sed -n '40,50p' package.jsonRepository: JonasBaeumer/AgentWallet
Length of output: 868
🏁 Script executed:
# Examine the current Prisma schema
head -20 prisma/schema.prisma
# Check if prisma.config.ts exists
ls -la prisma/config.ts 2>/dev/null || echo "prisma.config.ts not found in prisma/"
ls -la prisma.config.ts 2>/dev/null || echo "prisma.config.ts not found at root"Repository: JonasBaeumer/AgentWallet
Length of output: 414
🏁 Script executed:
# Search for PrismaClient instantiation in the codebase
rg "new PrismaClient" --type ts --type tsx --type js --type jsx -A 3Repository: JonasBaeumer/AgentWallet
Length of output: 96
Critical: Prisma v7 migration is incomplete. Multiple changes are required beyond version bumping.
This PR upgrades the Prisma CLI to ^7.8.0 but leaves @prisma/client at ^5.14.0. However, the migration has broader scope than just matching versions. Prisma v7 requires several breaking changes:
-
Update both package versions to
^7.8.0:@prisma/client(line 21) remains at^5.14.0— must be updatedprisma(line 45) is correctly updated to^7.8.0
-
Add database driver adapter (missing from dependencies):
- v7 requires an explicit driver adapter, e.g.,
@prisma/adapter-pgfor PostgreSQL - Add to dependencies:
"@prisma/adapter-pg": "^7.8.0"
- v7 requires an explicit driver adapter, e.g.,
-
Update schema generator (currently in
prisma/schema.prisma):- Change
provider = "prisma-client-js"toprovider = "prisma-client" - Add required
outputfield (e.g.,output = "./generated/client")
- Change
-
Create
prisma.config.tsat repository root:- v7 requires a
prisma.config.tsfile for CLI configuration - Move
datasourceconfiguration from schema to this new config file
- v7 requires a
-
Update PrismaClient instantiation:
- All code creating
new PrismaClient()must pass a driver adapter instance
- All code creating
These changes are mandatory for v7. Without them, the application will fail at runtime. Node.js 20.19+ and TypeScript 5.4+ are also required.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 45, The Prisma upgrade is incomplete: update
`@prisma/client` to ^7.8.0 to match prisma, add the required DB driver adapter
dependency (e.g., add "@prisma/adapter-pg": "^7.8.0"), modify
prisma/schema.prisma generator from provider = "prisma-client-js" to provider =
"prisma-client" and add an output path (e.g., output = "./generated/client"),
add a new prisma.config.ts at the repo root and move datasource configuration
there, and update all instantiations of PrismaClient (new PrismaClient(...)) to
pass the adapter instance per v7 driver API; ensure Node.js and TypeScript
versions meet the v7 requirements.
Bumps prisma from 5.22.0 to 7.8.0.
Release notes
Sourced from prisma's releases.
... (truncated)
Commits
5723406fix(cli): route bootstrap telemetry to Prisma Web Properties project (#29473)8e71aa7fix(cli): install missing@prisma/clientinprisma bootstrap(#29444)ada077bfix(cli): bootstrap UX — auto-install deps, resumable flow, timeout handling ...9b0b7f5feat(cli): add prisma bootstrap command (#29374)5fece0achore: bump@prisma/devto 0.24.3 (#29396)45d7e0ffeat(cli): addprisma postgres linkcommand (#29352)adbdf15Pre-bundle Studio frontend assets and replace Hono (#29389)f8258adchore: bump effect to fix vulnerability (#29384)74839a9feat(cli): update bundled@prisma/studio-coreto 0.27.3 (#29376)309b4bcrefactor: extract 'prisma-client-js' into PRISMA_CLIENT_JS_PROVIDER constant ...Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for prisma 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@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