docs(): more v7 updates #7333
docs(): more v7 updates #7333
Conversation
WalkthroughMoves seeding config from package.json into Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Areas requiring extra attention:
Possibly related issues
Possibly related PRs
Pre-merge checks❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (6)📓 Common learnings📚 Learning: 2025-11-20T21:00:02.587ZApplied to files:
📚 Learning: 2025-10-08T16:23:00.388ZApplied to files:
📚 Learning: 2025-10-08T16:23:00.388ZApplied to files:
📚 Learning: 2025-10-08T16:22:57.129ZApplied to files:
📚 Learning: 2025-10-09T21:32:50.340ZApplied to files:
🪛 Gitleaks (8.29.0)content/200-orm/500-reference/380-connection-urls.mdx[high] 97-97: Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data. (jwt) [high] 106-106: Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data. (jwt) ⏰ 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)
Tip 📝 Customizable high-level summaries are now available in beta!You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.
Example instruction:
Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later. 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. Comment |
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects:
|
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdx
Errors in 200-orm/800-more/400-comparisons/03-prisma-and-mongoose.mdx
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
content/200-orm/500-reference/380-connection-urls.mdx (1)
264-264: MongoDB note could be more specific about the timeline. The current note states "We're working on support for MongoDB in Prisma 7" without indicating expected availability. Consider adding a reference to a tracking issue or roadmap link if available, so users know where to find updates.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx(3 hunks)content/200-orm/500-reference/380-connection-urls.mdx(2 hunks)content/800-guides/070-cloudflare-d1.mdx(1 hunks)
🧰 Additional context used
🧠 Learnings (5)
📓 Common learnings
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7301
File: content/800-guides/410-cloudflare-workers.mdx:87-107
Timestamp: 2025-11-20T21:00:02.587Z
Learning: Do not suggest changes to `prisma.config.ts` files in the prisma/docs repository, as the code examples are intentional for documentation purposes.
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.
📚 Learning: 2025-11-20T21:00:02.587Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7301
File: content/800-guides/410-cloudflare-workers.mdx:87-107
Timestamp: 2025-11-20T21:00:02.587Z
Learning: Do not suggest changes to `prisma.config.ts` files in the prisma/docs repository, as the code examples are intentional for documentation purposes.
Applied to files:
content/200-orm/500-reference/380-connection-urls.mdxcontent/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
📚 Learning: 2025-10-08T16:23:00.388Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.
Applied to files:
content/200-orm/500-reference/380-connection-urls.mdx
📚 Learning: 2025-10-09T21:32:50.340Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.
Applied to files:
content/200-orm/500-reference/380-connection-urls.mdxcontent/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
📚 Learning: 2025-10-15T06:36:42.423Z
Learnt from: jy-joung-bitor
Repo: prisma/docs PR: 0
File: :0-0
Timestamp: 2025-10-15T06:36:42.423Z
Learning: The `tsc --init` command requires the `--types node` flag to properly include Node.js type definitions from `types/node` in the generated tsconfig.json, even when types/node is already installed. Without this flag, TypeScript may not automatically pick up Node.js typings.
Applied to files:
content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
🪛 Gitleaks (8.29.0)
content/200-orm/500-reference/380-connection-urls.mdx
[high] 97-97: Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
(jwt)
[high] 106-106: Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.
(jwt)
⏰ 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: Check internal links
- GitHub Check: Cloudflare Pages
🔇 Additional comments (7)
content/200-orm/500-reference/380-connection-urls.mdx (2)
10-10: Clear and appropriately scoped version guidance. The updated text correctly distinguishes between Prisma config (v7/v8) and Prisma schema (v6) approaches, providing readers with accurate context. The mention of Prisma Postgres as an exception is helpful.
69-111: Tabbed examples for Accelerate are well-structured and version-specific. The Prisma 7 (prisma.config.ts) and Prisma 6 (schema.prisma) variants are clearly presented, making it easy for users on different versions to find the relevant example. The placeholderAPI_KEYexplanation on line 90 is helpful for context.content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx (3)
19-33: Strong anchor statement that clearly reframes the seeding approach. The opening sentence on line 19 explicitly states the new paradigm using prisma.config.ts and migrations.seed, which immediately orients readers to the expected configuration shape. The example code block demonstrates the complete structure users need.
41-42: Version boundary clearly marked. The "Prisma 6 Only" heading correctly signals to users that the integrated Prisma Migrate seeding behavior described in the following section applies only to Prisma 6, preventing confusion for Prisma 7 users who follow a different workflow.
139-142: Perfect. I've completed the verification. The search results show:
- No ts-node references exist in the
content/200-orm/300-prisma-migrate/directory- Only one seed-related file exists:
content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx(the file under review)- No ts-node references in any seed-related documentation files
This means the shift from ts-node to tsx in the file under review is isolated and consistent — there are no other seeding or seed-related documentation files that reference ts-node that would create downstream inconsistencies.
The dependency update from ts-node to tsx is consistent and creates no documentation inconsistencies. The search confirms no other seed-related documentation references ts-node, so the change to
tsxis isolated to this file and aligns with the modern TypeScript execution approach used throughout.content/800-guides/070-cloudflare-d1.mdx (2)
269-269: Excellent addition of non-blocking resource cleanup for serverless context. Usingctx.waitUntil(prisma.$disconnect())is the correct pattern for Cloudflare Workers—it ensures the connection is cleaned up without blocking the response. The inline comment indicating theawaitalternative is helpful for users who may need synchronous teardown in different contexts.
275-276: Clear, concise rationale for the cleanup. The explanation immediately following the code block explains the memory leak risk, which is crucial context for developers new to serverless patterns. This prevents users from wondering why the cleanup is necessary.
Deploying docs with
|
| Latest commit: |
2b3247b
|
| Status: | ⚡️ Build in progress... |
mhartington
force-pushed
the
minor-v7-updates
branch
from
349ef18 to
1d79e28
Compare
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 200-orm/200-prisma-client/150-using-raw-sql/200-raw-queries.mdx
Errors in 200-orm/800-more/400-comparisons/03-prisma-and-mongoose.mdx
|
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx(3 hunks)content/200-orm/500-reference/380-connection-urls.mdx(2 hunks)content/800-guides/070-cloudflare-d1.mdx(1 hunks)
🧰 Additional context used
🧠 Learnings (5)
📓 Common learnings
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7301
File: content/800-guides/410-cloudflare-workers.mdx:87-107
Timestamp: 2025-11-20T21:00:02.587Z
Learning: Do not suggest changes to `prisma.config.ts` files in the prisma/docs repository, as the code examples are intentional for documentation purposes.
📚 Learning: 2025-11-20T21:00:02.587Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7301
File: content/800-guides/410-cloudflare-workers.mdx:87-107
Timestamp: 2025-11-20T21:00:02.587Z
Learning: Do not suggest changes to `prisma.config.ts` files in the prisma/docs repository, as the code examples are intentional for documentation purposes.
Applied to files:
content/800-guides/070-cloudflare-d1.mdxcontent/200-orm/500-reference/380-connection-urls.mdxcontent/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
📚 Learning: 2025-10-08T16:23:00.388Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.
Applied to files:
content/200-orm/500-reference/380-connection-urls.mdx
📚 Learning: 2025-10-09T21:32:50.340Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.
Applied to files:
content/200-orm/500-reference/380-connection-urls.mdxcontent/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
📚 Learning: 2025-10-15T06:36:42.423Z
Learnt from: jy-joung-bitor
Repo: prisma/docs PR: 0
File: :0-0
Timestamp: 2025-10-15T06:36:42.423Z
Learning: The `tsc --init` command requires the `--types node` flag to properly include Node.js type definitions from `types/node` in the generated tsconfig.json, even when types/node is already installed. Without this flag, TypeScript may not automatically pick up Node.js typings.
Applied to files:
content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
🪛 LanguageTool
content/200-orm/500-reference/380-connection-urls.mdx
[grammar] ~264-~264: Ensure spelling is correct
Context: ...bbedContent> ### MongoDB _Support for MonogDB is limited to Prisma 6. We're working o...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~264-~264: Ensure spelling is correct
Context: ... Prisma 6. We're working on support for MonogDB in Prisma 7_ ```prisma file=schema.pri...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
⏰ 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). (1)
- GitHub Check: Check internal links
🔇 Additional comments (1)
content/800-guides/070-cloudflare-d1.mdx (1)
254-272: Resource cleanup pattern looks correct.The placement and use of
ctx.waitUntil()withprisma.$disconnect()is the right way to handle async cleanup after returning the response in a Cloudflare Worker without blocking the response handler. The explanatory note at lines 275–276 appropriately conveys the intent.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
🍈 Lychee Link Check Report
📊 Results Overview
|
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.