Repository navigation
docs: redirect /guides/upgrade-prisma-orm/v8 to the Prisma 8 upgrade hub - #8889
ankur-arch wants to merge 1 commit into
Conversation
Every major from v3 to v7 has an upgrade guide at /docs/guides/upgrade-prisma-orm/v{major}.
The Prisma 8 guide lives on the section index, so /v8 returned a 404. The Prisma ORM 7 CLI
update notice is moving to the per-major URL (prisma/orm#31110), so /v8 needs to resolve.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
✅ Gizmo reviewed 55b383e — posted 0 inline comment(s) this pass. Open findings: none Change walkthroughThis PR adds a single redirect to apps/docs/vercel.json:918: How it fits the codebase. The docs app keeps its platform-level redirect table in |
/docs/guides/upgrade-prisma-orm/v8now redirects to the Prisma 8 upgrade hub at/docs/guides/upgrade-prisma-orm. Today it returns a 404.Why
The Prisma ORM 7 CLI prints an update notice that recommends Prisma 8 and links to
https://pris.ly/d/major-version-upgrade, which lands on the Prisma 6 to 7 guide (prisma/orm#31110). The CLI fix builds the link from the major version being upgraded to, using the URL pattern the docs already follow forv3throughv7. Prisma 8 is the one major without a page at that pattern, because its guide is the section index.What changes
One redirect in
apps/docs/vercel.json. It is temporary (307), not permanent, so a dedicatedv8page can replace it later without fighting cached redirects.Validation
node scripts/audit-redirects.mjsreports the same findings asmain, with the redirect count going from 1517 to 1518.Merge order: this should be live before the CLI change ships in a 7.x release.
Summary by CodeRabbit