Skip to content

merge dev to main (v2.10.2) #1919

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 18, 2024
Merged

merge dev to main (v2.10.2) #1919

merged 2 commits into from
Dec 18, 2024

Conversation

ymc9
Copy link
Member

@ymc9 ymc9 commented Dec 18, 2024

No description provided.

Copy link
Contributor

coderabbitai bot commented Dec 18, 2024

📝 Walkthrough

Walkthrough

This pull request involves version updates across multiple files in the project. The primary changes include updating the project version from "2.10.1" to "2.10.2" in the JetBrains IDE package build script, and upgrading Prisma-related dependencies from version 6.0.x to 6.1.x in test-related scripts and integration tests.

Changes

File Change Summary
packages/ide/jetbrains/build.gradle.kts Version bumped from "2.10.1" to "2.10.2"
script/test-scaffold.ts Updated Prisma package versions from 6.0.x to 6.1.x
tests/integration/tests/cli/plugins.test.ts Updated @prisma/client and prisma package versions from 6.0.x to 6.1.x in test initialization

Possibly related PRs

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


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
🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
tests/integration/tests/cli/plugins.test.ts (1)

78-78: LGTM! Consider adding version compatibility test.

The Prisma dependency updates are consistent with test-scaffold.ts. Since this is a version upgrade, consider adding a test case to verify that all plugin functionality works correctly with Prisma 6.1.x.

Add a test case like:

it('verify prisma 6.1.x compatibility', async () => {
    // Initialize project with Prisma 6.1.x
    await initProject();
    
    // Add a schema that exercises Prisma-specific features
    const schemaContent = `
    generator client {
        provider = "prisma-client-js"
    }
    
    model TestModel {
        id String @id @default(cuid())
        // Add fields that use Prisma 6.1.x features
    }
    `;
    
    fs.writeFileSync('schema.zmodel', schemaContent);
    
    // Verify generation and compilation succeeds
    zenstackGenerate('npm');
    run('npx tsc');
});

Also applies to: 88-88

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f7f85ea and b41fd93.

⛔ Files ignored due to path filters (25)
  • .github/workflows/codeql.yml is excluded by !**/*.yml
  • .github/workflows/config/codeql-config.yml is excluded by !**/*.yml
  • .github/workflows/management-changelog.yml is excluded by !**/*.yml
  • .github/workflows/security-defender-for-devops.yml is excluded by !**/*.yml
  • 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-lock.json is excluded by !**/package-lock.json, !**/*.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)
✅ Files skipped from review due to trivial changes (1)
  • packages/ide/jetbrains/build.gradle.kts
🔇 Additional comments (1)
script/test-scaffold.ts (1)

22-22: LGTM! Verify Prisma version consistency.

The Prisma dependency update from 6.0.x to 6.1.x looks good. Let's verify version consistency across the codebase.

✅ Verification successful

Inconsistent Prisma versions detected in the codebase

The verification reveals version inconsistencies:

  • pnpm-lock.yaml shows dependencies on Prisma 6.0.0 and 5.14.0
  • The test scaffold and test files specify version 6.1.x
  • RedwoodJS dependencies are using Prisma 6.0.0

Let's verify if there are any package.json files specifying Prisma versions:


Version update is consistent with dependencies

The verification shows that the Prisma version update to 6.1.x in script/test-scaffold.ts is actually consistent with the project's dependencies:

  1. The SDK and runtime packages specify peer dependencies for Prisma as 5.0.0 - 6.1.x
  2. All test projects and integration tests are using version 6.1.x
  3. The version references in pnpm-lock.yaml are expected to be updated after running the scaffold script

The version update in the scaffold script is appropriate and maintains consistency with the project's dependency specifications.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any inconsistent Prisma version specifications across the codebase

# Search for Prisma version specifications
echo "Checking Prisma version specifications across the codebase..."
rg -g '!{node_modules,dist,build}/**' -e "prisma@[0-9]" -e "@prisma/client@[0-9]"

Length of output: 1239


Script:

#!/bin/bash
# Check package.json files for Prisma version specifications
echo "Checking package.json files for Prisma versions..."
fd package.json --type f --exec grep -l "prisma" {} \; --exec cat {}

Length of output: 16696

@ymc9 ymc9 merged commit 689d013 into main Dec 18, 2024
11 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant