Skip to content

chore(deps-dev): Bump the prisma group with 2 updates #26061

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps-dev): Bump the prisma group with 2 updates #26061

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions dev-packages/cloudflare-integration-tests/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
"@langchain/typesafe": "^0.0.2",
"@opentelemetry/api": "^1.9.1",
"@prisma/adapter-d1": "6.15.0",
"@prisma/client": "6.15.0",
"@prisma/client": "7.10.1",

@cursor cursor Bot Nov 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cloudflare Prisma adapter version mismatch

High Severity

@prisma/client and prisma are now 7.10.1 while @prisma/adapter-d1 stays at 6.15.0. The Cloudflare Prisma suite still uses a Prisma 6 schema with previewFeatures = ["driverAdapters"] and a datasource url, then generates the client before the worker runs, so generate and the D1 instrumentation test fail.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 3cb2bff. Configure here.

"@sentry-internal/test-utils": "11.10.0",
"@sentry/cloudflare": "11.10.0",
"@sentry/conventions": "0.30.0",
Expand All @@ -35,7 +35,7 @@
"hono": "^4.13.7",
"langchain": "^1.5.16",
"openai": "5.18.1",
"prisma": "6.15.0",
"prisma": "7.10.1",
"vite": "^8.3.5",
"vitest": "^4.1.11",
"wrangler": "4.156.0"
Expand Down
4 changes: 2 additions & 2 deletions dev-packages/node-integration-tests/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@
"@modelcontextprotocol/server": "^2.0.0",
"@neondatabase/serverless": "1.2.0",
"@prisma/adapter-pg": "7.2.0",
"@prisma/client": "6.15.0",
"@prisma/client": "7.10.1",

@cursor cursor Bot Nov 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prisma 6 tests run Prisma 7

High Severity

The shared @prisma/client and prisma packages jump from 6.15.0 to 7.10.1, but the Prisma ORM v6 suite does not pin its own versions. That suite generates a Prisma 6 schema, constructs PrismaClient without an adapter, and asserts Prisma 6 engine spans, so generate and the tests fail under Prisma 7.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 3cb2bff. Configure here.

"@prisma/orm-postgres": "8.0.0-rc.17",
"@sentry-internal/rollup-utils": "11.10.0",
"@sentry-internal/test-utils": "11.10.0",
Expand Down Expand Up @@ -109,7 +109,7 @@
"pino": "10.4.0",
"pino-next": "npm:pino@^9.12.0",
"postgres": "^3.4.7",
"prisma": "6.15.0",
"prisma": "7.10.1",
"proxy": "^4.1.0",
"react": "^18.3.1",
"redis-4": "npm:redis@^4.6.14",
Expand Down
Loading
Loading