You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This upgrade from Prisma 6.14.0 to 6.19.3 is a minor version update that includes new features, bug fixes, and preparations for the upcoming Prisma 7 major release. While mostly additive, there are changes that require verification.
Key Changes & Potential Impacts:
Runtime Options (v6.15.0): The runtime options for Prisma Client have been simplified. Obsolete aliases like node and deno-deploy have been removed in favor of nodejs and deno respectively. If you were using these older aliases in your schema, you will need to update them.
Rust-Free Engine (v6.16.0): The new TypeScript-based query engine is now generally available. While it is an opt-in feature in version 6, it represents a significant architectural shift that will become the default in v7. Adopting it requires installing a database-specific driver adapter (e.g., @prisma/adapter-pg).
Configuration with prisma.config.ts (v6.18.0): Prisma is moving configuration from schema.prisma to a new prisma.config.ts file. This is currently optional but will be required in v7. The prisma init command now automatically creates this file.
Recommendation:
Review your schema.prisma file for the runtime option in the generator block and update it if you are using a removed alias. Although the Rust-free engine and prisma.config.ts are opt-in, it is recommended to review the documentation to prepare for the eventual migration to Prisma 7. No other breaking API changes are documented in this version range.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 1 vulnerabilities in the pnpm dependencies of this project.
Snyk changed the following file(s):
internal-packages/database/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-EFFECT-15746380
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Race Condition
This change is