Skip to content

TML-2503: add examples/supabase/.env.example for the acceptance lane#996

Merged
wmadden-electric merged 3 commits into
mainfrom
worktree/supabase-env-example-14a097
Jul 17, 2026
Merged

TML-2503: add examples/supabase/.env.example for the acceptance lane#996
wmadden-electric merged 3 commits into
mainfrom
worktree/supabase-env-example-14a097

Conversation

@wmadden-electric

@wmadden-electric wmadden-electric commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Linked issue

Refs TML-2503. Follow-up to the Slice E close-out (#985) and the project-workspace deletion (#990).

At a glance

# examples/supabase/.env.example
# Direct connection to your Supabase Postgres (service_role-capable).
# For the local dev stack, use the Postgres connection string from
# `supabase status` (port 54322 by default).
DATABASE_URL=postgres://postgres:postgres@localhost:54322/postgres

# The project's JWT secret (Settings → API → JWT Secret on hosted projects;
# `supabase status` → `JWT secret` for local dev). Used to sign HS256 JWTs
# exactly as GoTrue issues them.
SUPABASE_JWT_SECRET=your-supabase-jwt-secret

Before this PR, examples/supabase had no .env.example — the two env vars its real-Supabase acceptance lane needs were documented only in prose in the README.

Decision

Add examples/supabase/.env.example documenting the two env vars that enable the real-Supabase acceptance test, with comments matching the README's "Running the tests" section and pointing at supabase status for local-dev secrets.

Reviewer notes

Testing performed

  • Docs-only change (one untracked-file addition); verified git check-ignore does not exclude the file and that the wording matches examples/supabase/README.md § "Running the tests".

Skill update

n/a — doc-only addition; no user-facing surface change (the env vars were already documented in the example's README).

Checklist

  • All commits are signed off (git commit -s) per the DCO.
  • I read CONTRIBUTING.md and the change is scoped to one logical concern.
  • Tests are updated — n/a, doc-only change with no behavioural delta.
  • The PR title is in TML-NNNN: <sentence-case title> form.
  • The Skill update section above is filled in.

Summary by CodeRabbit

  • Documentation
    • Added an example environment configuration for local Supabase development.
    • Documented the required database connection (DATABASE_URL) and optional JWT secret (SUPABASE_JWT_SECRET) settings.
    • Clarified when real Supabase acceptance tests will run (only when the required variables are set).

@wmadden-electric
wmadden-electric requested a review from a team as a code owner July 16, 2026 12:43
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@wmadden-electric, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 12 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 6a70786d-55f0-4957-9995-f58282ce0ecb

📥 Commits

Reviewing files that changed from the base of the PR and between d08c295 and 47f38f1.

📒 Files selected for processing (2)
  • examples/supabase/.env.example
  • skills/upgrade/prisma-next-upgrade/upgrades/0.15-to-0.16/instructions.md
📝 Walkthrough

Walkthrough

Adds an .env.example template for local Supabase development, defining the local database URL and JWT secret placeholder, and documenting that both variables enable real-Supabase acceptance tests.

Changes

Supabase configuration

Layer / File(s) Summary
Local Supabase environment template
examples/supabase/.env.example
Documents local Supabase setup and defines DATABASE_URL and SUPABASE_JWT_SECRET, including acceptance-test gating notes.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: adding the Supabase example env file for the acceptance lane.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch worktree/supabase-env-example-14a097

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Jul 16, 2026

Copy link
Copy Markdown

size-limit report 📦

Path Size
postgres / no-emit 158.98 KB (0%)
postgres / emit 132.5 KB (0%)
mongo / no-emit 98.71 KB (0%)
mongo / emit 89.43 KB (0%)
cf-worker / no-emit 185.14 KB (0%)
cf-worker / emit 155.9 KB (0%)

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@examples/supabase/.env.example`:
- Around line 9-12: Change the SUPABASE_JWT_SECRET placeholder in the
environment template to an unset or empty value so copying the template keeps
the real-Supabase acceptance test skipped until a valid secret is provided;
preserve the existing explanatory comments and other configuration.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: c9feaf86-9ac9-4a79-aefa-79a1d39a4e45

📥 Commits

Reviewing files that changed from the base of the PR and between cfea1a2 and a75d855.

📒 Files selected for processing (1)
  • examples/supabase/.env.example

Comment thread examples/supabase/.env.example Outdated
@pkg-pr-new

pkg-pr-new Bot commented Jul 16, 2026

Copy link
Copy Markdown

Open in StackBlitz

@prisma-next/extension-author-tools

npm i https://pkg.pr.new/@prisma-next/extension-author-tools@996

@prisma-next/mongo-runtime

npm i https://pkg.pr.new/@prisma-next/mongo-runtime@996

@prisma-next/family-mongo

npm i https://pkg.pr.new/@prisma-next/family-mongo@996

@prisma-next/sql-runtime

npm i https://pkg.pr.new/@prisma-next/sql-runtime@996

@prisma-next/family-sql

npm i https://pkg.pr.new/@prisma-next/family-sql@996

@prisma-next/extension-arktype-json

npm i https://pkg.pr.new/@prisma-next/extension-arktype-json@996

@prisma-next/middleware-cache

npm i https://pkg.pr.new/@prisma-next/middleware-cache@996

@prisma-next/mongo

npm i https://pkg.pr.new/@prisma-next/mongo@996

@prisma-next/extension-paradedb

npm i https://pkg.pr.new/@prisma-next/extension-paradedb@996

@prisma-next/extension-pgvector

npm i https://pkg.pr.new/@prisma-next/extension-pgvector@996

@prisma-next/extension-postgis

npm i https://pkg.pr.new/@prisma-next/extension-postgis@996

@prisma-next/postgres

npm i https://pkg.pr.new/@prisma-next/postgres@996

@prisma-next/sql-orm-client

npm i https://pkg.pr.new/@prisma-next/sql-orm-client@996

@prisma-next/sqlite

npm i https://pkg.pr.new/@prisma-next/sqlite@996

@prisma-next/extension-supabase

npm i https://pkg.pr.new/@prisma-next/extension-supabase@996

@prisma-next/target-mongo

npm i https://pkg.pr.new/@prisma-next/target-mongo@996

@prisma-next/adapter-mongo

npm i https://pkg.pr.new/@prisma-next/adapter-mongo@996

@prisma-next/driver-mongo

npm i https://pkg.pr.new/@prisma-next/driver-mongo@996

@prisma-next/contract

npm i https://pkg.pr.new/@prisma-next/contract@996

@prisma-next/utils

npm i https://pkg.pr.new/@prisma-next/utils@996

@prisma-next/config

npm i https://pkg.pr.new/@prisma-next/config@996

@prisma-next/errors

npm i https://pkg.pr.new/@prisma-next/errors@996

@prisma-next/framework-components

npm i https://pkg.pr.new/@prisma-next/framework-components@996

@prisma-next/operations

npm i https://pkg.pr.new/@prisma-next/operations@996

@prisma-next/ts-render

npm i https://pkg.pr.new/@prisma-next/ts-render@996

@prisma-next/contract-authoring

npm i https://pkg.pr.new/@prisma-next/contract-authoring@996

@prisma-next/ids

npm i https://pkg.pr.new/@prisma-next/ids@996

@prisma-next/psl-parser

npm i https://pkg.pr.new/@prisma-next/psl-parser@996

@prisma-next/psl-printer

npm i https://pkg.pr.new/@prisma-next/psl-printer@996

@prisma-next/cli

npm i https://pkg.pr.new/@prisma-next/cli@996

@prisma-next/cli-telemetry

npm i https://pkg.pr.new/@prisma-next/cli-telemetry@996

@prisma-next/config-loader

npm i https://pkg.pr.new/@prisma-next/config-loader@996

@prisma-next/emitter

npm i https://pkg.pr.new/@prisma-next/emitter@996

@prisma-next/language-server

npm i https://pkg.pr.new/@prisma-next/language-server@996

@prisma-next/migration-tools

npm i https://pkg.pr.new/@prisma-next/migration-tools@996

prisma-next

npm i https://pkg.pr.new/prisma-next@996

@prisma-next/vite-plugin-contract-emit

npm i https://pkg.pr.new/@prisma-next/vite-plugin-contract-emit@996

@prisma-next/mongo-codec

npm i https://pkg.pr.new/@prisma-next/mongo-codec@996

@prisma-next/mongo-contract

npm i https://pkg.pr.new/@prisma-next/mongo-contract@996

@prisma-next/mongo-value

npm i https://pkg.pr.new/@prisma-next/mongo-value@996

@prisma-next/mongo-contract-psl

npm i https://pkg.pr.new/@prisma-next/mongo-contract-psl@996

@prisma-next/mongo-contract-ts

npm i https://pkg.pr.new/@prisma-next/mongo-contract-ts@996

@prisma-next/mongo-emitter

npm i https://pkg.pr.new/@prisma-next/mongo-emitter@996

@prisma-next/mongo-schema-ir

npm i https://pkg.pr.new/@prisma-next/mongo-schema-ir@996

@prisma-next/mongo-query-ast

npm i https://pkg.pr.new/@prisma-next/mongo-query-ast@996

@prisma-next/mongo-orm

npm i https://pkg.pr.new/@prisma-next/mongo-orm@996

@prisma-next/mongo-query-builder

npm i https://pkg.pr.new/@prisma-next/mongo-query-builder@996

@prisma-next/mongo-lowering

npm i https://pkg.pr.new/@prisma-next/mongo-lowering@996

@prisma-next/mongo-wire

npm i https://pkg.pr.new/@prisma-next/mongo-wire@996

@prisma-next/sql-contract

npm i https://pkg.pr.new/@prisma-next/sql-contract@996

@prisma-next/sql-errors

npm i https://pkg.pr.new/@prisma-next/sql-errors@996

@prisma-next/sql-operations

npm i https://pkg.pr.new/@prisma-next/sql-operations@996

@prisma-next/sql-schema-ir

npm i https://pkg.pr.new/@prisma-next/sql-schema-ir@996

@prisma-next/sql-contract-psl

npm i https://pkg.pr.new/@prisma-next/sql-contract-psl@996

@prisma-next/sql-contract-ts

npm i https://pkg.pr.new/@prisma-next/sql-contract-ts@996

@prisma-next/sql-contract-emitter

npm i https://pkg.pr.new/@prisma-next/sql-contract-emitter@996

@prisma-next/sql-lane-query-builder

npm i https://pkg.pr.new/@prisma-next/sql-lane-query-builder@996

@prisma-next/sql-relational-core

npm i https://pkg.pr.new/@prisma-next/sql-relational-core@996

@prisma-next/sql-builder

npm i https://pkg.pr.new/@prisma-next/sql-builder@996

@prisma-next/target-postgres

npm i https://pkg.pr.new/@prisma-next/target-postgres@996

@prisma-next/target-sqlite

npm i https://pkg.pr.new/@prisma-next/target-sqlite@996

@prisma-next/adapter-postgres

npm i https://pkg.pr.new/@prisma-next/adapter-postgres@996

@prisma-next/adapter-sqlite

npm i https://pkg.pr.new/@prisma-next/adapter-sqlite@996

@prisma-next/driver-postgres

npm i https://pkg.pr.new/@prisma-next/driver-postgres@996

@prisma-next/driver-sqlite

npm i https://pkg.pr.new/@prisma-next/driver-sqlite@996

commit: 47f38f1

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Commenting the secret out (rather than assigning an empty string) keeps
both consumers correct when the file is sourced unedited: the acceptance
suite stays skipped, and src/prisma/db.ts still falls back to fixtureJwt
via ?? — which an empty string would defeat.

Also record that nothing auto-loads .env here, so the vars must be
exported into the shell.

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
@wmadden-electric
wmadden-electric force-pushed the worktree/supabase-env-example-14a097 branch from d08c295 to 47f38f1 Compare July 17, 2026 06:34
@wmadden-electric
wmadden-electric added this pull request to the merge queue Jul 17, 2026
Merged via the queue into main with commit 5bd5902 Jul 17, 2026
21 checks passed
@wmadden-electric
wmadden-electric deleted the worktree/supabase-env-example-14a097 branch July 17, 2026 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants