supabase 2.35.2

v2.35.2

on Node.js NPM

Changelog

Bug fixes

• b3d509d: fix(functions): set per_worker as default request policy for functions serve (#4040) (@avallete)

As of CLI v2.27.0, supabase functions serve now supports hot reload when using the per_worker request policy.
This means you can get automatic reloads on code changes while still benefiting from the higher throughput of per_worker mode.

per_worker is now the default policy for new projects.
If you encounter issues with hot reload, you can switch back to oneshot mode and file a bug report.

Known issues:

• Large repositories may hit the max recursion depth limit.
• Changes in symlinked directories are not detected.
• Only files reachable through imports from the function’s entrypoint are watched.

How to switch back to oneshot mode:

1. Open your supabase/config.toml file.

2. Find or add the policy setting under [edge_runtime].

3. Set it to:

   policy = "oneshot"

4. Save the file and restart supabase functions serve.

Others

• 9a1207c: chore(deps): bump github.com/getsentry/sentry-go from 0.35.0 to 0.35.1 in the go-minor group across 1 directory (#4037) (@dependabot[bot])
• d981b48: chore: separate coverage reporting step (#4039) (@sweatybridge)