$ the-wire · showcase
CLI config push stops ignoring a piped "no"; storage and realtime artifacts refresh
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)
13 people shipped this
github-actions[bot]
@github-actions[bot]
1 cited
7ttp
@7ttp
1 cited
Coly010
@Coly010
1 cited
johnstonmatt
@johnstonmatt
1 cited
mattrossman
@mattrossman
1 cited
jgoux
@jgoux
supabase-evals-releaser
@supabase-evals-releaser
NickLittman
@NickLittman
supabase-evals-releaser[bot]
@supabase-evals-releaser[bot]
joshenlim
@joshenlim
fsansalvadore
@fsansalvadore
claude[bot]
@claude[bot]
mandarini
@mandarini
A quiet day weighted toward CLI correctness: consent handling, SSL mode classification, and project-state error messages all got sharper, while slim-services shipped new smoke-tested storage and realtime artifacts.
fix(cli): honour config push consent (CLI-2450) supabase/cli
JSON and stream JSON confirmations used to return the default before reading stdin, so an explicit piped `n` was ignored and `config push` applied remote changes anyway; unattended runs now skip updates without affirmative input or `--yes`/`SUPABASE_YES`. This is a breaking change for anything scripting `config push` without an explicit flag.
fix(cli): distinguish an unenrolled project from a missing one on the compute routes supabase/cli
The Management API returns 404 on the compute routes for several distinct conditions, and the CLI collapsed them into one message; projects outside the private alpha were told `No project <ref> was found for this account` or `"<name>" is not deployed`, sending people to re-link or re-push a project that was never the problem. Unenrolled projects are now distinguished from genuinely missing ones...
fix(cli): treat only verifying sslmodes as a local TLS demand (CLI-2366) supabase/cli
The predicate added earlier was too broad: it treated any populated `sslmode` as a TLS demand. `prefer` and `allow` name a TLS/plaintext fallback, and now only verifying sslmodes count as a local TLS demand, so `sslConfigsFor` no longer misreads fallback modes.
feat(studio): let High Compliance projects opt-in to Assistant data access supabase/supabase
Orgs with the HIPAA add-on had the Assistant's opt-in level forced to `disabled` on High Compliance projects regardless of their AI settings, a restriction that predated the AI provider BAAs. The server and client restrictions are removed so those projects honor the org's chosen setting.
storage v1.79.4 supabase/slim-services
Portable, smoke-tested artifacts for linux/amd64, linux/arm64 and darwin/arm64 ship as `ghcr.io/supabase/cli/storage:v1.79.4`, with realtime following at v2.137.3; each release carries a SHA256SUMS file and an immutable digest reference for pinned deploys. Pgmeta also gained an independent admin listener via `PG_META_ADMIN_PORT`, accepting `0` for an OS-assigned port, which fixes collisions whe...
Action items
