RepoJournal
Supabase @supabase
124 wires and counting

$ follow Supabase

Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-09-12
stories 79
GitHub RSS Archive Reviews Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Supabase CLI gains stack service selection, slim-services pins imgproxy to Storage's compose value

By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology

github-actions[bot] jgoux seanoliver mattrossman Miranda Limonczenko Pamela Chia supabase-evals-releaser
11 people shipped this
github-actions[bot] @github-actions[bot] 4 cited jgoux @jgoux 3 cited seanoliver @seanoliver 2 cited mattrossman @mattrossman 1 cited Miranda Limonczenko @czenko 1 cited Pamela Chia @pamelachia 1 cited supabase-evals-releaser @supabase-evals-releaser supabase-releaser @supabase-releaser supabase-releaser[bot] @supabase-releaser[bot] Aleksi Immonen @4L3k51 dnywh @dnywh

Supabase's CLI shipped experimental stack controls for choosing services, stopping everything, and destroying stacks, while slim-services fixed an hourly polling gap that had left published imgproxy stuck at v3.8.0.

The CLI added stack command options and destruction for experimental local stacks [1]: `start --exclude` (or `-x`) takes comma-separated or repeated service names, preserves the project file, and records the effective configuration in stack state, with dependent services disabled automatically (excluding REST or Analytics disables Studio), while `stop --all` preserves data and attempts every service. Managed stacks can now start without a `supabase/config.toml`, using defaults without creating the file, and new stacks select Docker when its client is installed and native otherwise, with a stopped Docker daemon still selecting Docker; existing stacks retain their runtime [2].

On the release side, slim-services followed Storage's imgproxy pin in release polling after imgproxy was excluded from hourly polling, leaving the published version at v3.8.0 [3]. The poller now reads `services.imgproxy.image` from Storage's Compose infrastructure on master and dispatches exactly that pinned version through the existing external source-build and OCI mirror workflow; Storage currently pins v3.26.0, also used in its latest stable v1.76.2 release [3]. Alongside it, the repo published smoke-tested runtime artifacts for postgres 17.6.1.171 [4], imgproxy v3.26.0 [5], storage v1.77.0 [6], and realtime v2.135.0 [7], each with a multi-platform Docker image on ghcr.io/supabase/cli and an immutable digest reference.

In supabase/supabase, the docs guide 404 handling changed: expected guide-path 404s were reported to Sentry as errors, making up roughly 246k events and nearly all Docs volume with 0 users impacted, because `getGuidesMarkdownInternal` tested `error.cause instanceof FileNotFoundError` while `GuideModelLoader.fromFs` rethrows `FileNotFoundError` directly and sets `cause` to the underlying `ENOENT` error [8]. The www sitemap generator also stopped dropping changelog entries: it reads changelog URLs from the build-generated RSS feed but only accepted links whose slug starts with a number, the shape `computeChangelogEntrySlug` produces solely for entries carrying `legacy_gh_discussion`, so every entry authored since that migration was silently missing from `sitemap_www.xml`; the match is now widened to any non-empty slug [9].

On the evals side, evals were reorganized under per-suite folders, `evals/<suite>/<id>/`, replacing the `suite:` frontmatter so CODEOWNERS can scope by path, and the docs team got its own `docs` suite to add and refresh evals on their own cadence [10]. The harness system prompt was removed for CLI agents because Claude Code, Codex and OpenCode ship their own system prompt and ours was layered on top [11], and skills are now installed natively per harness [12].

Action items

References

  1. [1] feat(cli): add stack command options and destruction (#6576) ↗ supabase/cli
  2. [2] fix(cli): improve stack startup defaults and clean managed state (#6563) ↗ supabase/cli
  3. [3] Follow Storage imgproxy pin in release polling ↗ supabase/slim-services
  4. [4] postgres 17.6.1.171 ↗ supabase/slim-services
  5. [5] imgproxy v3.26.0 ↗ supabase/slim-services
  6. [6] storage v1.77.0 ↗ supabase/slim-services
  7. [7] realtime v2.135.0 ↗ supabase/slim-services
  8. [8] fix(docs): stop reporting guide 404s to Sentry, redirect missing paths (#50279) ↗ supabase/supabase
  9. [9] fix(www): sitemap lists all changelog slugs (#50275) ↗ supabase/supabase
  10. [10] feat: add docs eval suite with docs team ownership ↗ supabase/evals
  11. [11] fix(framework): remove the harness system prompt for CLI agents (AI-1034) ↗ supabase/evals
  12. [12] fix(sandbox): install skills natively per harness (AI-1034) ↗ supabase/evals

$ ls supabase/reviews/ # the step-back reads

the week in review Studio moves to Nitro, CLI stack goes flag-gated the month in review Supabase ships CLI v2, Postgres middleware, and safety rails across Studio
Topics: JavaScript Full archive → Weekly reviews →

Quick answers

What shipped in Supabase on September 12, 2026?
Supabase's CLI shipped experimental stack controls for choosing services, stopping everything, and destroying stacks, while slim-services fixed an hourly polling gap that had left published imgproxy stuck at v3.8.0. In total, 35 commits, 36 pull requests, and 8 releases landed.
Who contributed to Supabase on September 12, 2026?
11 developers shipped this update, including github-actions[bot], jgoux, supabase-evals-releaser, mattrossman, seanoliver, supabase-releaser, supabase-releaser[bot], and Miranda Limonczenko, and 3 more.
What were the notable Supabase updates?
feat(cli): add stack command options and destruction (#6576), fix(cli): improve stack startup defaults and clean managed state (#6563), and Follow Storage imgproxy pin in release polling.
♥

$ log @supabase --recent

Turbopack build cache disabled, eval results refreshed 4 shipped CLI config push stops ignoring a piped "no"; storage and realtime artifacts refresh 70 shipped MCP v0.13.0 gates destructive SQL, CLI stops deleting vector buckets 113 shipped Replicator health probes land, Studio pipeline overview rebuilt 135 shipped

$ log --all # elsewhere on the wire

@openclaw Cold-start Gateway diagnostics stop crying wolf, doctor repairs plugin drift Agentic Coding Cline desktop bundles shrink, goose unblocks its own clicks

$ ls showcases/

Rails Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.