chore: update to Prisma 6.13

[ymc9]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

The version numbers for the @prisma/client and prisma packages were updated from 6.12.x to 6.13.x in the integration test configuration for CLI plugins. A test case in the Prisma schema generator tests and a view-related test suite were changed to be skipped with TODO comments referencing the Prisma 6.13 release. Additionally, the data model validator was updated to exempt models marked as views from the unique criteria validation. No other logic or code structure was changed.

Changes

Cohort / File(s)	Change Summary
Integration Test Dependency Version Bump tests/integration/tests/cli/plugins.test.ts	Updated @prisma/client and prisma dependency versions from 6.12.x to 6.13.x in test setup arrays. No other code changes.
Schema Generator Test Update packages/schema/tests/generator/prisma-generator.test.ts	Changed "view support" test case to skipped (it.skip) with a TODO comment referencing Prisma 6.13 release. No logic changed.
Data Model Validator Update packages/schema/src/language-server/validator/datamodel-validator.ts	Modified validation to exclude models marked as views from unique criteria checks. No other validation logic changed.
View Test Suite Disabled tests/integration/tests/enhancements/with-policy/view.test.ts	Disabled "View Policy Test" suite with describe.skip and added TODO comment for Prisma 6.13 release. No logic changes made.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• chore: update to Prisma 6.6 #2079: Updates @prisma/client and prisma versions in the same integration test setup, reflecting a similar version bump.
• chore: update to Prisma 6.7 #2108: Also updates @prisma/client and prisma versions in the same CLI plugin integration test file.
• chore: remove commented code #1794: Introduces broader validation enhancements in datamodel-validator.ts, related to unique identifier validation logic.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9b1e30e and 8067615.

📒 Files selected for processing (1)

• tests/integration/tests/enhancements/with-policy/view.test.ts (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• tests/integration/tests/enhancements/with-policy/view.test.ts

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: dependency-review
• GitHub Check: OSSAR-Scan
• GitHub Check: build-test (20.x)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: build-test (20.x)
• GitHub Check: build-test (20.x)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/prisma-6.13

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

tests/integration/tests/cli/plugins.test.ts (1)

72-82: Consider pinning the exact patch version for reproducible CI runs

Using the wildcard spec 6.13.x means every CI run may pick up the latest patch of 6.13, which can unexpectedly introduce breaking changes or regressions.
If deterministic builds are important for these integration tests, prefer an exact version (e.g., 6.13.1) or lock the version via package-lock.json/npm ci.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6d11737 and d3a9546.

⛔ Files ignored due to path filters (10)

• packages/plugins/trpc/tests/projects/nuxt-trpc-v10/package.json is excluded by !**/*.json
• packages/plugins/trpc/tests/projects/nuxt-trpc-v11/package.json is excluded by !**/*.json
• packages/plugins/trpc/tests/projects/t3-trpc-v11/package.json is excluded by !**/*.json
• packages/runtime/package.json is excluded by !**/*.json
• packages/schema/package.json is excluded by !**/*.json
• packages/sdk/package.json is excluded by !**/*.json
• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml, !**/*.yaml
• tests/integration/test-run/package.json is excluded by !**/*.json
• tests/integration/tests/frameworks/nextjs/test-project/package.json is excluded by !**/*.json
• tests/integration/tests/frameworks/trpc/test-project/package.json is excluded by !**/*.json

📒 Files selected for processing (1)

• tests/integration/tests/cli/plugins.test.ts (2 hunks)

🔇 Additional comments (1)

tests/integration/tests/cli/plugins.test.ts (1)

85-95: Runtime / dev-dependency alignment looks correct

prisma@6.13.x is kept in sync with @prisma/client@6.13.x, avoiding the common mismatch issue between the CLI and generated client.