Repository navigation
chore(stack): bump edge-runtime to v1.78.0-r0 - #7502
Merged
Merged
Conversation
supabase-cli-releaser
Bot
requested review from
a team and
supabase-oss
as code owners
November 5, 2026 05:39
supabase-oss
approved these changes
Nov 5, 2026
Contributor
CLI benchmark (Lightweight Commands): no changes foundCommit
API calls: unchanged for all 7 commands. Binary size: 134.6 MB, unchanged. Details: timing ranges, API calls per command, slowest phasesTiming ranges
API calls per command
Slowest phasesNo command moved beyond noise, so there are no phase deltas. Comment |
jgoux
approved these changes
Nov 5, 2026
kallebysantos
pushed a commit
to kallebysantos/supabase-cli
that referenced
this pull request
Nov 5, 2026
…pabase#7504) ## TL;DR Fixes an e2e port race and adds named per-phase deadlines to a test whose stall cause is still unknown. The `sso list` flake originally in this PR is already fixed on `develop` by supabase#7502. - **`status` e2e › reports a running local stack…** failed with Kong's host port `address already in use`. The e2e helper picked ports by binding port 0 and releasing it, so they came from the kernel's ephemeral range, where an outbound connection on the runner could take one before Docker published it. Ports now come from 1024–9999, below both the stack's own allocation ranges (10000 and up, see `packages/stack/src/Ports.ts`) and the OS ephemeral ranges, so neither a concurrent stack-mode e2e nor an outbound connection can claim a probed port. Each port is probed on `0.0.0.0`, as Docker binds it, and on `127.0.0.1`, because macOS lets a wildcard bind succeed over a loopback-only listener. Ports stay partitioned per e2e worker. - **`DockerDatabaseStorage` › keeps the prior marker decodable when a real kill lands…** hit the 20s test timeout and the failure didn't say which step hung. Each remaining phase (helper image, `prepare`, PG_VERSION seed, killed writer exit and pipe close, `markInitialized` retry, both cleanups) now fails with a `PhaseStallError` naming the phase, well before the test timeout. This is diagnostic-only; the next failure will name the phase to fix. ## ref spotted in: - status e2e: https://github.com/supabase/cli/actions/runs/41813449030/job/126518169570 - DockerDatabaseStorage: https://github.com/supabase/cli/actions/runs/41820563616/job/126542347726 --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Julien Goux <hi@jgoux.dev>
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
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.
This bumps edge-runtime from v1.77.9-r0 to v1.78.0-r0.
https://github.com/supabase/slim-services/releases/tag/edge-runtime-v1.78.0-r0
Planned after supabase/slim-services published v1.78.0-r0. This branch is rewritten from develop whenever a newer relevant release arrives.