chore: upgrade to Prisma 5.21

[ymc9]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the version numbers of the @prisma/client and prisma packages from 5.20.x to 5.21.x in two files: script/test-scaffold.ts and tests/integration/tests/cli/plugins.test.ts. The changes specifically affect dependency management in the test project scaffolding process and the test configurations, while the overall structure and logic of the files remain unchanged.

Changes

File(s)	Change Summary
script/test-scaffold.ts	Updated @prisma/client version from 5.20.x to 5.21.x in the run function.
tests/integration/tests/cli/plugins.test.ts	Updated @prisma/client version from 5.20.x to 5.21.x in depPkgs and devDepPkgs; updated prisma version from 5.20.x to 5.21.x.

Possibly related issues

• Upgrade peer dependencies to Prisma 5.15 #1478: This issue addresses upgrading peer dependencies to Prisma 5.15, which is relevant to the overall dependency management context of this PR.
• Prisma 5.19 support #1669: This issue discusses support for Prisma 5.19, which relates to the ongoing updates and compatibility with newer Prisma versions.

Possibly related PRs

• chore: Prisma 5.20 support #1741: This PR updates the version numbers of the prisma and @prisma/client packages in the same files as the main PR, indicating a direct connection through similar changes in dependency versions.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4f00cf1 and f6ba6a5.

⛔ Files ignored due to path filters (7)

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

• script/test-scaffold.ts (1 hunks)
• tests/integration/tests/cli/plugins.test.ts (2 hunks)

🧰 Additional context used

🔇 Additional comments (4)

script/test-scaffold.ts (1)

22-22: LGTM! Prisma version updated as intended.

The update of Prisma and @prisma/client to version 5.21.x is consistent with the PR objectives. This change looks good and should keep the test scaffold up-to-date with the latest minor version.

To ensure a smooth transition, please:

1. Check the Prisma 5.21.x changelog for any breaking changes or new features that might affect the project.
2. Verify if other files in the project need to be updated for version consistency.

Run the following script to find other files that might need updating:

Would you like assistance in updating the project's documentation to reflect this Prisma version change?

✅ Verification successful

It looks like there was an error in the previous search script due to incorrect regex syntax. Let's correct the regex and rerun the search to identify any files still referencing Prisma version 5.20.x.

Please run the following script:

---

There was an issue with the previous search script due to an unrecognized file type. Let's adjust the script to remove the unsupported typescript type and ensure we can successfully find any references to Prisma version 5.20.x.

Please run the following script:

---

The previous search encountered issues with unrecognized file types. Let's adjust the rg command to use file extensions instead of type names to successfully locate any references to Prisma version 5.20.x.

Please run the following script:

---

Prisma version update verified successfully.

All references to Prisma version 5.20.x have been updated to 5.21.x in the codebase. No lingering references found.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Find other files that might reference Prisma version

# Search for files containing Prisma version references
echo "Files potentially referencing Prisma version:"
rg --type-add 'lock:*.lock' --type lock --type json --type typescript --type javascript -i '(prisma|@prisma\/client).*5\.20'

# Search for Prisma schema files
echo -e "\nPrisma schema files that might need review:"
fd -e prisma

Length of output: 865

---

Script:

#!/bin/bash
# Description: Find other files that might reference Prisma version

# Search for files containing Prisma version references with corrected regex
echo "Files potentially referencing Prisma version:"
rg --type-add 'lock:*.lock' --type lock --type json --type typescript --type javascript -i '(prisma|@prisma/client).*5\.20'

# Search for Prisma schema files
echo -e "\nPrisma schema files that might need review:"
fd -e prisma

Length of output: 786

---

Script:

#!/bin/bash
# Description: Find other files that might reference Prisma version

# Search for files containing Prisma version references with corrected rg command
echo "Files potentially referencing Prisma version:"
rg --type-add 'lock:*.lock' --type lock --type json --type javascript -i '(prisma|@prisma/client).*5\.20'

# Search for Prisma schema files
echo -e "\nPrisma schema files that might need review:"
fd -e prisma

Length of output: 768

---

Script:

#!/bin/bash
# Description: Find other files that might reference Prisma version

# Search for files containing Prisma version references using file extensions
echo "Files potentially referencing Prisma version:"
rg '(prisma|@prisma/client).*5\.20' -g '*.lock' -g '*.json' -g '*.ts' -g '*.js'

# Search for Prisma schema files
echo -e "\nPrisma schema files that might need review:"
fd -e prisma

Length of output: 707

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

88-88: LGTM: Prisma dev dependency version update

The update of prisma to version 5.21.x is consistent with the PR objective and matches the @prisma/client version update. This change should maintain compatibility within the test suite.

To ensure all Prisma-related packages are consistently updated across the project, please run the following script:

#!/bin/bash
# Description: Verify all Prisma-related package versions are updated to 5.21.x in package.json files

# Test: Search for Prisma package versions in package.json files. Expect: Only 5.21.x versions.
rg --type json '"@prisma/client": "\\^?5\.21\.x"|"prisma": "\\^?5\.21\.x"' $(fd -e json -e jsonc)

---

Line range hint 1-388: Suggestion: Run the test suite to verify compatibility

The changes to update Prisma-related package versions look good and are consistent with the PR objective. However, to ensure full compatibility and catch any potential issues, it's recommended to run the entire test suite.

Please run the following command to execute the test suite:

#!/bin/bash
# Description: Run the test suite to verify compatibility with updated Prisma versions

# Test: Execute the test suite. Expect: All tests to pass.
npm test

If any issues arise during the test run, please address them before merging this PR.

---

78-78: LGTM: Prisma client version update

The update of @prisma/client to version 5.21.x is in line with the PR objective. This change should maintain compatibility with the test suite.

To ensure all Prisma-related packages are consistently updated, please run the following script:

✅ Verification successful

---

Prisma-related package versions have been successfully updated to 5.21.x across all relevant files. No issues found.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all Prisma-related package versions are updated to 5.21.x

# Test: Search for Prisma package versions. Expect: Only 5.21.x versions.
rg --type typescript '"@prisma/client@5\.21\.x"|"prisma@5\.21\.x"'

Length of output: 2512

---

Script:

#!/bin/bash
# Description: Verify all Prisma-related package versions are updated to 5.21.x

# Find all JSON files and search for Prisma package versions matching 5.21.x
fd --type json | xargs rg '"@prisma/client": "\^?5\.21\.x"|"prisma": "\^?5\.21\.x"'

Length of output: 844

---

Script:

#!/bin/bash
# Description: Verify all Prisma-related package versions are updated to 5.21.x

# Find all JSON files and search for Prisma package versions matching 5.21.x
fd --type f -e json | xargs rg '"@prisma/client": "\^?5\.21\.x"|"prisma": "\^?5\.21\.x"'

Length of output: 677

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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