fix(blog): Prisma Next posts still teach the removed migration apply command

[sorenbs]

Product gotcha: published content teaches a removed CLI verb

The Prisma Next CLI replaced prisma-next migration apply with the top-level prisma-next migrate (verified against prisma/prisma-next origin/main: the CLI ships an explicit removed-verb redirect that exits with "Use prisma-next migrate --to <contract> instead"). Two published blog posts still teach the old verb, so readers copying commands hit an unknown-command error on current builds.

Fixed here

• TypeScript Migrations in Prisma Next: two $ npx prisma-next migration apply invocations, the Fix: line inside the sample error output, and the workflow list item.
• MongoDB Without Compromise: one narrative "Run prisma-next migration apply to execute."

Not fixed here (needs the docs team, flagging for follow-up)

The apps/docs/content/docs/cli/next/* reference section documents the old CLI surface more broadly and needs regeneration rather than find/replace, e.g.:

• cli/next/migration-apply.mdx exists as a page (the verb is gone; the replacement migrate has different flags: --to, --advance-ref, --show, --from)
• cli/next/migration-ref.mdx documents migration apply --ref <name> (removed; refs are now prisma-next ref set|list|delete plus --to <ref>)
• cli/next/configuration.mdx lists migration apply among commands needing db.connection
• cli/next/db-update.mdx links to the migration-apply page

The new /orm/next/migrations section (#8025) documents the current surface and can serve as the reference for that update.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated migration command examples in two blog posts to use the current prisma-next migrate command.
  • Revised related walkthrough steps and error-output examples so readers see the latest migration workflow.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jul 7, 2026 12:10pm
docs	Ready	Preview, Comment	Jul 7, 2026 12:10pm
eclipse	Ready	Preview, Comment	Jul 7, 2026 12:10pm
site	Ready	Preview, Comment	Jul 7, 2026 12:10pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: daec4e7d-a5a0-4c4e-8ac0-63099a391915

📥 Commits

Reviewing files that changed from the base of the PR and between 044f348 and ce9ed37.

📒 Files selected for processing (2)

• apps/blog/content/blog/mongodb-without-compromise/index.mdx
• apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx

---

Walkthrough

Two blog articles were updated to replace the deprecated prisma-next migration apply command examples with the newer prisma-next migrate command across code snippets, failure output examples, and workflow instructions.

Changes

Blog documentation command updates

Layer / File(s)	Summary
MongoDB blog command update apps/blog/content/blog/mongodb-without-compromise/index.mdx	Migration plan output example changed from `prisma-next migration apply` to `prisma-next migrate`.
TypeScript migrations blog command updates apps/blog/content/blog/typescript-migrations-in-prisma-next/index.mdx	Workflow command, failure output example (command and "Fix" text), and checklist step all updated from `prisma-next migration apply` to `prisma-next migrate`.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• prisma/web#7933: Reworks onboarding docs to remove inline migration plan/apply command examples referencing the same migration CLI instructions.

Poem
A rabbit hopped through blog post lines,
Swapping "apply" for cleaner signs,
"migration apply" now bids goodbye,
"migrate" alone now catches the eye,
Two posts refreshed, both docs align! 🐇

🚥 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 clearly matches the PR's main change: updating Prisma Next blog posts to replace the removed migration apply command.
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.

---

_{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 7, 2026, 12:17 PM