$ the-wire · showcase
CLI stack goes flag-gated, functions serve stops crying wolf
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
14 people shipped this
jgoux
@jgoux
2 cited
joshenlim
@joshenlim
1 cited
ivasilov
@ivasilov
1 cited
seangeo
@seangeo
1 cited
Prashansa Kulshrestha
@Prashansa-K
1 cited
Prashant Sridharan
@CoolAssPuppy
Miranda Limonczenko
@czenko
supabase-evals-releaser
@supabase-evals-releaser
supabase-evals-releaser[bot]
@supabase-evals-releaser[bot]
edgurgel
@edgurgel
leandrocp
@leandrocp
Tobias Pfeiffer
@PragTob
Mandar Joshi
@mandar1045
7ttp
@7ttp
Supabase's CLI made its experimental local stack backend opt-in and fixed `supabase functions serve` reporting working sessions as failures, while devs got SQL Editor column completion and a Next.js bump off a vulnerable version.
fix(cli): report functions serve outcomes from real container state (CLI-2426) (#6594) supabase/cli
`supabase functions serve` used to report almost every session as a failure, including containers that exited cleanly on their own with exit 0, and most of the failures it did report carried no usable classification. Outcomes now come from real container state, so a session that worked no longer shows up as broken.
fix(cli): gate stack commands behind experimental flag supabase/cli
`supabase stack` was registered unconditionally and bypassed feature-flag resolution, so it appeared in help and completion even for users who never enabled it. It now registers only when `experimental.stack` is set, resolved from TOML or JSON project config with `SUPABASE_EXPERIMENTAL_STACK=1` or `0` taking precedence; top-level `start` and `stop` use the stack implementations only when enable...
feat(cli): add experimental stack status supabase/cli
`supabase status` and `supabase stack status` now share one implementation when the stack feature is on, reporting identity, runtime, owner, readiness, endpoints, and configuration drift without revealing credential values, plus connection-variable export. With the flag off, the `stack` command group is absent entirely.
chore: Bump nextjs to non-vulnerable version supabase/supabase
Next.js moved off a vulnerable version in both the application and documentation sites, landing on 15.5.24 and aligning workspace tooling with 16.3.5.
Improve SQL Editor auto completion for column names supabase/supabase
SQL Editor intellisense used to resolve table names nicely after the `.` operator but offered nothing for a table's columns after a `where` clause; the change adjusts `PgSQLCompletionProvider` to cover that case.
chore(devtools): Improve local Realtime Inspector functionality and DX supabase/realtime
The Realtime Inspector was expecting the socket at `/realtime/v1/websocket` rather than the `/socket/websocket` path supabase-js uses, which is why it never worked locally. It now runs against the local stack, and pgdelta keeps grants intact on customer-created roles rather than dropping them.
Action items
- → Bump Next.js to a non-vulnerable release (15.5.24 or 16.3.5) in apps and docs supabase/supabase [plan]
