Changelog

Inline Editor (Feature Preview)#

We're introducing a new inline editor that you may toggle through Feature Previews! 🙂 The inline editor can be used to run SQL wherever you are in the dashboard without taking you away from what you're doing. As usual, we'd love to hear what you think about this so please do feel free to share with us the good and (perhaps more importantly) the bad about this functionality right here in our GitHub discussions! 🙏 More details and information about this is also available there 😄

PR: https://github.com/supabase/supabase/pull/33541

Link: https://supabase.com/dashboard/project/_

Other bug fixes and improvements#

General

• Fix Assistant's usability for local / self-host environment (PR)

Auth

• Add context menu support for users to copy email or delete user (PR)
• Add link to open user logs in the Auth logs (PR)

Billing

• Support adding additional billing email address (PR)
• Add Logdrain Egress to Total Egress per day usage chart (PR)

Edge Functions

• Redirect back to main page of edge functions if navigating to a slug that doesn't exist (PR)

Advisors

• Remove unnecessary 2dp precision for ms values in Query Performance (PR)
• Fix retrieving indexes in use for a selected SELECT query (PR)

Schema Visualizer

• Support downloading current view as PNG (PR)

Storage

• Fix List view footer showing up top instead of the bottom, covering the first item in the list (PR)

Logs

• Allow users to click on a property of a selected log and add it to search (PR)
• Remember last visited route in the Logs section (PR)

Reports

• Add Supavisor connections to database reports (PR)

We have introduced two new API endpoints that allow you to deploy and update Edge Functions programmatically. This will be handy if you're building a Supabase integration or want to create an internal workflow without relying on Supabase CLI.

These are the same endpoints we use internally for Deploying Edge Functions from CLI without needing Docker and writing Edge Functions using AI assistant.

Deploy an Edge Function#

This endpoint allows you to deploy a function by providing source files and metadata in a multipart/form-data body. You can also provide a function slug as the query parameter. If an existing function for the same slug exists, it will be updated; otherwise, a new function will be created.

You can pass the bundleOnly=1 query parameter to return the response metadata to the bundled function without persisting it. This is useful if you want to bulk update multiple functions atomically. Check the next section for the new bulk update endpoint.

API reference: https://supabase.com/docs/reference/api/v1-deploy-a-function

Example:

After the function is created, you can immediately invoke it:

Bulk update Edge Functions#

This endpoint allows you to update multiple Edge Functions atomically.

When deploying multiple edge functions, we recommend calling the deploy endpoint with the bundleOnly=1 query parameter, collecting the responses and then calling bulk update endpoint to update them atomically.

API reference: https://supabase.com/docs/reference/api/v1-bulk-update-functions

Write and run queries from anywhere in the dashboard#

https://github.com/user-attachments/assets/5951fbb2-3db7-48e5-b4fa-7c83fbad3d2d

Today we are introducing a feature preview that gives you access to a new "inline editor". This is a SQL editor that is accessible from wherever you are in the dashboard. You can write or generate queries, run queries, view results, and save them to snippets if needed. It sits alongside other pages in the dashboard which makes it easy to reference tables, policies, functions, triggers etc while writing your queries.

As part of this preview we are also changing how you create and edit policies, triggers and functions to make use of this new inline editor. We often receive feedback around the existing UI based approach to creating policies, and our hope is that with the continued advancement of LLM's we can augment a plain SQL Editor with AI assistance vs needing a UI. The inline editor has access to an inline Assistant (press cmd + k while in editor) which will help you generate and modify queries.

To enable the feature preview, click your profile avatar, click feature previews and enable inline editor

What we'd like to know from you#

• When you use the inline editor, please tell us what you used it for, how the experience was, and what could be improved
• For each use case, try the inline assistant (via cmd + k) and provide feedback on the results. We want to continue to iterate on our prompts so that accuracy is as good as it can be
• How comfortable are you using an open editor with templates and AI guidance vs the existing UI based approach for policies and functions?
• Any other ideas or suggestions

[!NOTE] This change has now been fully rolled out - thank you everyone for the feedback! 🙏

We've made a significant proposal to enhance the Supabase Dashboard UX, ensuring that Organizations serve as the central hub for managing billing and member access. This update introduces clearer navigation between Organizations and Projects, providing a more intuitive experience for all users.

We encourage everyone to share their feedback in this discussion while we actively refine these changes.

Quick video demo#

https://github.com/user-attachments/assets/1492484b-b3f7-44c5-817c-3188689ef528

What’s Changed?#

Organization#

• Navigation will focus on 1 Organization at a time.
• When you are viewing an organization only the Projects for that Navigation will be visible.
• You can switch Organization by clicking the Organization picker on the top header.

Sidebar Updates#

• Separate sidebars for Projects and Organizations.
• The User Account Dropdown will be moved to the top right, and be always visible.

Improved Routing & Auto-Redirects#

• You will be redirected back to your last active organization when opening the Dashboard.
• Users without an organization will always be prompted to create one upon signup.
• If no organization is available, you will be prompted to create an organization.

New /organizations Page#

• Lists all organizations owned by the user.
• We may also support a page which shows all projects for all of your organizations.

Account Settings#

• Account settings moved out of the organization context.

Usage Banners & In-App Notifications#

• Consolidated banners at the top of the dashboard.
• Clear notifications about unpaid invoices in other organizations.
• Notifications will be filtered per active organization.

Self-hosting / Local#

• No major changes for self-hosting or local

Rollout#

• Changes are behind a feature preview in the dashboard
• We will roll out to the hosted platform first as incremental % rollout where users will be opted into the feature preview by default
• If you might want opt out of the changes, you may disable the changes via the feature previews which you can access through the user dropdown in the header here:

Feedback#

Please feel free to leave feedback in this thread.

We've introduced an experimental flag to the Supabase CLI, which allows you to deploy Edge Functions without running Docker.

How to use#

This also simplifies importing files outside the supabase/ directory within Edge Functions. Useful for monorepo setups where you want to share code between your frontend and Edge Functions.

For example, Given the directory layout below, you can import my-lib from either index.ts or deno.json.

The new flag is available from the Supabase CLI beta releases 2.13.3. Please check CLI upgrade guide on how to use the beta releases on your machine.

CI#

We also recommend using the --use-api flag if you deploy Edge Functions via CI. This should speed up the deploys as it no longer requires Docker and also solves a race condition previously occurred when deploying multiple functions in parallel.

Here's an example GitHub Action config:

Note: If you run into any issues with the --use-api, you can drop the flag to use the default Docker-based deploy mechanism.

Note 2: To run/ test Edge Functions locally (supabase functions serve), you will still need Docker. This only modifies deploy behavior.

Deploy Edge Functions via the Assistant#

https://github.com/user-attachments/assets/c567ecc2-8eed-4589-b077-f578ceaeb562

You can now get help with writing edge functions using the Assistant, and also deploy the suggested edge functions right from the dashboard! This is just the first step towards providing a convenient way to manage your edge functions through the dashboard instead of using solely through the CLI, so watch this space! 👀 🙂

PR: https://github.com/supabase/supabase/pull/33293

Link: https://supabase.com/dashboard/project/_

Update to Authentication settings location in the dashboard#

All authentication settings are now consolidated into in one place, which is within the Auth section of the dashboard. They were previously split between project settings and the authentication product page which created confusion and potentially hid functionalities that a user might be looking for. We'll eventually also follow up with similar efforts for other product settings to improve the general information architecture of the dashboard, in hopes to help make finding your way around the dashboard better! 😄🙏

PR: https://github.com/supabase/supabase/pull/33335

Link: https://supabase.com/dashboard/project/_/auth/users

Table Editor peek referencing row from the table#

Clicking "View reference row" from the Table Editor now shows the row in a Popover rather than opening the referencing table with the relevant filters applied. This is in hopes to make the UX less intrusive and abrupt - and we'd love to hear what you think! Feel free to leave any feedback either through the dashboard or right here in the discussions 🙂

PR: https://github.com/supabase/supabase/pull/33141

Link: https://supabase.com/dashboard/project/_/editor

Easy way to Fix "Security Definer view" warnings#

Views that were created in the public schema without specifying security invoker will normally have a warning in the Table Editor regarding its accessibility via the project's API. Understandably, the solution to address this might not be intuitive, especially if you're not familiar with Postgres. As such, we've added a convenient action to automatically address this warning by applying the necessary fixes.

PR: https://github.com/supabase/supabase/pull/33363

Link: https://supabase.com/dashboard/project/_/editor

Other bug fixes and improvements#

Table Editor

• Changing schemas will render the table editor empty state instead of persisting the currently viewed table to prevent confusion (PR)
• Add support for bytea data type (PR)

SQL Editor

• Each section's (Shared, Favorites, Private) opened/closed state now persists from where you left off (PR)
• Support duplicating a query (PR)
• Fix inability to scroll results section when query returns an error with a long message (PR)
• Opt to not clear search results when clicking on a query while searching (PR)
• Fix moving query to new folder (PR)

Database

• Fix database tables not showing foreign key relations when opening Edit Table panel for the first time (PR)

Reports

• Add refresh button to Custom reports, API report, Storage report and Database report (PR)

Webhooks

• Fix issue with saving values with quotes in http parameters and headers (PR)

Cron

• Support single quotes in cron job names (PR)

Advisors

• Support resetting query performance report on read replicas (PR)

Logs & Analytics

• Support navigating logs in the table with arrow keys (PR)

Here’s everything that happened with Supabase in the last month:

Third-party Auth with Firebase is now GA#

Use Firebase Auth with your Supabase projects. [Docs]

Easier to see errors in log charts#

Log charts in Supabase are now stacked with successes and errors on top of each other, and colored by type. [Link] [GitHub]

Enhanced type inference for JSON fields#

Set up custom types with supabase-js for more concise and accurate types that reflect your data. [GitHub]

Type validation for query filter values#

The Supabase TypeScript SDK will correctly validate all query filter values in  eq,  neq, and  in  methods. [GitHub] [Docs]

AI Prompt for writing Edge Functions#

A prompt to help generate Supabase Edge Functions following best practices that you can supply to Cursor, Copilot, and other AI coding tools. [Docs]

Quick Product Announcements#

• Free plans are now limited to 0.5GB per project instead of 0.5GB per account. Keep building! [GitHub]
• Now you can top up your credit balance through your organization's billing settings. [GitHub]
• Added 3 configurable parameters to control disk autoscaling. [GitHub]
• Easier to find queries in the SQL Editor. [GitHub]

Supabase is deprecating Fly’s Postgres offering managed by Supabase on April 11, 2025.

Why are we deprecating this offering?#

This deprecation enables us to focus on a new architecture for scale-to-zero databases, zero-downtime upgrades (more on this later), and more. Afterward, we’ll re-evaluate multi-cloud deployments beyond AWS, our current cloud provider.

What’s the current status of Fly Postgres on Supabase?#

We have disabled Fly Postgres signups and existing Fly Postgres customers will no longer be able to spin up new projects on Supabase. However, you can still access any existing Fly Postgres database.

What is the deprecation timeline?#

Before April 11:

You will still be able to access your existing Fly Postgres projects. We strongly recommend that you transition to Supabase’s or Fly’s native Postgres offering as soon as possible.

On April 11:

Your Fly Postgres projects are removed from our platform.

Reach out to our support if you have any questions or concerns regarding this deprecation.

Log charts now show stacked charts with total warnings and errors#

With stacked charts, you should now be able to get a better, faster glance at your logs' status, and also identify potential issues with incoming requests easily!

Link: https://supabase.com/dashboard/project/_/logs/edge-logs

PR: https://github.com/supabase/supabase/pull/32742

Additional parameters added to Disk Settings#

3 new configurable parameters have been added that can control the autoscale behaviour of your disk, namely:

• Autoscale growth percent: Refers to the percentage of current disk size to grow by
• Minimum increment: Refers to the minimum value to grow the disk size by when autoscaling
• Maximum disk size: Refers to the maximum size that your disk can grow to

These parameters can be configured anytime with no cooldown, and can be accessed under "Advanced disk settings" in your project settings "Compute and Disk"

Link: https://supabase.com/dashboard/project/_/settings/compute-and-disk

PR: https://github.com/supabase/supabase/pull/32628

SQL Editor searching now renders a flat list#

https://github.com/user-attachments/assets/3cd07693-882d-486b-b848-842d67d0316a

This addresses a UX problem whereby searching for snippets do not immediately surface results that might be within folders - with rendering a flat list instead, this should enable users to find what they need faster. Results are also no longer separated into "Shared", "Favorites", or "Private to make scanning through results easier.

Link: https://supabase.com/dashboard/project/_/sql/new

PR: https://github.com/supabase/supabase/pull/33064

Bug fixes and other improvements#

General

• More mobile responsiveness improvements (PR)

Advisors

• Show timing in seconds instead of ms if > 1000 ms (PR)
• Allow exporting advisor results to CSV, or copy as JSON / Markdown

Cron

• Show all cron jobs even those with no names (PR)
• Any changes made using the UI will reflect in the SQL snippet textbox to support further customization (PR)

Table Editor

• Fix a bug with Set to NOW CTA that was specifically happening only in certain timezones (PR)

SQL Editor

• Fix X axis labels with charting in SQL Editor (PR)
• Fix client crash issue when using a non-numerical column as the Y axis (PR)
• Opened / closed state of each section is now persisted (PR)
• Support duplicating a query (PR)

[!NOTE]
This is only relevant for Free Plan customers.

We've relaxed the Database Size limit on the Free Plan to be 0.5 GB per active project, rather than 0.5 GB for your entire Free Plan organization (previously included paused/deleted projects within your billing cycle). This will be beneficial in a few cases:

• When pausing or deleting projects, they will no longer count towards the Free Plan limit.
• When launching more than one project on the Free Plan, each project is allowed 0.5 GB Database Size, rather than a total of 0.5 GB (i.e. two projects using 0.25 GB).

Before Every project that has been active at some point in your billing cycle counts towards the 0.5 GB Database Size limit. If you've deleted a project, the average Database Size will still count towards your limit. We sum up the average Database Size of all projects that are/have been active in the billing cycle. Two projects with 0.5 GB Database Size each equal a Database Size usage of 1 GB and therefore exceed the Free Plan quota.

After We only limit active projects to a Database Size of 0.5 GB per project. Deleted or paused projects, even within the billing cycle, do not count towards your Database Size limits. As long as none of your active projects exceeds 0.5 GB Database Size, you'll stay within the Free Plan limits. Two projects with 0.5 GB Database Size each would still be within the Free Plan quota, as no project is exceeding 0.5 GB.