supabase / cli / 36734366353
67%
develop: 67%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7102-9bfe6af0c27bb182dcbfd296cc94a961cc928b2d
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
36734366353

push

github

web-flow 
feat(cli): report stack MCP at the API URL and include connection env in JSON (CLI-2546) (#6914)

## Summary

Follow-up to #6894 and #6898 (which serves Studio's MCP server at `/mcp`
on the shared API listener). With the stack backend, `start` and
`status` now report connection details the way legacy `start`/`status`
do:

- `MCP_URL` is `<API_URL>/mcp` (for example
`http://127.0.0.1:54321/mcp`), present when the API listener and a
Studio member exist. `endpoints` no longer carries a synthetic
`studio.mcp` entry.
- `DB_URL` is a plain
`postgresql://postgres:<password>@<host>:<port>/postgres` using the
`postgres` role, built by the same helper `db` commands connect with,
without the internal `connect_timeout` parameter.
- The exported variables are `API_URL`, `REST_URL`, `FUNCTIONS_URL`,
`DB_URL`, `STUDIO_URL`, `MCP_URL`, `MAILPIT_URL`, `INBUCKET_URL` (a
deprecated alias of `MAILPIT_URL`, as in legacy), `PUBLISHABLE_KEY`,
`SECRET_KEY`, `ANON_KEY` and `SERVICE_ROLE_KEY`. The never-populated
`S3_PROTOCOL_*` names are no longer accepted by `--override-name`, which
now names a rejected entry and lists the valid variables.
- The `status --env` hint printed by `start` is exercised through the
real command grammar, including named stacks and `--workdir`.

**Deliberate contract change:** `start` JSON (every success path) and
`status` JSON now include an `env` object with those values, including
the local keys and the password-bearing `DB_URL`. It is the same map
`status --env --output-format json` returns. Previously the docs
promised that only `status --env` revealed credentials; this matches
legacy `start`/`status`, whose JSON output includes the local keys.
Plain `status` JSON `env` comes from saved bindings and still reports
when credentials cannot be read, while `--env` requires a reachable
owner and a running primary database.

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 36734366353.1 79
66.74
GitHub Action Run
Source Files on build 36734366353