supabase / cli / 37284349235
67%
develop: 67%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7129-d68f6d098f8e65a6f2909087fa443bae284eb405
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
37284349235

push

github

web-flow 
fix(cli): accept the short stack id from stack list in --stack-id (#6967)

## Summary

**TL;DR:** `supabase stack list` prints an 8-character stack ID, but
every `--stack-id` flag rejected it and required the full 64-character
id. Every stack command now accepts the short ID from the list, or any
unique prefix of at least four characters, the same convention git and
docker use. The list table keeps its compact column.

### Before

```mermaid
flowchart LR
  L["stack list"] --> S["ID column: 8 chars"]
  S --> D["stack destroy --stack-id abcd1234"]
  D --> E["error: must be a lowercase SHA-256 stack id"]
```

### After

```mermaid
flowchart LR
  A["--stack-id value"] --> B{"4-64 lowercase hex?"}
  B -->|no| E["flags error + hint"]
  B -->|64 chars| F["exact lookup"]
  B -->|4-63 chars| D["match saved stacks by prefix"]
  D -->|none| N["not found: run stack list"]
  D -->|several| G["ambiguous: lists full ids"]
  D -->|one unreadable| I["read error surfaced"]
  D -->|one| OK["full id used"]
  F --> OK
```

### Why

Copying the ID column from `stack list` into `stack destroy --stack-id`
(or `stop`, `status`, ...) failed with `--stack-id must be a lowercase
SHA-256 stack id`, so users had to rerun the list with `--output-format
json` to find the real id.

### What changed

- The shared stack target resolver accepts a full id (unchanged exact
lookup) or a unique lowercase-hex prefix of 4 or more characters. This
covers `destroy`, `stop`, `start`, `restart`, `status`, `logs`, and
`prepare`.
- A prefix matching several stacks fails with a flags error listing
every matching full id. A prefix matching a stack whose saved state is
unreadable surfaces the read error instead of reporting it missing.
- "Not found" and malformed-id errors now point to `supabase stack
list`.
- The `status --env` pointer printed by `stack start` repeats the
resolved full id rather than the typed prefix.
- Flag help, command `SIDE_EFFECTS.md` files, and
`docs/stack-commands.md` describe... (continued)

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37284349235.1 79
66.74
GitHub Action Run
Source Files on build 37284349235