Skip to content

chore(cli): declare experimental access and deprecation on commands - #7698

Open
mdonnalley wants to merge 5 commits into
developfrom
feat/cli-2684-command-lifecycle
Open

mdonnalley wants to merge 5 commits into
developfrom
feat/cli-2684-command-lifecycle

Conversation

@mdonnalley

Copy link
Copy Markdown
Contributor

Generate the CLI reference from command annotations instead of maintaining separate lists of experimental and deprecated commands. Parent help and shell completion derive the (deprecated) label from the same annotation that excludes a command from the website. Deprecated commands remain callable.

For experimental access, the command annotates the policy and its handler explicitly checks that policy. This preserves which error users see first: network-bans get validates the output format before checking access, while db schema declarative sync reads project config before checking access. CI checks that the annotation and handler reference the same policy. The annotation does not itself enforce access.

@mdonnalley
mdonnalley requested a review from a team as a code owner November 18, 2026 20:24
@mdonnalley
mdonnalley requested a review from Coly010 November 18, 2026 20:24
@github-actions

Copy link
Copy Markdown
Contributor

CLI benchmark (Lightweight Commands): no changes found

Commit fe6b0b3 against develop at d64f3c9 · 10 runs each · report only, never blocks merging

Command Workload Before After Change
supabase --version version 263 ms 272 ms no real change
supabase --help help 377 ms 370 ms no real change
supabase init init 301 ms 295 ms no real change
supabase migration new bench migration-new 312 ms 304 ms no real change
supabase config convert config-convert 317 ms 345 ms no real change (+9%, within normal variation)
supabase config validate config-validate 328 ms 342 ms no real change
supabase gen types --lang typescript --project-id replayfixtureprojref gen-types 360 ms 368 ms no real change
supabase projects list projects-list 351 ms 371 ms no real change (+5%, within normal variation)
supabase functions list --project-ref replayfixtureprojref functions-list 341 ms 323 ms no real change (-5%, within normal variation)

API calls: unchanged for all 9 commands.

Binary size: 135.3 MB, up 4.0 KB from 135.2 MB.

Details: timing ranges, API calls per command, slowest phases

Timing ranges

Command Workload Before range After range Change Verdict
supabase --version version 237-559 ms 232-469 ms +8 ms (+3%) within noise
supabase --help help 287-439 ms 304-472 ms -7 ms (-2%) within noise
supabase init init 269-388 ms 247-342 ms -6 ms (-2%) within noise
supabase migration new bench migration-new 281-403 ms 274-338 ms -7 ms (-2%) within noise
supabase config convert config-convert 265-472 ms 267-383 ms +28 ms (+9%) within noise
supabase config validate config-validate 253-380 ms 281-374 ms +14 ms (+4%) within noise
supabase gen types --lang typescript --project-id replayfixtureprojref gen-types 282-500 ms 313-413 ms +8 ms (+2%) within noise
supabase projects list projects-list 289-421 ms 303-454 ms +19 ms (+5%) within noise
supabase functions list --project-ref replayfixtureprojref functions-list 276-404 ms 266-403 ms -18 ms (-5%) within noise

API calls per command

Command Workload Before After Endpoint changes
supabase --version version 0 0
supabase --help help 0 0
supabase init init 0 0
supabase migration new bench migration-new 0 0
supabase config convert config-convert 0 0
supabase config validate config-validate 0 0
supabase gen types --lang typescript --project-id replayfixtureprojref gen-types 2 2
supabase projects list projects-list 1 1
supabase functions list --project-ref replayfixtureprojref functions-list 2 2

Slowest phases

No command moved beyond noise, so there are no phase deltas.

Workflow run

Comment /bench to run the lightweight benchmark (this comment) again on the latest commit, or /bench full to also run the integration-heavy benchmark, which posts in its own comment.

This branch has not been deployed

No deployments
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.

1 participant