fix: removed EA tag

[luanvdw]

This PR removes the EA tag for Prisma Postgres Extensions, and renames the page to be called "Extensions"

Summary by CodeRabbit

• Documentation
  • Updated PostgreSQL extensions documentation page with refined titles and descriptions.
  • Removed early-access designation from the extensions documentation.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Mar 24, 2026 7:20am
docs	Ready	Preview, Comment	Mar 24, 2026 7:20am
eclipse	Ready	Preview, Comment	Mar 24, 2026 7:20am
site	Ready	Preview, Comment	Mar 24, 2026 7:20am

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Mar 24, 2026, 7:28 AM

[coderabbitai]

Walkthrough

This PR updates documentation frontmatter metadata for the PostgreSQL extensions page, simplifying the title to "Extensions," refining the description text, removing the early-access badge designation, and adjusting the metaDescription for improved consistency.

Changes

Cohort / File(s)	Summary
Documentation Metadata apps/docs/content/docs/postgres/database/postgres-extensions.mdx	Updated page frontmatter: title shortened to "Extensions", description refined to reference standard PostgreSQL extensions, early-access badge removed, and metaDescription updated for conciseness.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: removed EA tag' directly corresponds to the main change: removing the early-access badge from the PostgreSQL extensions documentation page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

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

6-6: Minor: Consider consistency in terminology.

The metaDescription uses "Postgres" while the description (line 3) uses "PostgreSQL". While both are acceptable, consistent terminology across metadata fields improves professionalism.

📝 Suggested consistency improvement

Option 1: Use "PostgreSQL" consistently:

-metaDescription: Learn about Postgres extensions with Prisma Postgres
+metaDescription: Learn about PostgreSQL extensions with Prisma Postgres

Option 2: Use "Postgres" consistently:

-description: Enable and use standard PostgreSQL extensions with Prisma Postgres.
+description: Enable and use standard Postgres extensions with Prisma Postgres.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/docs/content/docs/postgres/database/postgres-extensions.mdx` at line 6,
The metadata uses inconsistent terminology: the frontmatter field
metaDescription currently says "Postgres" while the description field uses
"PostgreSQL"; update either metaDescription or description so both use the same
term (choose and apply "PostgreSQL" or "Postgres" consistently), e.g., change
the value of metaDescription to match description or vice versa, ensuring the
fields named metaDescription and description are identical in terminology.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@apps/docs/content/docs/postgres/database/postgres-extensions.mdx`:
- Line 6: The metadata uses inconsistent terminology: the frontmatter field
metaDescription currently says "Postgres" while the description field uses
"PostgreSQL"; update either metaDescription or description so both use the same
term (choose and apply "PostgreSQL" or "Postgres" consistently), e.g., change
the value of metaDescription to match description or vice versa, ensuring the
fields named metaDescription and description are identical in terminology.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6409ca0c-7e91-4ddd-9658-eff1395044c9

📥 Commits

Reviewing files that changed from the base of the PR and between 52d993a and ccc7dc7.

📒 Files selected for processing (1)

• apps/docs/content/docs/postgres/database/postgres-extensions.mdx