Prisma 8 + Supabase: blog post and extension docs guide - #8131
Draft
ankur-arch wants to merge 11 commits into
Draft
Prisma 8 + Supabase: blog post and extension docs guide#8131ankur-arch wants to merge 11 commits into
ankur-arch wants to merge 11 commits into
Conversation
Blog: prisma-8-supabase-rls-and-auth (Will + Ankur), covering RLS policies in the Prisma contract and the supabase:auth.AuthUser cross-space FK, with hero/meta cover images. Docs: orm/next/extensions/supabase guide following the docs-writer conventions. All code executed against a real hosted Supabase project and deployed to Prisma Compute; see the test evidence in the PR description. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Contributor
🍈 Lychee Link Check Report9 links: ✅ All links are working!Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
Blog: new benefit-led title, pain-first opening, schema and policy in the first third, one policy shown in full, before/after and request-flow diagrams, Compute/versions/test-report sections cut. Docs: replace unsupported 'terminal' code fence language with 'bash' (broke the Shiki-based docs build and every downstream docs check) and add the new page's SQL catalog terms plus PostgREST to cspell. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ankur-arch
commented
Aug 6, 2026
|
|
||
| The CLI builds locally, uploads, and prints a live URL. Environment values from `.env` are configured through the deploy per the config's `env` field and never land in your repository. Because enforcement lives in Postgres, the deployed app preserves the exact RLS behavior you tested locally; re-run your curl checks against the live URL to confirm. | ||
|
|
||
| ## Reading auth.users for admin work |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| ## Reading auth.users for admin work | |
| ## Reading `auth.users` for admin work |
Contributor
Author
There was a problem hiding this comment.
Add backticks for things that represent code/or a part of.
Pyramid-principle pass: RC1 framing throughout with a feedback CTA, sections renamed to reader takeaways, connected prose instead of fragments, proof section removed, limitations reframed around supported scenarios. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Restructure in the Turborepo-guide style: what-you'll-learn list, connection details collected up front, numbered steps with expected output after each command, plain-language explanations of the auth relation, @@rls, and policy blocks, and a verification step. RC1 framing replaces Early Access copy; jargon (contract space, facade, secondary root) replaced with plain terms. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Remount the code block when the snippet language changes so codehike's token transitions only run between same-language steps; the ts->sql transition locked the main thread. Shorten contract-graph comments that clipped at desktop card width. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Open with the migration-hunt pain and the schema as the answer, move generated SQL after the schema as an implementation detail, drop Prisma-history framing and negative migration language, reframe the contrast graph as Supabase today vs Prisma 8, and weave the AI-agent angle into the story. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Restructure the opening per the DevRel storytelling pass: show the policy-next-to-model payoff first, then walk through today's migration hunt, then unpack the schema one idea at a time. 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.
TL;DR
Adds the Prisma 8 + Supabase launch content: the blog post ("Your Supabase RLS policies and auth.users, in your Prisma contract", authors Will + Ankur, with cover images) and the
orm/next/extensions/supabasedocs guide. Every command and code block was executed against a real hosted Supabase project and deployed to Prisma Compute before being written down. Draft until launch coordination (publish date + public example repo link).What's in the PR
apps/blog/content/blog/prisma-8-supabase-rls-and-auth/index.mdx+hero.svg/meta.png(Eclipse house style, official Prisma + Supabase logos)apps/docs/content/docs/orm/next/extensions/supabase.mdx+ registration in the extensionsmeta.jsonEvidence behind the content
@@rls+ 4 policies,supabase:auth.AuthUserFK, Hono API) built withprisma-next@0.17.0,@prisma/orm-postgres@0.17.0,@prisma/orm-extension-supabase@0.17.0db verifyfails on current hosted projects due to extension storage-contract drift; workaround--marker-only)Conventions
prisma@nextdoes not exist)docs-writerskill (numbered steps, verify blocks, troubleshooting, agent prompt); one flagged deviation: the skill reference still says "Prisma Next", overridden by the Prisma 8 naming decisionBefore merge
TODO before publishcomment with the public example repo link🤖 Generated with Claude Code