docs: promote Prisma ORM 8 and version Prisma 7 content - #8171
Merged
Conversation
Prisma 8 becomes the default docs version: the orm/v8, (index)/v8, cli/v8, and guides/v8 trees move to their unversioned paths and the previous Prisma 7 content moves to orm/v7, (index)/v7, cli/v7, and guides/v7. Prisma 8 commands use prisma@latest, Prisma 7 content pins prisma and @prisma/client to 7.9.1 and scaffolds with create prisma@stable. Adds the DR-8687 cutover redirects, rewrites legacy vercel.json destinations to final pages, and updates blog and site links. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QwZ5uHUb52mVjtZnkcCXDq
Contributor
|
Important Review skippedToo many files! This PR contains 667 files, which is 517 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to Pro+ to raise the limit. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (667)
You can disable this status message by setting the Comment |
Contributor
🍈 Lychee Link Check Report5244 links: ✅ All links are working!Full Statistics Table
|
…ections Adds /prisma-orm/create-prisma from the current create-prisma README and CLI help, points the old create-prisma URLs at it, redirects /management-api/* and /compute/cli-reference (still linked from older posts), and fixes the dead libpg-query link that failed the Lychee check. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QwZ5uHUb52mVjtZnkcCXDq
ankur-arch
added a commit
that referenced
this pull request
Aug 25, 2026
The sidebar card drops the raster tile and becomes a brand-drawn panel: card-wash surface, always-on spectrum ring, prism rays behind the copy, full description, always-visible CTA and an icon dismiss. The 486 KB PNG and the OG-image fetch go with it. The top Prisma 8 banner lost its styling in #8171 when the Banner id changed while the CSS still targeted #prisma-next-docs. The selectors now hang off the class and carry a light surface (paper wash, ink CTA) alongside the existing dark one. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015n7scJPoiTqRkSrfbRffmS
ankur-arch
added a commit
that referenced
this pull request
Aug 25, 2026
…#8181) * docs: point sidebar banner at the software factory post and pin Prisma 7 to 7.10.0 The docs sidebar banner now links to Søren's launch post, Building the Stack for the Next Million Products, using the post's meta image as the tile. All Prisma 7 install and CLI pins move from 7.9.1 to 7.10.0, the last Prisma 7 release. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014sJtgWyY2MUoS1aGibxQYi * docs: brand the sidebar and top banners for light and dark The sidebar card drops the raster tile and becomes a brand-drawn panel: card-wash surface, always-on spectrum ring, prism rays behind the copy, full description, always-visible CTA and an icon dismiss. The 486 KB PNG and the OG-image fetch go with it. The top Prisma 8 banner lost its styling in #8171 when the Banner id changed while the CSS still targeted #prisma-next-docs. The selectors now hang off the class and carry a light surface (paper wash, ink CTA) alongside the existing dark one. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015n7scJPoiTqRkSrfbRffmS * docs: hold the software factory post until launch, lift the dismiss button out of the banner link The post and its assets come back in a follow-up with the launch date. The sidebar slide returns to the Prisma 8 announcement meanwhile. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013LtZjpkr83WYb47gsFYyhE --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prisma ORM 8 is now the default docs version, and the Prisma 7 docs are preserved as a versioned set. The
/orm/v8,/v8,/cli/v8, and/guides/v8trees now serve at their unversioned paths, the previous default content moved to/orm/v7,/v7,/cli/v7, and/guides/v7, and every reference across docs, site, and blog was reclassified as Prisma 8, Prisma 7, or unrelated and updated accordingly.What changed
Prisma 8 is the default (DR-8687 cutover)
The four versioned Prisma 8 trees were promoted in place, so the URLs users already know keep working with Prisma 8 content:
orm/v8/*is noworm/*(the ORM overview, data modeling, contract authoring, fundamentals, migrations, middleware, extensions, reference).(index)/v8/*is now the getting-started funnel:/getting-started,/prisma-orm(the Prisma 8 introduction),/prisma-orm/quickstart/{postgresql,mongodb},/prisma-orm/add-to-existing-project/*, and/prisma-postgres/{quickstart/prisma-orm,from-the-cli,import-*}.cli/v8/*is nowcli/*(the unified CLI).guides/v8/*is nowguides/*for the converted framework, runtime, and upgrade guides; unconverted Prisma 7 guides keep their URLs.The version model in
src/lib/version.tsnow treats Prisma 8 as Latest and Prisma 7 asv7. The sidebar tree, version switcher, sitemap priorities, llms sections (orm.txtis Prisma 8, neworm-v7.txt), the site banner, the error-reference generator and its two workflows, the Playwright anchor test, cspell, and the docs-writer skill notes all follow. The getting-started switcher is back on (Latest / v7) now that Prisma 7 is a separate tree.Release Candidate language is gone from current content. The
badge: release-candidatefrontmatter, the "Prisma 8 Release Candidate is available" callouts, the "v8 (RC)" labels, and "Prisma 7 is the current generally available release" statements were replaced with one message: Prisma 8 is the current release, Prisma 7 remains fully supported at/orm/v7. Historical validation facts (for example "validated againstprisma@8.0.0-rc.6") stay.Prisma 7 is self-contained
Every Prisma 7 install and scaffold command now resolves to Prisma 7. In the
v7trees, the unconverted Prisma 7 guides, and the Prisma 7 snippets in Postgres, Studio, and AI pages: dependencies are pinned toprisma@7.9.1 @prisma/client@7.9.1(pnpm, yarn, bun, and deno forms included), pre-install CLI commands usenpx prisma@7.9.1 init, and scaffolding usesnpm create prisma@stable. Commands that run after the pinned install (npx prisma migrate dev,npx prisma generate) resolve to the local binary and stay as they are. Internal links inside the Prisma 7 trees point at/orm/v7,/v7,/cli/v7, and/guides/v7pages, so a Prisma 7 reader never lands in a Prisma 8 flow by accident.create-prisma has a reference page again
/prisma-orm/create-prismadocuments the scaffolder from the current README and--helpoutput ofcreate-prisma@0.9.3: the four package-manager invocations, the deploy prompt and--workspace, every flag (--template,--provider,--authoring,--package-manager,--deploy/--no-deploy,--yes,--force,--verbose), the nine templates, the Deno path, and telemetry opt-out. It is linked from/getting-startedand/prisma-orm, and the old/v8/create-prisma,/next/create-prisma, and/orm/v8/create-prismaURLs redirect to it.Prisma 8 commands use
@latestEvery actionable
prisma@nextbecameprisma@latest: 72 docs pages, 12 blog posts (including the RC1 and Prisma Next launch posts, the migrations series, the pgvector demo runner), the site skills file, and the agent prompts. Current scaffolding staysnpm create prisma@latest;@stableis used only for Prisma 7 scaffolds.Site-wide and blog-wide audit
The blog archive and the marketing site were audited command by command. Prisma 7-era posts got pinned installs, the fifteen evergreen "Looking ahead: Prisma 8 is a Release Candidate, Prisma 7 stays the production choice" callouts were rewritten, the
introducing-create-prismahero (alt text and SVG) now says@stablelike the post body, the homepage FAQ no longer calls Prisma 8 a release candidate, and the footer/orm/nextlink points at/orm. Docs links in blog posts, site data, changelog entries, andpackages/uiwere rewritten to their final destinations.Redirects preserve every inbound link
next.config.mjsnow carries the live cutover map (the previously staged, commented block, with destinations updated to the promoted paths). Prisma 7 pages with a Prisma 8 equivalent redirect to it (the DR-8681, DR-8680, DR-8679, and migrations maps); everything else redirects page-to-page to its/v7twin (per-folder wildcards forprisma-client,prisma-schema,prisma-migrate,core-concepts,more, the classic CLI folders, and explicit rules for the reference pages and the database-specific quickstarts)./v8,/next,/orm/v8,/orm/next,/cli/v8,/guides/v8,/llms/v8.txt, and/prisma-postgres/quickstart/prisma-nextredirect to the unversioned pages. The 692 legacyvercel.jsonredirects that pointed at moved pages were rewritten to their final destinations so nothing chains.Validation
pnpm --filter docs types:check,pnpm --filter blog types:check,pnpm --filter site types:check: pass.pnpm --filter docs lint:links: 681 files, 0 errors.pnpm --filter blog lint:links: 0 errors.pnpm --filter docs lint:spellcheck: 820 files, 0 issues.pnpm --filter docs lint:agent-ready: 0 failures, 0 warnings.pnpm --filter docs audit:redirects:strict: 1297 redirects against 682 routes, 0 missing destinations (7 "broad" warnings are the DR-8679data-modelingmappings).pnpm --filter docs build: production build succeeds.www.prisma.io/docs/*URLs) and every Prisma 7 page (207) was requested against the local production build: all Prisma 7 pages return 200, and every blog/site link resolves through either the app or avercel.jsonredirect except pre-existing 404s in 2022 to 2024 posts (/data-platform/data-proxy,/pulse/*, oldsetup-prisma/*slugs) that are also 404 on production today. Three renamed sections still linked from older posts (/management-api/*,/compute/cli-reference) got redirects to/rest-api/*and/cli.pganalyze/libpg-query-nodein the pgfence guide, nowlaunchql/libpg-query-node.npx @prisma/cli@latest auth login,npx @prisma/cli@latest app deploy) was validated against@prisma/cli@latest(3.0.0-beta.30), which still shipsauthandapp deploy; those commands stay.next start: 91 of 92 checks pass (19 Prisma 8 default routes, 21 Prisma 7 versioned routes, 20 v8/next redirects, 24 cutover redirects, legacy routes, and every redirect target resolving in one hop). The one miss is/orm/v7/more, a folder without an index page;/orm/morewas already a 404.oxfmtandoxlinton the changed source files (no repo-widepnpm check, which reformats unrelated files).Assumption
This PR is written for the Prisma 8 release moment:
prisma@lateston npm is treated as Prisma 8 throughout the docs even though the tag still points at 7.9.1 at the time of writing. Nothing in the docs usesprisma@next; use@nextonly when testing the commands locally before the tag moves.Intentionally unchanged
guides/upgrade-prisma-orm/*("validated againstprisma@8.0.0-rc.6") stays as context; only actionable commands and links changed.npx @prisma/cli@nextincompute/object-storage.mdxtargets the separate@prisma/clibeta package, not Prisma 8; left as is, flagged for the Compute owner./orm,/orm/reference/error-reference,/cli,/cli/init,/getting-started, the two shared quickstarts, and the converted framework guides). The staged plan also listed redirects from/guides/frameworks/*to/guides/v7/*; those were not added because they would have redirected away from the promoted Prisma 8 guides./orm/latest/*keeps its existing wildcard to/orm/*; a legacy/orm/latest/prisma-clientlink therefore takes two hops (to/orm/prisma-client, then to the cutover target). Every other redirect resolves in one hop./orm/v6) and explicitly older-version blog posts keep their own version pins.public/img/orm/v8/*static asset paths are unchanged (assets, not routes).apps/eclipsedesign-system demo snippets (npm install prisma,npx prisma init) are component examples, not user-facing instructions.Follow-ups
apps/site/src/lib/agent-skills.tsandai/prompts/*describe the schema.prisma workflow; they are pinned to 7.9.1 here and could be rewritten for Prisma 8.compute/object-storage.mdx@prisma/cli@next(see above).prisma bootstrap(2026-04-07) is pinned to 7.9.1 on the assumption it is a 7.x command.