feat(cli): select local stack commands by project backend - #6516
Closed
jgoux wants to merge 3 commits into
Closed
Conversation
Contributor
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@629364a73726145605eec64352439464af2e777dPreview package for commit |
jgoux
force-pushed
the
feat/stack-command-routing
branch
from
September 8, 2026 12:32
2254c94 to
629364a
Compare
Contributor
Author
|
/ai-review |
pull Bot
pushed a commit
to oogalieboogalie/cli
that referenced
this pull request
Sep 9, 2026
Expose the new local runtime as `supabase stack start|stop`. Projects can opt top-level `start` and `stop` into that runtime with `[experimental] stack = true` in `supabase/config.toml`, or override it with `SUPABASE_EXPERIMENTAL_STACK=1|0`. Selection happens before argument parsing and completion, preserving each implementation’s flags and the invoked command’s telemetry identity. Unreadable or invalid routing config defaults to the legacy command tree; explicit environment overrides take precedence, and each command retains its own execution-time config validation. The shared experimental flag resolver is reusable for the later workers migration. `status` keeps its existing implementation and `experimental workers` remains available. The two stack backends retain separate state and databases; enabling the flag does not migrate existing data. The flag is excluded from hosted project configuration and accepted as a TypeScript-owned field by the Go sidecar. Extracts the start/stop portion of supabase#6516 onto `develop` after supabase#6507, so it can merge independently of the remaining stack commands. Regenerates the published configuration schemas, including previously stale auth fields already present in the source schemas. Refreshes stale Go config fixtures to match the current serializer and schema.
Contributor
Author
|
The feature flag is on |
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.
Expose the new local runtime as
supabase stack start|stop|status|list|logs|prepare|restart, replacingsupabase experimental stack.Projects can set
[experimental] stack = trueinsupabase/config.tomlto make top-levelstart,stop, andstatususe the corresponding new commands. Backend selection happens before argument parsing and completion, so each implementation retains its own flags. Explicitsupabase stackcommands always use the new backend.SUPABASE_EXPERIMENTAL_STACK=1or0overrides the config setting for top-level aliases; unset or empty values fall back to config, and other values are rejected. Without an environment override, absent or false configuration preserves the legacy aliases.The backends retain separate state and databases. Switching the flag does not migrate or reuse legacy data. The flag is local CLI configuration and is excluded from hosted project configuration. Other local-stack command families remain unchanged.
Routing follows the same working-directory and TOML-file selection as the lifecycle handlers, including both shell completion modes. Command telemetry retains the invoked command path and a unique run identifier.
New routing code stays within the Effect-linted stack command directory. This follows the command implementations through #6512.