supabase / cli / 37047555310
67%
develop: 67%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7205-c246e1e662911ab35e3f3d9927bb07b0601fcaf3
DEFAULT BRANCH: develop
Ran
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
coverage: 66.737%. Remained the same
37047555310

push

github

web-flow 
fix(cli): name the changed setting and the fix when a saved stack rejects a config change (#6944)

When `supabase start` (with `[experimental] stack`) refuses a change to
a saved stack, the error now says which setting changed and what to do
about it. It used to report internal paths such as `endpoints.http` with
a generic suggestion.

- Each rejected change is reported as the `config.toml` key, or the
`SUPABASE_*` environment variable that set it, with the saved and
requested values, after a lead-in saying the saved stack cannot adopt
them. For example: `[db] major_version: saved 17, requested 15`, or
`[api] port: saved automatic, requested 54999`.
- Changes across all affected services are reported together in one
error. A shared `[api] port` appears once.
- The suggestion offers two ways out: revert the setting to keep the
stack and its data, or run `supabase stack destroy --stack-id <id>` to
recreate it. It warns that recreating deletes the local database data.
The ID is used so the command targets this stack regardless of the
current directory. When a change can't be reverted, such as a
catalog-pinned artifact or Postgres build from a CLI upgrade, the
suggestion offers only the destroy command.
- JSON and stream-json errors carry the same details in structured form
(`stack_changes` with service, path, key, saved and requested values,
plus `recreate_command`), so agents don't have to parse prose.
`stack_changes` keeps one entry per affected service, and
`recreate_command` omits `--yes`, which a JSON-mode destroy requires.

Port settings are now defined once in `stack-config.ts`, shared by
config translation and error attribution, so a new port can't be added
to one and missed in the other. The tests use the real composition
planner.

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37047555310.1 79
66.74
GitHub Action Run
Source Files on build 37047555310