-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat(deps): bump @prisma/client from 6.15.0 to 7.4.0 #19302
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.
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
base: develop
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -37,7 +37,7 @@ | |
| "@nestjs/core": "^11", | ||
| "@nestjs/platform-express": "^11", | ||
| "@prisma/adapter-pg": "7.2.0", | ||
| "@prisma/client": "6.15.0", | ||
| "@prisma/client": "7.4.0", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Prisma v6 test now runs against v7 clientHigh Severity The Prisma v6 integration test doesn't pin its |
||
| "@sentry/aws-serverless": "10.39.0", | ||
| "@sentry/core": "10.39.0", | ||
| "@sentry/node": "10.39.0", | ||
|
|
||


There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prisma CLI version not bumped to match client
High Severity
@prisma/clientis bumped to7.4.0but theprismaCLI dependency (at line 78) remains at6.15.0. Prisma requires bothprismaand@prisma/clientto be the same version — this is a major version mismatch (6 vs 7) that will cause failures during schema generation and migrations, and likely break integration tests.