content(blog): add Prisma Next April milestone roadmap post

[ankur-arch]

Adds the new "Prisma Next: April milestone complete" article and its hero/meta images, refreshes hero/meta assets across related Prisma Next blog posts, and ignores the locally cloned prisma-next repo so it can't be accidentally added as a gitlink.

Summary by CodeRabbit

• Documentation

  • Published a new blog post announcing Prisma Next’s April milestone, extension API availability to external authors, shipped reference extensions, progress on migrations and contract authoring parity, runtime transactional/RSC safety, MongoDB as a first‑class family, a SQLite proof‑of‑concept, streaming subscriptions timeline, and May guidance.

• Chores

  • Updated ignore rules to exclude a locally cloned repository directory.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	May 11, 2026 4:42pm
docs	Ready	Preview, Comment	May 11, 2026 4:42pm
eclipse	Ready	Preview, Comment	May 11, 2026 4:42pm
site	Ready	Preview, Comment	May 11, 2026 4:42pm

[argos-ci]

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

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	May 11, 2026, 4:48 PM

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Walkthrough

Adds a new MDX blog post describing Prisma Next’s April milestone (progress, shipped extensions, architecture status, gaps, and May Early Access plans) and updates .gitignore to exclude a locally cloned prisma-next/ repository.

Changes

Prisma Next April Milestone Blog Post

Layer / File(s)	Summary
Blog Post Metadata apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx	MDX frontmatter with title, slug, date, author, SEO fields, hero/meta images, and tags.
April-to-May Roadmap Introduction apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx	Announces April milestone completion and extension API availability; frames shift to May.
Extension API & Reference Extensions apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx	Call for extension authors and lists four shipped reference extensions with links.
Architecture Improvements and Feature Coverage apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx	Summarizes TypeScript migrations, contract parity, runtime transactional behavior, MongoDB first-class support, and SQLite proof of concept.
Gaps apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx	Streaming subscriptions did not ship; describes planned realtime subscription approach for May.
May: Early Access and Getting Started apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx	Early Access targets and watch list for DX, query/migration surfaces, and new platform support.
Try It Out & Production Notes apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx	Try-it-out instructions and production-readiness guidance (Prisma 7 recommended).
Further Reading & Closing Stat apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx	Links to roadmap/planning/status documents and a closing commit-volume stat.

Build and Repository Configuration

Layer / File(s)	Summary
Git Ignore Rule .gitignore	Added ignore entry to exclude a locally cloned prisma-next/ repository.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically summarizes the main change: adding a new blog post about the Prisma Next April milestone roadmap.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ 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.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx (1)

21-21: ⚡ Quick win

Standardize extension name formatting.

The extension names have inconsistent formatting—pgvector and arktype-json use backticks while ParadeDB and CipherStash don't. For consistency and clarity, either apply backticks to all four extensions or remove them from all.

✨ Proposed fix for consistent formatting

-Four extensions are now built on the new extension API: `pgvector`, `arktype-json`, ParadeDB, and CipherStash.
+Four extensions are now built on the new extension API: `pgvector`, `arktype-json`, `ParadeDB`, and `CipherStash`.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx` at line
21, The extension names are inconsistently formatted—pgvector and arktype-json
are in backticks while ParadeDB and CipherStash are not; update the text in the
blog content to consistently format all extension names (e.g., wrap ParadeDB and
CipherStash in backticks to match `pgvector` and `arktype-json`) so all four
extension identifiers use the same inline code style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx`:
- Line 34: Update the brand capitalization in the post content: find every
occurrence of the string "Arktype" in the MDX content (e.g., the article title,
headings, and body text) and change it to "ArkType" to match official branding
while leaving code or package names (like the npm package `arktype`) lowercase
where appropriate.

---

Nitpick comments:
In `@apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx`:
- Line 21: The extension names are inconsistently formatted—pgvector and
arktype-json are in backticks while ParadeDB and CipherStash are not; update the
text in the blog content to consistently format all extension names (e.g., wrap
ParadeDB and CipherStash in backticks to match `pgvector` and `arktype-json`) so
all four extension identifiers use the same inline code style.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 291eb598-9d31-4f49-9f4e-6f9ac45c76b9

📥 Commits

Reviewing files that changed from the base of the PR and between e9ef439 and 64cd85a.

⛔ Files ignored due to path filters (10)

• apps/blog/public/data-migrations-in-prisma-next/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/data-migrations-in-prisma-next/imgs/meta.png is excluded by !**/*.png
• apps/blog/public/mongodb-without-compromise/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/mongodb-without-compromise/imgs/meta.png is excluded by !**/*.png
• apps/blog/public/prisma-next-call-for-extension-authors/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/prisma-next-call-for-extension-authors/imgs/meta.png is excluded by !**/*.png
• apps/blog/public/prisma-next-roadmap-april-milestone/imgs/hero.svg is excluded by !**/*.svg
• apps/blog/public/prisma-next-roadmap-april-milestone/imgs/meta.png is excluded by !**/*.png
• apps/blog/public/the-next-evolution-of-prisma-orm/imgs/hero-61773d2cc286213d32b63e59605b0f5e0df4fe52-844x474-cb41e2fab7.svg is excluded by !**/*.svg
• apps/blog/public/the-next-evolution-of-prisma-orm/imgs/meta-558fe7eccfd12d3b52c325d62e5fa463a1b5f619-1200x640-3212708663.png is excluded by !**/*.png

📒 Files selected for processing (2)

• .gitignore
• apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx`:
- Line 41: Replace the loose phrase "higher-order codecs end to end" in the MDX
content with the hyphenated compound adjective "higher-order codecs end-to-end"
so the sentence reads correctly; locate the exact string "higher-order codecs
end to end" in the blog content and update it to "higher-order codecs
end-to-end".

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f88449a2-42bb-4f72-aedd-4bd6b0ab5e34

📥 Commits

Reviewing files that changed from the base of the PR and between 64cd85a and 900d9f3.

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx

[coderabbitai]

♻️ Duplicate comments (1)

apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx (1)

29-29: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use official product capitalization: ArkType.

The visible brand name should be ArkType (capital T) for consistency with official branding.

✍️ Suggested edit

-- **`arktype-json`** lets you store and query typed JSON columns with [Arktype](https://arktype.io) validation.
+- **`arktype-json`** lets you store and query typed JSON columns with [ArkType](https://arktype.io) validation.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx` at line
29, The brand name in the text fragment "**`arktype-json`** lets you store and
query typed JSON columns with [Arktype](https://arktype.io) validation." uses
incorrect capitalization; update the visible product name to "ArkType" (capital
T) wherever it appears (e.g., adjust the inline code or surrounding copy
referencing `arktype-json`/Arktype so the displayed brand reads "ArkType") while
keeping the package identifier/backticks if needed.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Duplicate comments:
In `@apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx`:
- Line 29: The brand name in the text fragment "**`arktype-json`** lets you
store and query typed JSON columns with [Arktype](https://arktype.io)
validation." uses incorrect capitalization; update the visible product name to
"ArkType" (capital T) wherever it appears (e.g., adjust the inline code or
surrounding copy referencing `arktype-json`/Arktype so the displayed brand reads
"ArkType") while keeping the package identifier/backticks if needed.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 40425a14-f090-4f9f-86e3-127c39699299

📥 Commits

Reviewing files that changed from the base of the PR and between 79da1b4 and 65ed7b8.

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx

[coderabbitai]

🧹 Nitpick comments (1)

apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx (1)

33-33: 💤 Low value

Consider hyphenating "end-to-end" for consistency.

While "end to end" is grammatically acceptable in this adverbial position, technical documentation typically hyphenates this compound term for consistency and clarity. This aligns with the hyphenation used elsewhere in Prisma documentation.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx` at line
33, Change the phrase "end to end" to the hyphenated form "end-to-end" in the
sentence "If you want to see what an extension looks like end to end, the
upcoming build-your-own-extension tutorial walks through a small one from
scratch." so it reads "...what an extension looks like end-to-end..." to match
Prisma's documentation hyphenation style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx`:
- Line 33: Change the phrase "end to end" to the hyphenated form "end-to-end" in
the sentence "If you want to see what an extension looks like end to end, the
upcoming build-your-own-extension tutorial walks through a small one from
scratch." so it reads "...what an extension looks like end-to-end..." to match
Prisma's documentation hyphenation style.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 299617ca-bd1d-4112-9e2f-e835f0ffe8d9

📥 Commits

Reviewing files that changed from the base of the PR and between 65ed7b8 and 41a0fe5.

📒 Files selected for processing (1)

• apps/blog/content/blog/prisma-next-roadmap-april-milestone/index.mdx