refactor: adopt Prisma ORM composer API names; point repo links at prisma/orm - #8196
Conversation
…isma/orm Two mechanical sweeps: - Composer docs (composer/databases.mdx, composer/core-concepts.mdx, full-stack-tutorial.mdx) adopt composer 0.15.0's renamed API (prisma/composer#265): the /prisma-next entrypoint becomes /orm, pnPostgres() becomes postgres(), pnContract() becomes dataContract(), and the unmanaged factory becomes rawPostgres(). - Every github.com/prisma/prisma link now points at github.com/prisma/orm (the repo was renamed; issue/PR numbers are preserved by the rename, so deep links stay valid). prisma/prisma-next deep links in historical blog posts are left alone: that repo's PR numbers and paths do not map onto prisma/orm, so rewriting them would break the links. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
Important Review skippedToo many files! This PR contains 220 files, which is 70 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 a paid plan 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 Plus Run ID: 📒 Files selected for processing (220)
You can disable this status message by setting the Comment |
🍈 Lychee Link Check Report2790 links: ✅ All links are working!Full Statistics Table
|
prisma/composer#265 renamed examples/pn-widgets to examples/orm-demo; the link checker caught the resulting 404. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
pris.ly/multi-provider-deprecation redirects to github.com/prisma/orm/issues/3834, which now returns 404 after the repo rename; the issue lives at github.com/prisma/orm/issues/3834. Keep the quoted CLI error text as-is and point only the link target at the live URL. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
The snippet calls rawPostgres() but imported postgres, which the package root does not export (it lives under /orm). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012df5n5vC6MrnpMQzmVmNed
Follow-on to prisma/composer#265 (retiring the pre-release "Prisma Next" naming) and the
prisma/prisma→prisma/ormrepo rename.Composer docs — new API names
composer/databases.mdx,composer/core-concepts.mdx, andfull-stack-tutorial.mdxnow show composer 0.16.0's API: the/prisma-nextentrypoint is/orm,pnPostgres()ispostgres()(the ORM-managed database is the default name),pnContract()isdataContract(), and the unmanaged bring-your-own-client factory israwPostgres().These pages describe the API of composer 0.16.0, which is published (npm
latestand GitHub release v0.16.0 as of 2026-08-26). The names above were checked against the@prisma/composer-prisma-cloud@0.16.0type declarations:postgres()anddataContract()under/orm,rawPostgres()at the package root.Repo links
Every
github.com/prisma/prismalink (docs, blog, changelog, vercel.json redirect destinations, security.txt) now points atgithub.com/prisma/orm. GitHub's rename redirect keeps issue/PR numbers valid, so deep links survive the rewrite.Deliberately unchanged:
github.com/prisma/prisma-nextdeep links in historical blog posts — that repo's PR numbers and blob paths do not map ontoprisma/orm, so rewriting would break them./studio/prisma-nextURL slugs, image paths, and CSS class names — renaming those needs redirects and is a docs-team call, not part of this sweep.// use prisma-nextPSL pragma andprisma-next.mdmentions — still what the current upstream toolchain emits.🤖 Generated with Claude Code