docs: update create-prisma release tags

Author: AmanVarshney01

.claude/skills/docs-writer/references/prisma-8.md

@@ -16,7 +16,7 @@ Instead, append your section's redirect map to the commented block in `apps/docs
 
 ## Accuracy: test before you write
 
-Every code sample must be executed against the published `@prisma/orm-*` packages before it lands, or clearly marked as conceptual. Scaffold throwaway apps with `create-prisma@next` non-interactive flags; use `bunx create-db` for PostgreSQL and `mongodb-memory-server` (replica set) for MongoDB. Key tested facts that older internal docs get wrong:
+Every code sample must be executed against the published `@prisma/orm-*` packages before it lands, or clearly marked as conceptual. Scaffold throwaway apps with `create-prisma@latest` non-interactive flags; use `bunx create-db` for PostgreSQL and `mongodb-memory-server` (replica set) for MongoDB. Key tested facts that older internal docs get wrong:
 
 - PostgreSQL model access is namespace-qualified: `db.orm.public.User`, `db.sql.public.user`. MongoDB uses flat lowercase plural roots (`db.orm.users`) and documents keep `_id`.
 - `.update()` / `.delete()` affect one record; `updateAll` / `deleteAll` / `*Count` are the bulk forms. No `.count()` terminal; use `.aggregate(...)`.

apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

@@ -102,7 +102,7 @@ We've shared [our benchmark repo](https://pris.ly/pn-benchmarks), so you can run
 There are two ways to [get started](https://www.prisma.io/docs/v8/quickstart/postgresql). To spin up a complete template app, scaffold one with:
 
 ```shell
-bunx create-prisma@next
+bunx create-prisma@latest
 ```
 
 This sets you up with a [Prisma Postgres](https://www.prisma.io/postgres) database and can deploy the app to [Prisma Compute](https://www.prisma.io/compute), our serverless runtime for Prisma apps, so you can see the bundle-size and cold-start benefits above end to end.

apps/blog/content/blog/search-encrypted-data-with-prisma-next-and-cipherstash/index.mdx

@@ -234,7 +234,7 @@ The fastest way to understand searchable encryption is to run it. You don't need
 ### 1. Create a Prisma 8 app
 
 ```sh
-npx create-prisma@next
+npx create-prisma@latest
 ```
 
 This gives you a fresh project with the contract-first workflow already wired up: a `contract.prisma` describing your models, and a migration loop that plans and applies the changes needed to match it.

apps/docs/content/docs/(index)/getting-started.mdx

@@ -6,7 +6,7 @@ metaTitle: Prisma 7 getting started
 metaDescription: Choose the fastest Prisma 7 setup path. Quickstarts and existing-project guides for Prisma ORM 7, Prisma Postgres, and Prisma Compute, plus an agent prompt.
 ---
 
-Prisma 7 is the current generally available release of Prisma ORM. Install it with `npx prisma@latest init`. This page collects the Prisma 7 starting points: start a new project, add Prisma to an existing one, then deploy.
+Prisma 7 is the current generally available release of Prisma ORM. Scaffold a new Prisma 7 app with `npx create-prisma@stable`, or add it to an existing project with `npx prisma@latest init`. This page collects the Prisma 7 starting points: start a new project, add Prisma to an existing one, then deploy.
 
 :::note
 
@@ -57,7 +57,7 @@ Set up the Prisma 7 stack: Prisma ORM 7, Prisma Postgres, and Prisma Compute.
 
 If I have not told you which framework template to use, stop and ask.
 
-1. Scaffold a new app non-interactively: `npx create-prisma@latest --name my-app --template [next|hono|nuxt|astro|nest|svelte|tanstack-start|elysia|turborepo] --provider postgresql --no-deploy`. Or add Prisma 7 to an existing app with `npx prisma@latest init --db`, which provisions a Prisma Postgres database; before that, check `npx @prisma/cli@latest auth whoami` and stop and ask me to run `auth login` if I am not signed in, because provisioning can open a browser.
+1. Scaffold a new app non-interactively: `npx create-prisma@stable --name my-app --template [next|hono|nuxt|astro|nest|svelte|tanstack-start|elysia|turborepo] --provider postgresql --no-deploy`. Or add Prisma 7 to an existing app with `npx prisma@latest init --db`, which provisions a Prisma Postgres database; before that, check `npx @prisma/cli@latest auth whoami` and stop and ask me to run `auth login` if I am not signed in, because provisioning can open a browser.
 2. From the project directory, define a small schema in `prisma/schema.prisma`, then run `npx prisma migrate dev --name init` and `npx prisma generate`. If migrate dev asks to reset the database, stop and ask me first.
 3. Update the seed and app code to query the schema, and verify locally with the dev script.
 4. Deploy with Prisma Compute: check `npx @prisma/cli@latest auth whoami` first. If I am not signed in, stop and ask me to run `npx @prisma/cli@latest auth login`, because that step opens a browser. Then run `npx @prisma/cli@latest app deploy --create-project my-app --env .env` so DATABASE_URL reaches the deployment, and verify the deployed URL with curl.

apps/docs/content/docs/(index)/index.mdx

@@ -34,7 +34,7 @@ full: true
 The tutorial's journey, condensed: hand the prompt to your coding agent, or run the CLI steps yourself.
 
 <GetStartedTabs cli={`# Scaffold the app
-npx create-prisma@next
+npx create-prisma@latest
 # Create a database (prints a connection string and claim URL)
 npx create-db@latest
 # Initialize and run (sample data seeds on the first query)
@@ -51,7 +51,7 @@ Create a new [framework] application with Prisma 8, seed it, and run it locally.
 
 If I have not told you which framework, stop and ask before scaffolding. Valid --template values: next, hono, nuxt, astro, nest, svelte, tanstack-start, elysia.
 
-1. Scaffold the app: `npx create-prisma@next create my-app --template [framework] --provider postgres --yes`.
+1. Scaffold the app: `npx create-prisma@latest create my-app --template [framework] --provider postgres --yes`.
 2. Get a database connection string: use the one I give you, or create a Prisma Postgres database with `npx create-db@latest` and show me the claim URL it prints. Export it as `DATABASE_URL` in the shell and write it to `.env` in the project directory; the generated scripts read the environment variable, and the deploy step reads `.env`.
 3. From the project directory, apply the starter contract: `npm run db:init`. Sample users are seeded automatically on the app's first query; there is no separate seed script.
 4. Edit the starter contract under `src/prisma/` into a small schema for my use case, then run `npm run contract:emit` and plan and apply the migration: `npx prisma@next migration plan`, then `npx prisma@next migrate --yes`. Migration planning diffs the emitted contract, so the emit step is required.
@@ -82,7 +82,7 @@ If you're using Express or another Node.js server, follow the [existing-project
 
 </SectionRow>
 
-<SectionRow title="Using Prisma 7?" description="Prisma 7 is the current generally available release of Prisma ORM and remains fully supported. Install it with `npx prisma@latest init`. It pairs with Prisma Postgres and Prisma Compute the same way. When you're ready, Prisma 8 is the upgrade path.">
+<SectionRow title="Using Prisma 7?" description="Prisma 7 is the current generally available release of Prisma ORM and remains fully supported. Scaffold it with `npx create-prisma@stable`, or add it to an existing project with `npx prisma@latest init`. It pairs with Prisma Postgres and Prisma Compute the same way. When you're ready, Prisma 8 is the upgrade path.">
 
 <IconGrid>
   <IconLink href="/getting-started" title="Prisma 7 setup paths" description="All database quickstarts, plus the agent prompt" icon={<Milestone />} />
@@ -127,7 +127,7 @@ Create a new [framework] application with Prisma 8 against my existing PostgreSQ
 
 If I have not given you a connection string, stop and ask; do not invent one. Valid --template values: next, hono, nuxt, astro, nest, svelte, tanstack-start, elysia.
 
-1. Scaffold: `npx create-prisma@next create my-app --template [framework] --provider postgres --yes`.
+1. Scaffold: `npx create-prisma@latest create my-app --template [framework] --provider postgres --yes`.
 2. Export my connection string as `DATABASE_URL` in the shell; the generated scripts read the environment variable, not `.env`. From the project directory: `npm run db:init`, then start `npm run dev` in the background and verify the sample query returns data. Sample users are seeded automatically on the app's first query; there is no separate seed script.
 3. Evolve the starter contract under `src/prisma/` into my schema, then run `npm run contract:emit`, `npx prisma@next migration plan`, and `npx prisma@next migrate --yes`.
 

apps/docs/content/docs/(index)/prisma-postgres/quickstart/prisma-next.mdx

@@ -12,7 +12,7 @@ Create a Prisma 8 app backed by Prisma Postgres.
 ## Quick start
 
 ```npm
-npx create-prisma@next
+npx create-prisma@latest
 ```
 
 Run this from a Node.js 24 or newer environment. When prompted, choose PostgreSQL.

apps/docs/content/docs/(index)/v8/full-stack-tutorial.mdx

@@ -26,7 +26,7 @@ Prefer to delegate? This is the same journey as the prompt on the [getting start
 ```text
 Create a new Hono API with Prisma 8, seed it, and deploy it to Prisma Compute.
 
-1. Scaffold: `npx create-prisma@next create my-app --template hono --provider postgres --yes`.
+1. Scaffold: `npx create-prisma@latest create my-app --template hono --provider postgres --yes`.
 2. Get a database connection string: use the one I give you, or create a Prisma Postgres database with `npx create-db@latest` and show me the claim URL it prints. Export it as `DATABASE_URL` in the shell and write it to `my-app/.env` for the deploy step; the generated scripts read the environment variable, not `.env`.
 3. In `my-app`, run `npm run db:init`. Sample users are seeded automatically on the app's first query; there is no separate seed script.
 4. Start `npm run dev` in the background (with `DATABASE_URL` exported) and verify `curl http://localhost:3000/users` returns the seeded users.
@@ -42,7 +42,7 @@ Use the installed Prisma 8 skills.
 One command creates the app and wires up Prisma 8:
 
 ```npm
-npx create-prisma@next create my-app --template hono --provider postgres
+npx create-prisma@latest create my-app --template hono --provider postgres
 ```
 
 Answer the prompts for contract authoring style and package manager, then enter the project:

apps/docs/content/docs/(index)/v8/getting-started.mdx

@@ -12,7 +12,7 @@ Start with a quickstart if you want Prisma 8 to create the app. Use the existing
 ## Start a new project
 
 ```npm
-npx create-prisma@next
+npx create-prisma@latest
 ```
 
 <Cards>
@@ -34,7 +34,7 @@ Create a new [framework] application with Prisma 8, seed it, and run it locally.
 
 If I have not told you which framework, stop and ask before scaffolding. Valid --template values: next, hono, nuxt, astro, nest, svelte, tanstack-start, elysia.
 
-1. Scaffold the app: `npx create-prisma@next create my-app --template [framework] --provider postgres --yes`.
+1. Scaffold the app: `npx create-prisma@latest create my-app --template [framework] --provider postgres --yes`.
 2. Get a database connection string: use the one I give you, or create a Prisma Postgres database with `npx create-db@latest` and show me the claim URL it prints. Export it as `DATABASE_URL` in the shell; the generated scripts read the environment variable, not `.env`.
 3. From the project directory, apply the starter contract: `npm run db:init`. Sample users are seeded automatically on the app's first query; there is no separate seed script.
 4. Edit the starter contract under `src/prisma/` into a small schema for my use case, then run `npm run contract:emit` and plan and apply the migration: `npx prisma@next migration plan`, then `npx prisma@next migrate --yes`. Migration planning diffs the emitted contract, so the emit step is required.

apps/docs/content/docs/(index)/v8/index.mdx

@@ -21,7 +21,7 @@ If you want to stay on the current generally available version of Prisma ORM, yo
 Prisma 8 is the recommended starting point for new projects.
 
 ```npm
-npx create-prisma@next
+npx create-prisma@latest
 ```
 
 Start with the setup page when you want a guided first run.
@@ -46,7 +46,7 @@ Create a new [framework] application with Prisma 8, seed it, and run it locally.
 
 If I have not told you which framework, stop and ask before scaffolding. Valid --template values: next, hono, nuxt, astro, nest, svelte, tanstack-start, elysia.
 
-1. Scaffold the app: `npx create-prisma@next create my-app --template [framework] --provider postgres --yes`.
+1. Scaffold the app: `npx create-prisma@latest create my-app --template [framework] --provider postgres --yes`.
 2. Get a database connection string: use the one I give you, or create a Prisma Postgres database with `npx create-db@latest` and show me the claim URL it prints. Export it as `DATABASE_URL` in the shell and write it to `.env` in the project directory; the generated scripts read the environment variable, and the deploy step reads `.env`.
 3. From the project directory, apply the starter contract: `npm run db:init`. Sample users are seeded automatically on the app's first query; there is no separate seed script.
 4. Edit the starter contract under `src/prisma/` into a small schema for my use case, then run `npm run contract:emit` and plan and apply the migration: `npx prisma@next migration plan`, then `npx prisma@next migrate --yes`. Migration planning diffs the emitted contract, so the emit step is required.

apps/docs/content/docs/(index)/v8/prisma-postgres/from-the-cli.mdx

@@ -12,7 +12,7 @@ Use the CLI when you want Prisma 8 and Prisma Postgres set up without leaving th
 ## Start a new app
 
 ```npm
-npx create-prisma@next
+npx create-prisma@latest
 ```
 
 Choose PostgreSQL when prompted. Setup adds `prisma-next.md`, installs project-level Prisma 8 skills for your coding agent, and writes the generated scripts used below.