chore(docs): remove early access/preview labels from local development

[AmanVarshney01]

Summary

• Removed badge: preview from frontmatter
• Removed (Early Access) from metaTitle and metaDescription
• Removed the "Local Prisma Postgres is in Preview" callout

Local Prisma Postgres is no longer in early access/preview.

Summary by CodeRabbit

• Documentation
  • Updated local development documentation for Prisma Postgres, removing Early Access designation
  • Added Node.js v20 or later as a required prerequisite

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Feb 16, 2026 4:42pm

[coderabbitai]

Walkthrough

This pull request updates documentation for the Prisma Postgres local development guide. It removes early access language from metadata, eliminates preview status messaging, and adds a Node.js v20 minimum version requirement to the guide.

Changes

Cohort / File(s)	Summary
Documentation Metadata & Content Update apps/docs/content/docs/postgres/database/local-development.mdx	Front matter metadata updated to remove "(Early Access)" terminology; badge field removed from header. Preview status indicator deleted. New Node.js v20+ requirement note added. Introductory text reorganized for clarity.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately describes the main change: removing early access and preview labels from the local development documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[github-actions]

🍈 Lychee Link Check Report

3660 links: ✅ 2985 OK | 🚫 9 errors | 🔀 0 redirects | 👻 664 excluded

❌ Errors

./apps/docs/content/docs.v6/(index)/prisma-orm/add-to-existing-project/mongodb.mdx

• [404] Developer freindly Doc for solving Error when running prisma+mongodb with connection string with no database name #5562 | Error (cached)

./apps/docs/content/docs.v6/(index)/prisma-orm/quickstart/mongodb.mdx

• [404] Developer freindly Doc for solving Error when running prisma+mongodb with connection string with no database name #5562 | Error (cached)

./apps/docs/content/docs.v6/orm/more/dev-environment/editor-setup.mdx

• [503] https://fig.io/ | Rejected status code (this depends on your "accept" configuration): Service Unavailable

./apps/docs/content/docs.v6/orm/prisma-client/observability-and-logging/opentelemetry-tracing.mdx

• [ERROR] https://opentelemetry.io/ecosystem/registry/?language=js&component=instrumentation | Error (cached)

./apps/docs/content/docs.v6/orm/prisma-client/setup-and-configuration/databases-connections/index.mdx

• [404] We could give some numbers for connection pool size / concurrency limits for Serverless AWS Lambda or link to GitHub issue #667 | Error (cached)

./apps/docs/content/docs/(index)/prisma-orm/add-to-existing-project/mongodb.mdx

• [404] Developer freindly Doc for solving Error when running prisma+mongodb with connection string with no database name #5562 | Error (cached)

./apps/docs/content/docs/(index)/prisma-orm/quickstart/mongodb.mdx

• [404] Developer freindly Doc for solving Error when running prisma+mongodb with connection string with no database name #5562 | Error (cached)

./apps/docs/content/docs/orm/more/dev-environment/editor-setup.mdx

• [503] https://fig.io/ | Rejected status code (this depends on your "accept" configuration): Service Unavailable

./apps/docs/content/docs/orm/prisma-client/observability-and-logging/opentelemetry-tracing.mdx

• [ERROR] https://opentelemetry.io/ecosystem/registry/?language=js&component=instrumentation | Error (cached)

---

Full Statistics Table

Status	Count
✅ Successful	2985
🔀 Redirected	0
👻 Excluded	664
🚫 Errors	9
⛔ Unsupported	2
⏳ Timeouts	0
❓ Unknown	0

[coderabbitai]

🧹 Nitpick comments (1)

apps/docs/content/docs/postgres/database/local-development.mdx (1)

15-15: Consider elevating the Node.js requirement into a callout or prerequisites list.
This is easy to miss in the flow; an admonition (e.g., :::note) or a short “Prerequisites” list would improve visibility and consistency across docs. Also add a period for polish.