chore: update to Prisma 6.18

[ymc9]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates test files: bumps Prisma package versions in an integration test, adds TODO/ESLint comments in an expression-writer test, and marks a schema validation test suite as skipped (describe -> describe.skip), which prevents those tests from running. No other logic changes.

Changes

Cohort / File(s)	Summary
Prisma version bump tests/integration/tests/cli/plugins.test.ts	Update dependency strings: @prisma/client 6.17.x → 6.18.x and prisma 6.17.x → 6.18.x in test dependency arrays
Test comments added packages/schema/tests/generator/expression-writer.test.ts	Add // TODO: investigate CI failure and // eslint-disable-next-line jest/no-disabled-tests comments above the Expression Writer Tests block (no functional changes)
Test suite skipped packages/schema/tests/schema/validation/datasource-validation.test.ts	Convert describe(...) to describe.skip(...) and add TODO + eslint-disable-next-line comment above the suite, causing the contained tests to be skipped

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Developer
  participant CI as Test Runner
  note right of Dev #DDEBF7: Edit test files (version bump, comments, skip)
  Dev->>CI: Push PR
  alt Before change (describe)
    CI->>CI: Execute test suite block
    CI->>CI: Run individual tests
  else After change (describe.skip)
    CI->>CI: Skip test suite block
  end
  note right of CI #F3F8E7: Other tests proceed as usual

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Mixed small edits across test files (version strings, comment additions, and a skipped test suite) requiring review of test intents and CI impact.
• Areas to check:
  • Ensure Prisma version bump is compatible with CI/test fixtures in tests/integration/....
  • Confirm skipping datasource-validation.test.ts is intentional and note why (TODO).
  • Verify ESLint comment usage and that no tests were accidentally disabled.

Possibly related PRs

• chore: update to prisma 6.14 #2223 — modifies the same tests/integration/tests/cli/plugins.test.ts Prisma version pins (directly related).
• chore: update to Prisma 6.13 #2209 — edits the same test dependency lists and adds test skips/comments in schema tests (related at code level).
• chore: prisma 6.8 support #2118 — updates Prisma version specifiers in the same integration test file (related).

Pre-merge checks and finishing touches

❌ 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	No pull request description was provided by the author. While the check is intentionally lenient and only requires that a description (if present) not be completely off-topic, the absence of any description means there is no content to evaluate for relatedness to the changeset. The criteria do not explicitly address the case of a completely missing description, making it unclear whether this should be treated as a lenient pass or a failure to provide the minimum required context.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "chore: update to Prisma 6.18" directly relates to the primary change in the changeset, which is bumping the Prisma-related package versions from 6.17.x to 6.18.x in the dependency lists. While the changeset also includes ancillary modifications like adding TODO comments and skipping a test suite, the title clearly captures the main intent of the change from the developer's perspective. The title is concise, specific, and a teammate scanning the commit history would clearly understand the primary update being made.

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

---

📜 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 d980a1a and 38f3892.

📒 Files selected for processing (2)

• packages/schema/tests/generator/expression-writer.test.ts (1 hunks)
• packages/schema/tests/schema/validation/datasource-validation.test.ts (1 hunks)

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

• packages/schema/tests/generator/expression-writer.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). (5)

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

🔇 Additional comments (1)

packages/schema/tests/schema/validation/datasource-validation.test.ts (1)

3-5: Do not skip datasource validation tests without resolving the underlying CI failure.

Skipping the entire datasource validation test suite (6 tests) masks potential regressions and breaks test coverage for core functionality. The TODO comment provides no details about the failure or timeline for resolution.

Note: The expression-writer.test.ts file only receives the TODO comment—its tests still run normally and are not skipped.

Before merging this PR, investigate why the datasource validation tests fail with Prisma 6.18 and either:

• Fix the tests to work with the new Prisma version
• Fix the implementation if Prisma 6.18 introduced breaking changes
• Document a specific plan and timeline for re-enabling if this is a known Prisma issue

---

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