Skip to content

chore(stack): bump storage to v1.89.13-r0 - #7523

Merged
supabase-cli-releaser[bot] merged 3 commits into
developfrom
slim-bump/storage
Nov 6, 2026
Merged

supabase-cli-releaser[bot] merged 3 commits into
developfrom
slim-bump/storage

Conversation

@supabase-cli-releaser

Copy link
Copy Markdown
Contributor

This bumps storage from v1.89.12-r0 to v1.89.13-r0.

https://github.com/supabase/slim-services/releases/tag/storage-v1.89.13-r0

Planned after supabase/slim-services published v1.89.13-r0. This branch is rewritten from develop whenever a newer relevant release arrives.

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

CLI benchmark (Lightweight Commands): no changes found

Commit d05bb74 against develop at a4f9be0 · 10 runs each · report only, never blocks merging

Command Workload Before After Change
supabase --version version 223 ms 229 ms no real change
supabase --help help 199 ms 202 ms no real change
supabase init init 196 ms 195 ms no real change
supabase migration new bench migration-new 215 ms 215 ms no real change
supabase gen types --lang typescript --project-id replayfixtureprojref gen-types 243 ms 244 ms no real change
supabase projects list projects-list 219 ms 239 ms no real change (+9%, within normal variation)
supabase functions list --project-ref replayfixtureprojref functions-list 233 ms 237 ms no real change

API calls: unchanged for all 7 commands.

Binary size: 134.7 MB, unchanged.

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

Timing ranges

Command Workload Before range After range Change Verdict
supabase --version version 210-243 ms 192-250 ms +6 ms (+3%) within noise
supabase --help help 171-244 ms 177-223 ms +3 ms (+1%) within noise
supabase init init 182-232 ms 171-218 ms -1 ms (0%) within noise
supabase migration new bench migration-new 199-250 ms 194-243 ms +0 ms (+0%) within noise
supabase gen types --lang typescript --project-id replayfixtureprojref gen-types 220-277 ms 226-278 ms +1 ms (+0%) within noise
supabase projects list projects-list 208-252 ms 199-250 ms +20 ms (+9%) within noise
supabase functions list --project-ref replayfixtureprojref functions-list 206-274 ms 199-261 ms +4 ms (+2%) 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 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.

@supabase-cli-releaser
supabase-cli-releaser Bot added this pull request to the merge queue Nov 6, 2026
Merged via the queue into develop with commit 3394a54 Nov 6, 2026
50 checks passed
@supabase-cli-releaser
supabase-cli-releaser Bot deleted the slim-bump/storage branch November 6, 2026 06:47
TFSebben pushed a commit to TFSebben/supabase_cli that referenced this pull request Nov 6, 2026
…pabase#7524)

The tokenless `gen types` e2e asserts the output never mentions the
offline profile's `http://127.0.0.1:1` API URL with a plain substring
check. The CLI prints `Target: local stack (127.0.0.1:<dbPort>)`, so
whenever the randomly allocated DB port starts with `1` (e.g. `1191`)
the assertion fails even though no remote call happened. Seen on
supabase#7523.

The assertion now matches `127.0.0.1:1` only when no further port digit
follows.
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.

3 participants