docs(skills): drop the RLS-testing guidance — testing a Supabase project is not our surface - #1002
Conversation
… is not our surface The Supabase skill taught pgTAP syntax and a supabase test db workflow; the upgrade recipes and extension README echoed it. None of it is Prisma Next product surface, nothing in the repo runs it, and the endorsement traces to a forwarded suggestion, not a product decision. The skill now covers only what is ours: policy authoring, migrations, role binding, JWT config, connections, grants. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughSupabase documentation and 0.15→0.16 upgrade instructions remove Supabase CLI-based RLS testing guidance, including local-stack and pgTAP examples. The Supabase reference-files description is also revised. ChangesSupabase testing documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
size-limit report 📦
|
@prisma-next/extension-author-tools
@prisma-next/mongo-runtime
@prisma-next/family-mongo
@prisma-next/sql-runtime
@prisma-next/family-sql
@prisma-next/extension-arktype-json
@prisma-next/middleware-cache
@prisma-next/mongo
@prisma-next/extension-paradedb
@prisma-next/extension-pgvector
@prisma-next/extension-postgis
@prisma-next/postgres
@prisma-next/sql-orm-client
@prisma-next/sqlite
@prisma-next/extension-supabase
@prisma-next/target-mongo
@prisma-next/adapter-mongo
@prisma-next/driver-mongo
@prisma-next/contract
@prisma-next/utils
@prisma-next/config
@prisma-next/errors
@prisma-next/framework-components
@prisma-next/operations
@prisma-next/ts-render
@prisma-next/contract-authoring
@prisma-next/ids
@prisma-next/psl-parser
@prisma-next/psl-printer
@prisma-next/cli
@prisma-next/cli-telemetry
@prisma-next/config-loader
@prisma-next/emitter
@prisma-next/language-server
@prisma-next/migration-tools
prisma-next
@prisma-next/vite-plugin-contract-emit
@prisma-next/mongo-codec
@prisma-next/mongo-contract
@prisma-next/mongo-value
@prisma-next/mongo-contract-psl
@prisma-next/mongo-contract-ts
@prisma-next/mongo-emitter
@prisma-next/mongo-schema-ir
@prisma-next/mongo-query-ast
@prisma-next/mongo-orm
@prisma-next/mongo-query-builder
@prisma-next/mongo-lowering
@prisma-next/mongo-wire
@prisma-next/sql-contract
@prisma-next/sql-errors
@prisma-next/sql-operations
@prisma-next/sql-schema-ir
@prisma-next/sql-contract-psl
@prisma-next/sql-contract-ts
@prisma-next/sql-contract-emitter
@prisma-next/sql-lane-query-builder
@prisma-next/sql-relational-core
@prisma-next/sql-builder
@prisma-next/target-postgres
@prisma-next/target-sqlite
@prisma-next/adapter-postgres
@prisma-next/adapter-sqlite
@prisma-next/driver-postgres
@prisma-next/driver-sqlite
commit: |
Decision
How users test their Supabase project is Supabase's concern, not Prisma Next's. The
prisma-next-supabaseskill had grown a full "Testing your RLS policies" workflow — a pgTAP tutorial with a worked SQL example — and the 0.15→0.16 upgrade recipes and extension README echoed the samesupabase test dbendorsement. None of that is our product surface, nothing in this repo executes any of it (documented-but-unexecuted guidance is exactly the defect class TML-3035 was about), and the endorsement traces back to a forwarded external-agent suggestion that was mislabeled as an operator decision during shaping — not to anyone deciding "our skills teach pgTAP."What changed
skills/prisma-next-supabase/SKILL.md— the "Workflow — Testing your RLS policies" section is deleted. The skill now covers only what is ours: policy authoring, migrations, role binding, JWT config, connections, and the one grant our admin-read feature needs. Also fixes a stale line from TML-3035: a first Supabase project works first-try — RLS migrations, verify, migrate, JWKS, grants #997: the example ships acceptance tests only (the hermetic suites moved into the extension package).bootstrapSupabaseShimremoval entries keep their real remediation (delete the dead import; keep hermetic helpers package-internal) and drop the trailing "usesupabase test db(pgTAP)" advice.packages/3-extensions/supabase/README.md— drops the closing "user-facing RLS testing is Supabase's own tooling" sentence.Repo-wide sweep confirms zero remaining pgTAP /
supabase test dbmentions. Prose only — no code paths touched;pnpm lint:skillsgreen.🤖 Generated with Claude Code
Summary by CodeRabbit