DC-5041 Datasource URLs Deprecated

[aidankmcalister]

Summary by CodeRabbit

• Documentation
  • Added deprecation notices for three datasource configuration fields (url, directUrl, shadowDatabaseUrl) as of Prisma ORM v7
  • Updated documentation to inform users these fields should now be configured via Prisma Config
  • Included migration guidance and notes to support users transitioning to the new configuration method

[coderabbitai]

Walkthrough

Documentation updates across three files add deprecation notices for datasource block fields (url, directUrl, shadowDatabaseUrl) in Prisma ORM v7, directing users to configure these via Prisma Config instead of the Prisma schema.

Changes

Cohort / File(s)	Change Summary
Prisma Schema Deprecation Documentation content/200-orm/100-prisma-schema/10-overview/02-data-sources.mdx, content/200-orm/500-reference/100-prisma-schema-reference.mdx	Added deprecation notices for url, directUrl, and shadowDatabaseUrl fields, marking them as deprecated in Prisma ORM v7 with guidance to configure via Prisma Config.
Prisma Config Documentation content/200-orm/500-reference/325-prisma-config-reference.mdx	Added inline notes documenting that datasource.url, datasource.shadowDatabaseUrl, and datasource.directUrl now replace the deprecated schema-level fields in Prisma ORM v7+.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify deprecation messaging is consistent across all three documentation files
• Confirm Prisma Config field documentation accurately reflects the replacement mappings for each deprecated field

Possibly related PRs

• docs(config): add missing datasource reference #7206: Main PR that deprecates datasource fields (url, directUrl, shadowDatabaseUrl) in Prisma schema; this PR documents and cross-references those deprecations across documentation pages.
• fix: add callout to Prisma Config DC-4961 #7095: Related documentation updates for Prisma Config that work in conjunction with this PR's datasource field migration guidance.

Pre-merge checks

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title accurately reflects the main change—adding deprecation notices for datasource URL fields in Prisma ORM v7.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[github-actions]

🍈 Lychee Link Check Report

Note: Links are cached for 5 minutes. Failed links (timeouts, rate limits) are retried in a second run with longer timeout.

📊 Results Overview

Status	Count
🔍 Total	2405
✅ Successful	2375
⏳ Timeouts	0
🔀 Redirected	8
👻 Excluded	21
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	1

Redirects per input

Redirects in 200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdx

• [200] https://github.com/prisma/docs/issues/new?title=Glossary%20suggestion%3A%20 | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://github.com/prisma/docs/issues/new?title=Glossary%20suggestion%3A%20 --> https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fprisma%2Fdocs%2Fissues%2Fnew%3Ftitle%3DGlossary%2520suggestion%253A%2520

Redirects in 800-guides/070-cloudflare-d1.mdx

• [200] https://github.com/prisma/prisma-examples/blob/latest/deployment-platforms/edge/cloudflare-workers/with-d1 | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://github.com/prisma/prisma-examples/blob/latest/deployment-platforms/edge/cloudflare-workers/with-d1 --> https://github.com/prisma/prisma-examples/tree/latest/deployment-platforms/edge/cloudflare-workers/with-d1

Redirects in 800-guides/090-nextjs.mdx

• [200] https://github.com/prisma/prisma-examples/blob/latest/orm/nextjs | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://github.com/prisma/prisma-examples/blob/latest/orm/nextjs --> https://github.com/prisma/prisma-examples/tree/latest/orm/nextjs

Redirects in 800-guides/170-react-router-7.mdx

• [200] https://github.com/prisma/prisma-examples/blob/latest/orm/react-router-7 | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://github.com/prisma/prisma-examples/blob/latest/orm/react-router-7 --> https://github.com/prisma/prisma-examples/tree/latest/orm/react-router-7

Redirects in 800-guides/350-authjs-nextjs.mdx

• [200] https://github.com/settings/developers | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://github.com/settings/developers --> https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fsettings%2Fdevelopers

Redirects in 800-guides/370-bun.mdx

• [200] https://pris.ly/bun-guide-example | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://pris.ly/bun-guide-example --> https://github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/bun-with-prisma-driver-adapters
• [200] https://pris.ly/bun_ppg_example | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://pris.ly/bun_ppg_example --> https://github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/bun

Redirects in 800-guides/380-vercel-app-deployment.mdx

• [200] https://pris.ly/vercel_app_deployment_demo?utm_source=docs | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://pris.ly/vercel_app_deployment_demo?utm_source=docs --> https://github.com/prisma/vercel-deployment-claim-demo?utm_source=docs&utm_campaign=vercel_app_deployment
  Full Github Actions output

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	ea9291b
Status:	✅  Deploy successful!
Preview URL:	https://a94c0346.docs-51g.pages.dev
Branch Preview URL:	https://dc-5041-datasource-url-depre.docs-51g.pages.dev

View logs

[aidankmcalister]

@CodeRabbit review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

content/200-orm/500-reference/325-prisma-config-reference.mdx (1)

104-104: Minor: Comment inconsistency with field name casing.

Line 104 references directURL (capital "URL"), but the actual field defined on line 108 is directUrl (lowercase "url"). While this is a pre-existing comment in the type definition (not part of the deprecation changes), consider aligning the comment to match the actual camelCase field naming convention.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e35e705 and ea9291b.

📒 Files selected for processing (3)

• content/200-orm/100-prisma-schema/10-overview/02-data-sources.mdx (1 hunks)
• content/200-orm/500-reference/100-prisma-schema-reference.mdx (1 hunks)
• content/200-orm/500-reference/325-prisma-config-reference.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📚 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/325-prisma-config-reference.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/325-prisma-config-reference.mdx
• content/200-orm/100-prisma-schema/10-overview/02-data-sources.mdx
• content/200-orm/500-reference/100-prisma-schema-reference.mdx

🔇 Additional comments (4)

content/200-orm/100-prisma-schema/10-overview/02-data-sources.mdx (1)

9-11: Deprecation notice placement and clarity look good.

The note block is positioned appropriately before the datasource example, ensuring readers encounter the deprecation warning early. The message is clear and actionable, directing users to configure these fields in Prisma Config.

content/200-orm/500-reference/325-prisma-config-reference.mdx (1)

377-379: Deprecation replacement notes are well-structured and consistent.

The inline notes clearly communicate what each Prisma Config datasource field replaces from the schema block. The placement immediately after each property description makes the relationship obvious to readers. The messaging is consistent across all three replacements, and the version indicator (v7 and later) is helpful.

Also applies to: 390-392, 403-405

content/200-orm/500-reference/100-prisma-schema-reference.mdx (2)

21-23: Table deprecation notices provide clear migration path.

The updated table entries effectively communicate the deprecation for each field (url, shadowDatabaseUrl, directUrl) with specific guidance on which Prisma Config field to use as a replacement. The embedded links to the corresponding config reference sections are helpful and appropriately scoped.

---

27-29: Note block complements table entries with emphasis.

The additional note block reinforces the deprecation message from a higher level, providing readers with a clear summary before diving into individual field details. While somewhat redundant with the table entries, it serves as a useful callout for users skimming the documentation.