$ the-wire · showcase
Worker deployments gain exposure control and --instances flag
By RepoJournal · Filed · About Supabase
Supabase CLI's @supabase/config v0.4.0 adds an exposure dial and lets workers new set instance count up front.
The @supabase/config package reached v0.4.0, adding an `exposure` dial (`public`/`private`) for worker deployments on `workers new` and `workers push`, plus a new `--instances` flag that lets `workers new` set instance count up front instead of only through `push`. [1] Exposure is recorded in `config.toml`/`config.json` and resolved with the same precedence as size/runtime: flag override, then recorded value, then the `public` default; an unrecognized recorded value refuses the deployment. [1] This is the headline feature of the config release, which bundles the change under config-v0.4.0. [2]
Elsewhere, supabase_testing v0.1.1 published to pub.dev, a dependency update to the latest release for the Flutter testing package. [3] The evals repo refreshed its eval results from the latest automated eval run, updating `apps/web/src/data/eval-results.json`, with no behavioral change for users. [4]
Action items
- → Review the new exposure and --instances flags before adopting config v0.4.0 in worker deployments supabase/cli [monitor]
- → Update supabase_testing to v0.1.1 in Flutter projects supabase/supabase-flutter [plan]
References
- [1] feat(workers): add exposure control and new --instances flag ↗ supabase/cli
- [2] @supabase/config v0.4.0 ↗ supabase/cli
- [3] supabase_testing v0.1.1 ↗ supabase/supabase-flutter
- [4] chore: refresh eval results ↗ supabase/evals