-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): bump @prisma/client from 6.17.0 to 7.3.0 #10
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: main
Are you sure you want to change the base?
Conversation
Bumps [@prisma/client](https://github.com/prisma/prisma/tree/HEAD/packages/client) from 6.17.0 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:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
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.
Pull request overview
This PR upgrades the @prisma/client dependency from version 6.17.0 to 7.3.0, representing a major version upgrade. Dependabot has automatically generated this PR to keep dependencies up to date.
Changes:
- Upgrade @prisma/client from 6.17.0 to 7.3.0 (major version upgrade)
- Update related lockfile entries for @prisma/client and @prisma/extension-accelerate
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| package.json | Updates @prisma/client dependency specifier from ^6.17.0 to ^7.3.0 |
| pnpm-lock.yaml | Updates resolved versions, integrity hashes, and engine requirements for @prisma/client 7.3.0, including new Node.js and TypeScript version requirements |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@nestjs/platform-express": "^11.0.1", | ||
| "@nestjs/schedule": "^6.0.1", | ||
| "@prisma/client": "^6.17.0", | ||
| "@prisma/client": "^7.3.0", |
Copilot
AI
Jan 26, 2026
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.
The Prisma Client is being upgraded to version 7.3.0, but the Prisma CLI (devDependency) remains at version 6.17.0. This version mismatch can cause serious compatibility issues because the Prisma CLI generates the Prisma Client code during the build process.
Prisma Client 7.x requires Prisma CLI 7.x for proper schema generation and database migrations. The versions should be kept in sync to avoid:
- Schema generation failures
- Type definition mismatches
- Migration incompatibilities
- Runtime errors
The Prisma CLI dependency in package.json should also be upgraded to ^7.3.0 to match the client version.
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.
@copilot open a new pull request to apply changes based on this feedback
pnpm-lock.yaml
Outdated
| specifier: ^7.3.0 | ||
| version: 7.3.0(prisma@6.17.0(typescript@5.9.3))(typescript@5.9.3) |
Copilot
AI
Jan 26, 2026
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 Client 7.3.0 has significantly stricter Node.js version requirements than the previous version. The package now requires Node.js ^20.19 || ^22.12 || >=24.0 (line 788), which means:
- Node.js 18.x is no longer supported
- Only specific patch versions of Node.js 20.x and 22.x are supported (20.19+, 22.12+)
- Node.js 24.x and above are supported
This is a breaking change from Prisma Client 6.17.0, which supported Node.js >=18.18. Before merging this PR, you should:
- Verify that your development, CI/CD, and production environments use compatible Node.js versions
- Update any Docker images, CI configurations, or deployment scripts to use Node.js 20.19+, 22.12+, or 24+
- Consider adding an "engines" field to package.json to enforce these Node.js version requirements
Without compatible Node.js versions, the application will fail to run with this upgraded Prisma Client.
| peerDependencies: | ||
| prisma: '*' | ||
| typescript: '>=5.1.0' | ||
| typescript: '>=5.4.0' |
Copilot
AI
Jan 26, 2026
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.
The TypeScript peer dependency requirement for Prisma Client has been increased from >=5.1.0 (in version 6.17.0) to >=5.4.0 (in version 7.3.0). While the project currently uses TypeScript 5.9.3, which satisfies this requirement, this change means that TypeScript versions below 5.4.0 are no longer supported.
This is a minor breaking change that shouldn't affect this project but is worth noting for documentation purposes.
|
@darwingtx I've opened a new pull request, #12, to work on those changes. Once the pull request is ready, I'll request review from you. |
Co-authored-by: darwingtx <79672629+darwingtx@users.noreply.github.com>
…vice Co-authored-by: darwingtx <79672629+darwingtx@users.noreply.github.com>
Sync Prisma CLI to 7.3.0 and migrate to Prisma 7 adapter pattern
Bumps @prisma/client from 6.17.0 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...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 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)