chore: release 2.17.1 for Prisma 6.12

[ymc9]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change increments the JetBrains IDE package version from 2.17.0 to 2.17.1 and updates the prisma and @prisma/client dependency versions from 6.11.x to 6.12.x in both a test scaffold script and CLI plugins integration tests. No other logic or configuration changes are introduced.

Changes

File(s)	Change Summary
packages/ide/jetbrains/build.gradle.kts	Incremented JetBrains IDE package version from 2.17.0 to 2.17.1.
script/test-scaffold.ts tests/integration/tests/cli/plugins.test.ts	Updated prisma and @prisma/client dependencies from 6.11.x to 6.12.x.

Possibly related PRs

• zenstackhq/zenstack#1777: Updates the versions of prisma and @prisma/client dependencies in the same files, reflecting a related dependency version bump.
• zenstackhq/zenstack#2118: Updates version specifiers for prisma and @prisma/client in the same script and test files, indicating a similar dependency update.
• zenstackhq/zenstack#2180: Increments prisma and @prisma/client versions in the same files, representing a direct continuation of dependency updates.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • @coderabbitai modularize this function.
• 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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 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 (2)

script/test-scaffold.ts (1)

22-22: Consider pinning the exact Prisma patch version to keep test scaffolds reproducible

Using the semver pattern 6.12.x lets NPM resolve to whatever the latest 6.12.* is at install-time. A new patch release could unexpectedly break CI or mask regressions that haven’t been caught yet. For deterministic scaffolds (and easier bisecting) it’s usually safer to lock to the current patch, e.g. 6.12.1, and bump intentionally when you’re ready:

-run('npm i --no-audit --no-fund typescript prisma@6.12.x @prisma/client@6.12.x zod@^3.22.4 decimal.js @types/node');
+run('npm i --no-audit --no-fund typescript prisma@6.12.1 @prisma/client@6.12.1 zod@^3.22.4 decimal.js @types/node');

If you rely on floating patches, please confirm the build pipeline will still cache the resolved versions or that breakages are acceptable.

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

78-79: Lock Prisma client & CLI to the same fixed patch for consistent test runs

Great to see runtime and dev dependencies kept in sync. Similar to the scaffold script, using 6.12.x can introduce non-determinism into integration tests as soon as a new patch ships. Suggest locking both packages to the current patch (e.g. 6.12.1) or piping npm ci through a lock-file committed to VCS.

Also applies to: 88-89

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 415fee2 and 5456608.

⛔ Files ignored due to path filters (20)

• package.json is excluded by !**/*.json
• packages/ide/jetbrains/package.json is excluded by !**/*.json
• packages/language/package.json is excluded by !**/*.json
• packages/misc/redwood/package.json is excluded by !**/*.json
• packages/plugins/openapi/package.json is excluded by !**/*.json
• packages/plugins/swr/package.json is excluded by !**/*.json
• packages/plugins/tanstack-query/package.json is excluded by !**/*.json
• packages/plugins/trpc/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.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
• packages/server/package.json is excluded by !**/*.json
• packages/testtools/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 (3)

• packages/ide/jetbrains/build.gradle.kts (1 hunks)
• script/test-scaffold.ts (1 hunks)
• tests/integration/tests/cli/plugins.test.ts (2 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

script/test-scaffold.ts (1)

packages/testtools/src/schema.ts (1)

• run (45-67)

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

• GitHub Check: dependency-review
• GitHub Check: OSSAR-Scan

🔇 Additional comments (1)

packages/ide/jetbrains/build.gradle.kts (1)

11-13: Version bump looks good

No other build-script changes are needed for this minor release.