Prisma 8 + Supabase: blog post and extension docs guide - #8131
Draft
ankur-arch wants to merge 1 commit into
Draft
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 Report3 links: ✅ All links are working!Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
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