Blog: signal Data Proxy discontinuation in metadata

[vanrensbird]

What

Metadata-only fix for /blog/prisma-data-proxy-xb16ba0p21. The post already carries a discontinuation note in the body (added May 2026), but the metaTitle and metaDescription still marketed Data Proxy as "(Early Access)" with no discontinuation signal. That meta is exactly what search snippets and LLM retrieval read first, and this page still ranks around position 4.7 with ~12k impressions per quarter plus ongoing AI citations, so it was actively teaching agents a dead product's story.

Changes

• metaTitle/metaDescription: now state the discontinuation and point to Prisma Postgres (built-in pooling).
• Update note: date bumped to July 2026, consolidated on Prisma Postgres per current positioning; own-database users are pointed at the deployment docs.
• In-body Early Access note: "is currently in Early Access" moved to past tense with a pointer to the update note.
• Modern alternatives list: Prisma Postgres first with the direct TCP connections capability; deployment docs cover own-database connection handling.
• updatedAt bumped; slug, title, body, and announcement history otherwise unchanged.

No code samples in the changed sections; the connection-pooling explainer body (the part still worth citing) is untouched.

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jul 6, 2026 4:17pm
docs	Ready	Preview, Comment	Jul 6, 2026 4:17pm
eclipse	Ready	Preview, Comment	Jul 6, 2026 4:17pm
site	Ready	Preview, Comment	Jul 6, 2026 4:17pm

[coderabbitai]

Warning

Review limit reached

@vanrensbird, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 08eb56c0-999a-405e-aef1-fd7ce23a1478

📥 Commits

Reviewing files that changed from the base of the PR and between f74f219 and 3f1588b.

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-data-proxy-xb16ba0p21/index.mdx

---

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.}

[argos-ci]

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

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jul 6, 2026, 4:23 PM