$ the-wire · showcase
Replicator health probes land, Studio pipeline overview rebuilt
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?v=4)
11 people shipped this
dnywh
@dnywh
1 cited
Miranda Limonczenko
@czenko
1 cited
iambriccardo
@iambriccardo
1 cited
Colum Ferry
@Coly010
1 cited
jgoux
@jgoux
1 cited
claude[bot]
@claude[bot]
Gildas Garcia
@djhi
Saxon Fletcher
@SaxonF
juleswritescode
@juleswritescode
supabase-evals-releaser
@supabase-evals-releaser
Vaibhav
@7ttp
Supabase's ETL replicator gains opt-in liveness signaling, Studio's pipeline Overview trades shifting bespoke layouts for stable sections, and the eval desk keeps grinding down the docs pages users complain about most.
feat(replicator): Add configurable activity health probes supabase/etl
supabase/etl adds opt-in replicator health endpoints and Kubernetes probes, tracking activity independently for each WAL apply/catchup loop and each initial table copy so a stalled replication pod goes unready and, after configured failures, restarts. Copy observation carries the source commit and the final durability barrier, so a pod that is mid-copy of a single table is not mistaken for a we...
feat(studio): rebuild the pipeline overview supabase/supabase
The pipeline Overview is rebuilt around stable Pipeline health and Replicated tables sections, replacing bespoke loading, metrics, table-state and empty-state layouts that shifted while data resolved and restated status from the detail header. It also adds layout-matched loading geometry, prioritised pipeline notices and initial-sync progress.
feat(evals): eval the tables and data guide in supabase.com/docs (#264) supabase/evals
The evals desk takes on database/tables, described in the PR as the most foundational database page in the docs and the one that is red: roughly 46 percent negative across its feedback votes, on the highest vote count of any task-driven database page. The page teaches table creation but, per the same description, says nothing about protecting a table, with row level security appearing once in 5...
feat(cli): target the managed stack for local storage commands and bucket seeding (CLI-2369) (#6633) supabase/cli
With the experimental stack backend selected via [experimental] stack = true or SUPABASE_EXPERIMENTAL_STACK=1, storage ls/cp/mv/rm --local and bucket seeding now target the managed stack instead of the local one. This is a breaking change for anything scripting those commands against the stack backend.
refactor(cli): resolve hostnames through Effect services supabase/cli
Docker hostname discovery no longer reads the process environment and Docker context files synchronously, resolving them through Effect's Config service instead, with an absent context endpoint represented as Option and context metadata read through Effect filesystem, path and crypto services. Docker context precedence is preserved, so behavior stays put while the commands' requirements become ...
