Rebrand Prisma Next to Prisma 8 across docs, blog, and site - #8117
Merged
Conversation
Contributor
|
Important Review skippedToo many files! This PR contains 263 files, which is 113 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. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (33)
📒 Files selected for processing (263)
You can disable this status message by setting the Comment |
Contributor
🍈 Lychee Link Check Report1058 links: ✅ All links are working!Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎ Awaiting the start of a new Argos build… |
The early-access major version keeps its working-name identifiers but is now called Prisma 8 everywhere users read it: - All prose, frontmatter, changelog entries, and UI labels (docs version dropdown now "v8 (Early Access)"; sidebar matchers keep URL fallbacks). - Reworded ~35 now-redundant "becomes Prisma 8 at GA" sentences and the announcement post's naming section; added a one-line editor's note to the nine posts that were about Prisma Next under its working name. - Replaced 14 images carrying the old wordmark: outlined badge/headline text in the teal covers swapped for live Mona Sans text, the indigo announcement family (incl. roadmap, TS-migrations, EA meta and the docs sidebar banner) rebuilt from the announcement SVG, and metas re-rendered from their heroes. Hero-image skill logos renamed to prisma-8-*. - Fixed 27 links pointing at renamed heading anchors. Deliberately unchanged (product-owned identifiers and live URLs): create prisma@next npm dist-tags, the prisma-next CLI and config file, the @prisma-next/* npm scope, /docs/orm/next URL segments (GA cutover plan in next.config.mjs), published blog slugs, pris.ly/pn-* links, Discord #prisma-next channels, and the EA banner CSS selectors that PostHog CTA actions target. Verified: types:check (docs, blog), lint:links, lint:agent-ready, test:llm-markdown, lint:spellcheck, pnpm check, plus rendered-page and image review on dev servers. Pre-commit hook skipped (pnpm is not callable in this non-interactive shell); its check command was run manually and passed.
nurul3101
force-pushed
the
prisma-8-rebrand
branch
from
July 30, 2026 10:49
1eac8ea to
b5ec2ad
Compare
Everywhere the site describes Prisma 8's current stage now says the
Release Candidate is available instead of Early Access:
- Docs: the EA banner, the version dropdown ("v8 (RC)"), section
meta.json titles, llms.txt topics, the standard "Prisma 8 is in Early
Access" callout on nine pages, and status prose across the next tree.
- New "release-candidate" badge type (badge-types.ts drives the zod
enum, label, and color maps); the 41 Prisma 8 pages switched to it.
Other products keep the early-access badge (e.g. the Postgres
serverless driver) and the generic maturity-tier docs are untouched.
- Blog: the "Looking ahead" footers, per-post status notes, and
pris.ly/pn-ea link text; site stack page descriptions.
Kept as historical artifacts: the Early Access announcement post
(title, slug, cover, body), launch-story references to it, dated
changelog entries, the April roadmap metaDescription, and every other
product's Early Access mentions.
Verified: docs types:check, lint:links, lint:agent-ready,
test:llm-markdown, lint:spellcheck, pnpm check, and rendered-page
checks on dev servers (banner, dropdown, callouts, footers, ltree
heading). Pre-commit hook skipped; its check command was run manually
and passed.
URL rename: the /next version segment (a working-name artifact) becomes
/v8 across all four trees: /orm/next -> /orm/v8, /cli/next -> /cli/v8,
/guides/next -> /guides/v8, and the getting-started tree /next -> /v8.
Content directories moved with git mv; every internal link, url:
frontmatter field, meta.json entry, llms.txt prefix and section slug
(/docs/llms/v8.txt), sidebar matcher, badge-visibility path, and the
version key ("next" -> "v8" in version.ts, the switcher, and the
sidebar tree) updated to match. Permanent redirects cover the old URLs,
including /llms/next.txt; the commented GA cutover map now speaks v8.
Package rename (ADR 242, prisma/prisma#29864): app-facing installs and
imports move from the @prisma-next scope to the consolidated @prisma
facades. Mappings verified against the merged monorepo's converted
example apps and facade export maps, e.g.:
- @prisma-next/postgres -> @prisma/orm-postgres (one dependency)
- @prisma-next/sql-runtime -> @prisma/orm-postgres/family-runtime
- @prisma-next/sql-orm-client -> @prisma/orm-postgres/orm-client
- @prisma-next/mongo-query-builder -> @prisma/orm-mongo/query-builder
- @prisma-next/target-postgres/migration -> @prisma/orm-postgres/target/migration
- @prisma-next/middleware-cache -> @prisma/orm-extension-middleware-cache
- extensions -> @prisma/orm-extension-{pgvector,postgis,paradedb,supabase,arktype-json}
Extension source links now point at prisma/prisma's
packages/3-extensions (verified to exist there).
Unchanged on purpose: the prisma-next bin and prisma-next.config.ts
(the Slack announcement defers that rename to a pre-RC roadmap task),
npm create prisma@next, blog slugs, pris.ly short links, and
prisma/prisma-next repo links whose targets have no equivalent in the
monorepo (retail-store example, planning docs).
Verified: docs types:check, lint:links (0 errors across the moved
trees), lint:agent-ready, test:llm-markdown, lint:spellcheck, pnpm
check; rendered /orm/v8 page with v8 (RC) dropdown and collapsed
sidebar; 308 redirects confirmed for all old-URL forms. Pre-commit hook
skipped; its check command was run manually and passed.
Main's #8125 added the generated error reference under the old /orm/next path with working-name branding. Resolution: - Accepted git's relocation of error-reference.mdx into orm/v8/reference (the meta.json entry merged into the renamed path automatically). - Taught generate-error-reference.mjs the naming standard so every future sync stays compliant: v8 output path and frontmatter (Prisma 8, release-candidate badge, /orm/v8 url), "Prisma Next" -> "Prisma 8" in canonical body text, and published facade names for app-facing imports (@internal/utils/structured-error -> the facade utils/structured-error subpath; @internal/{postgres,sqlite,mongo} -> @prisma/orm-*). Internal-only testkit names are deliberately kept. - Regenerated the page from the live canonical source (256 codes) and added its new vocabulary to cspell.json. - Updated both error-reference workflows and the anchors spec to the /orm/v8 path, and the sync workflow's commit message. - Reframed the 2026-08-02 changelog note from Early Access to Release Candidate. Old /orm/next docsUrls emitted by existing builds still land correctly: the 308 redirects preserve URL fragments. Verified: docs types:check, lint:links, lint:agent-ready, test:llm-markdown, lint:spellcheck (783 files, 0 issues), pnpm check. Pre-commit hook skipped; its check command was run manually and passed.
…ied CLI Replaces prisma-next invocations with npx @prisma/cli@next across the Prisma 8 getting-started funnel, add-to-existing-project and import guides, the ORM v8 concept/migrations/contract-authoring trees, the Studio Prisma 8 page, the Deno guide, and the agent prompt blocks, applying the verified command renames (init -> orm init). Left untouched on purpose: quoted CLI output (the bundled toolchain still prints prisma-next in hints), skill names, repo and blog URLs, prisma-next.config.ts / prisma-next.md file names, and listings of scaffold-generated files, which orm init still emits in that form. The generated error reference is owned by the upstream sync.
…s, version the CLI section Compute: rewrites the section around the unified CLI's real surface (verified against @prisma/cli@next 8.0.0-rc.2): app -> service + service deployment/domain, database -> postgres, the new bucket group, and the changed deploy model, where deployments come from a git push, the Console, or Composer rather than a CLI app deploy, and promote rebuilds with production env vars. Drops the beta-only error-code tables in favor of the verified dotted-code envelope. Blog: swaps prisma-next invocations to npx @prisma/cli@next in the four posts that show runnable commands. Skills: the twelve prisma-next-* skills were consolidated upstream into one prisma-8 skill in prisma/prisma/skills; updates the skills page (install command and table) and every Prompt-your-coding-agent section to reference prisma-8. CLI versioning: the CLI section's version dropdown now lists v6, and any pre-v8 selection resolves to the classic prisma CLI tree instead of jumping to that version's ORM docs. The /prisma-compute/deploy funnel page keeps the old flow on purpose; it is being rebuilt around Composer in a parallel stream.
Rewrites /prisma-compute/deploy around the real deploy model: init + project create + git connect, then push, with service show/open and build logs for verification and promote/rollback for shipping. The create-prisma path now hands off to the GitHub connection instead of the removed app deploy loop, and the agent prompt teaches the new command set.
# Conflicts: # apps/docs/content/docs/ai/tools/skills.mdx # apps/docs/content/docs/orm/v8/reference/error-reference.mdx
The generated error reference moved to orm/v8 with the docs tree, but the cspell ignore still named the old orm/next path, so the file's generated vocabulary failed the full spellcheck run.
Member
|
@coderabbitai review |
Contributor
|
Member
|
@coderabbitai approve |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
✅ Action performedComments resolved and changes approved. |
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
3 participants
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 Next is now named Prisma 8, its stage is framed as a Release Candidate rather than Early Access, its docs live under /v8 instead of /next, and code samples use the ADR 242 package names. This PR replaces the working name everywhere users read it (docs, blog, marketing site, and the images that carried the old wordmark), then updates the status framing, URLs, and package names in follow-up commits.
Commit 1: the rename
Content and labels
apps/docs,apps/blog, andapps/site(146 MDX files).llms.txttopic titles. Sidebar version matchers accept the new labels and keep their URL fallbacks.content-write-bloganddocs-writerskill conventions, hero-image skill logo lockups renamed toprisma-8-*with tokens/README updates, CONTRIBUTING.md.Images (14 replaced)
meta.pngwas re-rendered from its hero.prisma-8.png, old file removed).Commit 2: Early Access becomes Release Candidate
Everywhere the site describes Prisma 8's current stage now says the Release Candidate is available:
llms.txttopics, the standard status callout on nine pages, and status prose across the next tree.release-candidatebadge type (badge-types.tsdrives the zod enum, label, and color maps); the 41 Prisma 8 pages switched to it. The Postgres serverless driver keeps itsearly-accessbadge and the generic feature-maturity docs are untouched.pris.ly/pn-ealink text; site stack page descriptions.Kept as historical artifacts (they describe the June Early Access launch as an event): the Early Access announcement post (title, slug, cover, body), launch-story references to it, dated changelog entries, the April roadmap metaDescription, and every other product's Early Access mentions (Prisma Postgres EA, Optimize EA, legal terms, maturity-tier docs).
Commit 3: /next becomes /v8, packages become @prisma/orm-*
URL rename. The
/nextversion segment was a working-name artifact; all four trees moved withgit mv:/docs/orm/next->/docs/orm/v8,/docs/cli/next->/docs/cli/v8,/docs/guides/next->/docs/guides/v8, and the getting-started tree/docs/next->/docs/v8. Every internal link,url:frontmatter field, meta.json entry, llms.txt prefix and section slug (/docs/llms/v8.txt), sidebar matcher, badge-visibility path, and the internal version key ("next" -> "v8") follow. Permanent (308) redirects cover every old URL form, including/llms/next.txt; the commented GA cutover map now speaks v8.lint:linkspasses with 0 errors across the moved trees, and the redirects were exercised on a dev server.Package rename (ADR 242, prisma/prisma#29864). App-facing installs and imports move from the
@prisma-nextscope to the consolidated@prismafacades. Every mapping was verified against the merged monorepo's converted example apps and the facade export maps; highlights:@prisma-next/postgres(+ a dozen siblings)@prisma/orm-postgres(one dependency)@prisma-next/postgres/{runtime,config,migration}@prisma/orm-postgres/{runtime,config,migration}@prisma-next/sql-runtime@prisma/orm-postgres/family-runtime@prisma-next/sql-orm-client@prisma/orm-postgres/orm-client@prisma-next/sql-relational-core/*@prisma/orm-postgres/relational-core/*@prisma-next/mongo-query-builder,mongo-query-ast/*@prisma/orm-mongo/query-builder,query-ast/*@prisma-next/target-{postgres,mongo}/*@prisma/orm-{postgres,mongo}/target/*@prisma-next/middleware-cache@prisma/orm-extension-middleware-cache@prisma-next/extension-*@prisma/orm-extension-*Extension source links now point at
prisma/prisma'spackages/3-extensions(verified to exist). Per the announcement, theprisma-nextbin,prisma-next.config.ts, andnpm create prisma@nextare explicitly deferred and stay as-is.Deliberately unchanged
Product-owned identifiers and live URLs keep the working name until their owners change them:
npm create prisma@next/prisma@nextdist-tags, theprisma-nextCLI binary,prisma-next.config.ts, scaffolded skill names (prisma-next-queries, ...), andprisma/prisma-nextGitHub repo links whose targets have no monorepo equivalent (retail-store example, planning docs, star CTAs)./blog/prisma-next-*),pris.ly/pn-*short links, Discord#prisma-nextchannel names, UTM campaign tags.prisma-next-banner*): PostHog CTA click actions target these selectors.Verification
types:checkgreen for docs and blog (site andpackages/eclipsehave pre-existing failures unrelated to this PR, reproduced on a clean tree).lint:links,lint:agent-ready,test:llm-markdown,lint:spellcheck(778 files, 0 issues), andpnpm checkall pass after both commits.Possible follow-ups (not in this PR)
prisma-next-*blog slugs with 301s (kept for SEO/link continuity).pris.ly/p8-*aliases; product-side renames (CLI, npm scope, Discord) when the ORM repo rebrands.feat/prisma-next-referencebranch will need the same rename and framing when it lands.