chore: update to Prisma 6.19

[ymc9]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates Prisma client version from 6.17.x to 6.19.x in the CLI plugins test setup, affecting both runtime and development dependency specifications in the test configuration.

Changes

Cohort / File(s)	Change Summary
Prisma Client Version Bump tests/integration/tests/cli/plugins.test.ts	Updated prisma and @prisma/client versions from 6.17.x to 6.19.x in both runtime and development dependencies

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: use prisma 6.17 in tests #2287: Updates the same test file's Prisma dependency versions to 6.19.x.
• chore: update to Prisma 6.18 #2284: Bumps Prisma/@prisma/client version in the same test file (6.17.x → 6.18.x).
• chore: update to Prisma 6.17 #2268: Updates Prisma dependency versions in the same test file (6.16.x → 6.17.x).

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No description was provided by the author, making it impossible to evaluate whether it relates to the changeset.	Add a pull request description explaining the purpose of updating Prisma to 6.19, any breaking changes, and testing performed.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately describes the main change: updating Prisma from version 6.17.x to 6.19.x, which aligns with the file modification summary.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d6389fa and d29ef1b.

⛔ Files ignored due to path filters (12)

• package.json is excluded by !**/*.json
• 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-lock.json is excluded by !**/package-lock.json, !**/*.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)

⏰ 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). (4)

• GitHub Check: build-test (20.x)
• GitHub Check: dependency-review
• GitHub Check: build-test (20.x)
• GitHub Check: build-test (20.x)