• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 38228649129
67%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 12 Oct 2026 09:16AM UTC
Jobs 1
Files 79
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

12 Oct 2026 09:14AM UTC coverage: 66.737%. Remained the same
38228649129

push

github

web-flow
feat(stack): re-plan changed endpoint ports when a stopped stack starts (#6950)

With `[experimental] stack` enabled, changing a port in `config.toml`
(including removing the fixed ports a legacy `supabase init` writes)
used to make the next `supabase start` fail with "The saved stack cannot
adopt these changes". The only way out was to destroy the stack and lose
its data. Now, when a stopped stack starts, it applies endpoint port
changes and prints each one, for example `api: 54321 → 26199`. JSON and
stream-json output add an `endpoint_changes` array to the success
payload; each entry names the endpoint, the `endpoints` keys it moved
(`keys`), and its `from`/`to` port.

- `config.toml` is the source of truth. The re-plan runs inside the
stack owner's startup, while the owner holds the stack lease and before
it binds any endpoints. It saves the requested endpoint intents,
releases the changed endpoints' rows in the port registry (for example
an old sticky automatic port), and claims the new ports through the
owner's normal port acquisition, with the usual conflict and occupancy
checks. Concurrent starts attach to the winning owner instead of racing
it.
- Nothing is rolled back. A requested fixed port that is already taken
fails the start with the usual port conflict, naming the config key and
noting that the new port is saved and the previous automatic port
released, so starting again succeeds once the port is free.
- Changing which services share the API port is handled too: when a
different sharing service requests a fixed API port, the shared
listener's old automatic claim is released.
- A start request is the complete composition, so excluded or absent
services no longer pin the shared API port, and removing `[api] port`
moves the stack to an automatic port instead of being silently ignored.
A stopped service excluded during a re-plan has its endpoints rewritten
when it is requested again, so the start reuses it and its data instead
of creating a ... (continued)

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38228649129.1 12 Oct 2026 09:16AM UTC 79
66.74
GitHub Action Run
Source Files on build 38228649129
  • Tree
  • List 79
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #38228649129
  • 5bde3987 on github
  • Prev Build on gh-readonly-queue/develop/pr-6934-b5bba60046b8439aa248cfda878e9592db082757 (#37955511049)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc