--- next_cursor: eyJzY29yZSI6MCwic2VxIjo1NTcsInNpbmNlIjpudWxsLCJ0b29sIjoic3VwYWJhc2UiLCJ2IjoxfQ has_more: true next: https://sincecutoff.com/v1/changes.md?tool=supabase&score=0&cursor=eyJzY29yZSI6MCwic2VxIjo1NTcsInNpbmNlIjpudWxsLCJ0b29sIjoic3VwYWJhc2UiLCJ2IjoxfQ items: 10 --- # sincecutoff.com changes: supabase ## supabase functions download all functions when no name is provided (supabase, 2026-02-02) Published 2026-10-13 - slug: supabase-functions-download-all-functions-when-no-name-is-provided-9065ff7c82a0 - score: 0.91 How to use it: When you need to download every function from the linked Supabase project, run `supabase functions download` with no function name. Examples: ``` supabase functions download ``` - why_it_matters: Download the project’s functions without specifying an individual function name. - sources: , , - gotchas: "Version: v2.75.0"; "Function name: Omit it to download all functions."; "--project-ref : Project ref of the Supabase project; omit when using the linked project."; "--use-api: Unbundle functions server-side without using Docker."; "Prerequisite: Install the Supabase CLI, authenticate with `supabase login`, and link the local project with `supabase link --project-ref `; linking uses the stored access token for platform commands." ## supabase db advisors checks database security and performance (supabase, 2026-03-17) Published 2026-10-13 - slug: supabase-db-advisors-checks-database-security-and-performance-75b59c64d7be - score: 0.98 How to use it: When checking a Supabase database for security and performance issues, run `supabase db advisors`. To target a specific database, add `--db-url `; the command defaults to the local database. Examples: ``` supabase db advisors ``` ``` supabase db advisors --db-url ``` - why_it_matters: Check a Supabase database for security and performance issues during repository maintenance. - sources: , - gotchas: "Version: v2.81.0"; "--db-url : Connection string for the database to check; it must be percent-encoded. Mutually exclusive with `--linked` and `--local`."; "--local: Check the local database; this is the default target."; "--linked: Check the linked project; requires CLI login and a linked project reference."; "--type : Choose advisor checks by type."; "--level : Set the minimum issue level to display."; "--fail-on : Set the issue level that causes a non-zero exit status."; "Prerequisite: Use Supabase CLI v2.81.0 or later for this command, introduced in v2.81.0."; "Prerequisite: For `--db-url`, provide a percent-encoded database connection string."; "Prerequisite: For `--linked`, authenticate with `supabase login` and have a linked project reference." ## Supabase Auth configuration supports passkeys and WebAuthn (supabase, 2026-04-27) Published 2026-10-13 - slug: supabase-auth-configuration-supports-passkeys-and-webauthn-4c8d998d9570 - score: 0.97 How to use it: When enabling passkey authentication, add `[auth.passkey]` and `[auth.webauthn]` to `supabase/config.toml`; set `enabled = true` and provide the relying-party display name, ID, and origins. Examples: ``` [auth.passkey] enabled = true [auth.webauthn] rp_display_name = "" rp_id = "" rp_origins = [""] ``` - why_it_matters: Configure passkeys and WebAuthn for a Supabase Auth project. - sources: , , - gotchas: "Version: v2.95.4"; "auth.passkey.enabled (required): Enable passkey sign-in and registration; requires `auth.webauthn` configuration."; "auth.webauthn.rp_display_name (required): Human-readable relying-party name shown during passkey ceremonies."; "auth.webauthn.rp_id (required): Relying-party identifier; must be a registrable suffix of every configured origin."; "auth.webauthn.rp_origins (required): List of app origins allowed for WebAuthn ceremonies."; "Prerequisite: Include `[auth.webauthn]` with all three relying-party values when `auth.passkey.enabled` is true."; "Prerequisite: Origins must use HTTPS except loopback addresses; each origin hostname must match or be a subdomain of the relying-party ID. Up to five origins are allowed." ## Supabase CLI adds branches create command (supabase, 2026-05-18) Published 2026-10-13 - slug: supabase-cli-adds-branches-create-command-99f0fb3520da - score: 0.92 How to use it: When creating a preview branch for a repository workflow, run `supabase branches create` with the branch name. The command creates a preview branch for the linked project. Examples: ``` supabase branches create ``` - why_it_matters: Create a Supabase branch for a repository workflow. - sources: , - gotchas: "Version: 2.99.0"; "name: Branch name positional argument; the documented usage shows it in brackets."; "--project-ref: Project ref for the Supabase project; available as a `branches` command flag."; "--notify-url: URL to notify when the branch is active and healthy."; "--persistent: Create a persistent branch."; "--region: Region to deploy the branch database."; "--size: Desired instance size for the branch database."; "--with-data: Clone production data to the branch database."; "Prerequisite: The command creates a preview branch for the linked project." ## Supabase CLI adds branches list command (supabase, 2026-05-18) Published 2026-10-13 - slug: supabase-cli-adds-branches-list-command-53850465512e - score: 0.90 How to use it: To inspect preview branches, run `supabase branches list` for the linked project, or add `--project-ref ` to select a project explicitly. Examples: ``` supabase branches list ``` ``` supabase branches list --project-ref ``` - why_it_matters: Inspect available Supabase branches while maintaining a repository. - sources: , - gotchas: "Version: 2.99.0"; "--project-ref : Project ref of the Supabase project." ## Supabase CLI adds branches switch command (supabase, 2026-05-18) Published 2026-10-13 - slug: supabase-cli-adds-branches-switch-command-171d8f9495fd - score: 0.92 How to use it: When repository work needs a different Supabase branch, run `supabase branches switch ` (or provide its project ref). It updates the active branch in `.supabase/project.json`; a running local Supabase stack is stopped and restarted for that branch. Examples: ``` supabase branches switch ``` ``` supabase branches switch ``` - why_it_matters: Switch the Supabase branch used for repository work. - before: Before this command, `supabase branches list` showed the active branch but the CLI had no way to change it. - sources: , - gotchas: "Version: 2.99.0"; ": Branch name or project ref. If omitted in an interactive TTY, prompts to select a branch; without a TTY, omission fails."; "Docs conflict: Current Supabase CLI reference lists branches subcommands but omits `branches switch`, differing from the v2.99.0 command documented in its source commit: https://supabase.com/docs/reference/cli/global-flags" ## supabase db schema declarative sync adds --no-apply (supabase, 2026-05-21) Published 2026-10-13 - slug: supabase-db-schema-declarative-sync-adds-no-apply-57d46cfae43d - score: 0.96 How to use it: When you need a generated declarative-schema migration without applying it locally, run `supabase db schema declarative sync -f --no-apply` to write the migration and stop without prompting. The command requires declarative schema support to be enabled. Examples: ``` supabase db schema declarative sync -f --no-apply ``` - why_it_matters: Generate a declarative schema migration in CI or a review workflow and inspect the diff before changing the local database. - sources: , , - gotchas: "Version: v2.101.0"; "--no-apply: Generate the migration file without prompting or applying it locally."; "-f, --file : Save the schema diff to a new migration file; the example uses this to name it."; "--experimental: Enable experimental features for a single run; alternatively enable `[experimental.pgdelta]` in config.toml."; "Prerequisite: Requires `--experimental` or `[experimental.pgdelta] enabled = true` in config.toml."; "Prerequisite: The declarative sync command requires the pg-delta engine; it does not run on the legacy migra engine."; "`--no-apply` overrides the global `--yes`."; "`--no-apply` cannot be combined with `--apply`." ## Supabase CLI defaults detected coding-agent invocations to JSON (supabase, 2026-06-11) Published 2026-10-13 - slug: supabase-cli-defaults-detected-coding-agent-invocations-to-json-33cee61a8620 - score: 0.95 How to use it: When using Supabase CLI in a detected coding-agent environment, or with `--agent yes`, rely on JSON output unless you explicitly request another output mode, help, or version text. Use `--agent no` to keep human-oriented text output. Examples: ``` supabase --agent yes init ``` ``` supabase --agent no init ``` - why_it_matters: Use Supabase CLI commands in a coding-agent environment that needs machine-readable output. - sources: , - gotchas: "Version: v2.106.0"; "--agent : Global flag for every command; overrides agent detection. `auto` is the default. The v2.106.0 release note says detected agent environments and `yes` default to JSON unless another output mode, help, or version text is explicitly requested; `no` keeps human-oriented text."; "Prerequisite: Install the Supabase CLI."; "Prerequisite: `--agent` is a global flag supported by the Supabase CLI; the reference lists `auto` as its default."; "JSON is the default only when a coding-agent environment is detected or `--agent yes` is passed."; "An explicitly requested output mode, help, or version text takes precedence." ## Supabase CLI stops auto-exposing new public schema objects (supabase, 2026-06-11) Published 2026-10-13 - slug: supabase-cli-stops-auto-exposing-new-public-schema-objects-c43734a8eeb5 - score: 0.93 How to use it: When creating a `public` schema object that should be reachable through the Data API, add explicit `GRANT`s for the roles that need access. For temporary legacy behavior, set `[api].auto_expose_new_tables = true` in `config.toml`; the flag is deprecated and scheduled for removal. Examples: ``` GRANT SELECT ON public. TO anon; GRANT SELECT, INSERT, UPDATE, DELETE ON public. TO authenticated; GRANT SELECT, INSERT, UPDATE, DELETE ON public. TO service_role; ``` ``` [api] auto_expose_new_tables = true ``` - why_it_matters: When creating public schema objects that should be accessible through the Data API, configure their intended role access. - before: New public-schema objects were automatically exposed through the Data API by default. - sources: , , - gotchas: "Version: v2.106.0"; "GRANT ON