feat(deps): bump @prisma/client from 6.15.0 to 7.4.0#19302
feat(deps): bump @prisma/client from 6.15.0 to 7.4.0#19302dependabot[bot] wants to merge 1 commit intodevelopfrom
Conversation
| "@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.
Prisma CLI version not bumped to match client
High Severity
@prisma/client is bumped to 7.4.0 but the prisma CLI dependency (at line 78) remains at 6.15.0. Prisma requires both prisma and @prisma/client to 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.
Bumps [@prisma/client](https://github.com/prisma/prisma/tree/HEAD/packages/client) from 6.15.0 to 7.4.0. - [Release notes](https://github.com/prisma/prisma/releases) - [Commits](https://github.com/prisma/prisma/commits/7.4.0/packages/client) --- updated-dependencies: - dependency-name: "@prisma/client" dependency-version: 7.4.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
e493ce7 to
a9b493f
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| "@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.
Prisma v6 test now runs against v7 client
High Severity
The Prisma v6 integration test doesn't pin its @prisma/client version via additionalDependencies (unlike the v5 and v7 tests), so it uses the default from package.json. With this bump, it will now run against @prisma/client@7.4.0. The test expects v6-specific spans like prisma:client:detect_platform, prisma:client:load_engine, prisma:engine:connect, and prisma:engine:query, which differ from v7's span structure (e.g., prisma:client:db_query, db.system.name), causing test failures.
Bumps @prisma/client from 6.15.0 to 7.4.0.
Release notes
Sourced from
@prisma/client's releases.... (truncated)
Commits
7060f68chore(deps): update engines to 7.4.0-20.ab56fe763f921d033a6c195e7ddeb3e255bdb...91a24a9feat: query plan caching (#29038)b49d446chore(deps): update engines to 7.4.0-18.2997580c8cb38878f73e100453e7b27119e8f...3c99935chore(deps): update engines to 7.4.0-17.57b675f79cd26fbf702d70f9a13d2b7b2fad9...e7504d7chore(deps): update engines to 7.4.0-16.d0314091cdd30494eefc61d346f8c09aca20d...1e6c91cchore(deps): update engines to 7.4.0-15.6129681d45ea4510d3372dd5b28f6b8927584...e1bfd22chore(deps): update engines to 7.4.0-13.e876f7aec6b9be3e5147d061ed521ec45a845...12ca969chore(deps): update engines to 7.4.0-12.aa5ee090ba89988f1dce71be263f4bcd9519b...36b57cbchore(deps): update engines to 7.4.0-11.8583547702bad6d8e7de7d9812f7ec5c22e1c...b6afc3ftest: initialize the test client before the QPE (#29130)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@prisma/clientsince 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)