chore: prisma 6.16 update

[ymc9]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

Replaced Prisma package version strings in tests by updating '@prisma/client' and 'prisma' from 6.15.x to 6.16.x within tests/integration/tests/cli/plugins.test.ts. No other files or exported entities were changed.

Changes

Cohort / File(s)	Summary of Changes
Test Prisma version bump tests/integration/tests/cli/plugins.test.ts	Updated pinned versions: @prisma/client 6.15.x → 6.16.x and prisma 6.15.x → 6.16.x in test setup.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update to prisma 6.15 #2228 — Prior incremental bump in the same file (6.14 → 6.15) for Prisma packages.
• chore: update to Prisma 6.6 #2079 — Similar update to Prisma version pins in tests/integration/tests/cli/plugins.test.ts.
• chore: Prisma 5.22 support #1829 — Earlier PR updating Prisma package versions in the same test file.

Pre-merge checks (1 passed, 1 warning, 1 inconclusive)

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
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.
Description Check	❓ Inconclusive	I cannot evaluate the PR description because the actual <current_description> text was not provided; the raw_summary shows a Prisma 6.15→6.16 package bump which would be on-topic, but without the PR description I cannot conclusively determine if it is sufficiently related or descriptive.	Please provide the PR description or confirm its contents; if absent, ensure the description at minimum states the Prisma package bumps and any relevant migration notes so this check can be marked as passing.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "chore: prisma 6.16 update" succinctly and accurately summarizes the primary change (bumping Prisma packages to 6.16) described in the raw_summary; it is concise, on-topic, and suitable for a teammate scanning history.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

📜 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 8962ad9 and 5bbd25c.

⛔ Files ignored due to path filters (11)

• 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). (5)

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

🔇 Additional comments (2)

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

78-78: LGTM: aligned @prisma/client to 6.16.x

Keeping runtime client on the same minor as the CLI below avoids generator mismatch. Looks good.

---

88-88: Hoist Prisma version into a single const

Define PRISMA_VERSION and reference it for both deps to avoid drift.

-            '@prisma/client@6.16.x',
+            `@prisma/client@${PRISMA_VERSION}`,

-            'prisma@6.16.x',
+            `prisma@${PRISMA_VERSION}`,

Add near other constants (e.g., after Line 71):

const PRISMA_VERSION = '6.16.x';

Run locally to confirm no lingering 6.15 pins:
rg -nP '@prisma/client@6.15|prisma@6.15'

✨ 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.16

---

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.}