Repository navigation
fix(declarative-e2e): create the stack with start --runtime after CLI removed stack prepare - #552
Conversation
… removed stack prepare supabase/cli#7195 replaced `stack prepare` with `stack install`, which only downloads artifacts. Create the database-only stack with `start --runtime <rt> --exclude <all other capabilities>` instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
commit: |
Supabase CLI
developremovedsupabase stack preparein supabase/cli#7195 (replaced bystack install, which only downloads artifacts and creates no stack). That broke every stack-backend scenario at setup: https://github.com/supabase/pg-toolbelt/actions/runs/39410763678/job/118587669546 (stack destroy --yesthen failed because no stack existed).The harness now creates the database-only stack with
supabase start --runtime <runtime> --exclude rest,auth,realtime,storage,functions,studio,mail,analytics,pooler, thendb startas before. Legacy backend untouched.Verified: stack smoke set passes locally against CLI develop @ 617be96 (2 pass, 0 fail, no teardown failures). Private package, no changeset.
🤖 Generated with Claude Code