[pull] master from supabase:master#729
Merged
pull[bot] merged 12 commits intocode:masterfrom Mar 5, 2026
Merged
Conversation
This pull request upgrades the `next` framework and its related dependencies from version 16.0.11 to 16.1.6 across the `studio` project.
## Problem When navigating between buckets after having selected a folder, the storage view shows the previous folder content. ## Solution Set the selected bucket before navigating to it, preventing a race condition with Valtio updates and the effect that loads the bucket content. ## How to test 1. Create 2 buckets 2. In one of them, create a folder and upload some files 3. Go back to the bucket list 4. Open the other bucket Results: - It should not show the previous bucket content anymore - It should not show an empty 2nd column either --------- Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES
Added an alternative approach using the Supabase S3-compatible API and AWS CLI for bulk operations such as downloading, moving, and reorganizing objects in a bucket. Linear task: https://linear.app/supabase/issue/DOCS-725/update-storage-troubleshooting-doc-with-bulk-operation-workaround.
removing flags: - `enableCreateCommands` - `enableSearchEntitiesCommands`
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? - For the new filters experience, we are missing null changes for dates and also no support for isNull - Updated E2E tests to account for new null cases
We need to make sure we take spelling into acccount. 
…#43447) ## Problem When testing things in SQL Editor, you often have to impersonate the same user many times. It's cumbersome to look for them. We have a _Recents_ list but its order is not practical. ## Solution Invert the order of the _Recents_ list so that the last impersonated user is the first one ## How to test - Create multiple users - Open the SQL Editor - Impersonate different users - Check the order of the list
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Update Log Drains feature page ## What is the current behavior? The Log Drains feature page (`/features/log-drains`) reflects outdated information: - Status shows Public Alpha - Description only mentions Datadog and custom HTTP endpoints - Docs link points to the original blog post (`/blog/log-drains`) - No mention of Pro plan availability ## What is the new behavior? - Status updated to GA - Description updated to reflect Pro plan availability (previously Team/Enterprise only) - All supported destinations listed: Datadog, Grafana Loki, Sentry, AWS S3, Axiom, and generic HTTP - Pricing included: $60/drain/project + $0.20/M events + $0.09/GB egress - Docs link updated to `/docs/guides/telemetry/log-drains` ## Additional context Add any other context or screenshots. Co-authored-by: Ana Mogul <ana1337x@users.noreply.github.com>
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? A new blog post to announce Log Drains being available on Pro ## What is the current behavior? N/A ## What is the new behavior? Adds the blog post 2026-03-05-log-drains-now-available-on-pro.mdx announcing Log Drains availability on the Pro tier. It will be live at https://supabase.com/blog/log-drains-now-available-on-pro ## Additional context Related to #43360 (Log Drains feature page update for Pro launch) Co-authored-by: Ana Mogul <ana1337x@users.noreply.github.com>
…43383) - Filter out never-run queries early: previously the queries didn't check if a statement had ever actually been executed, so PostgreSQL would process and return those useless rows. Adding WHERE calls > 0 skips them upfront. - Replace window functions with a pre-computed total: two queries were using a SQL window function to calculate the "% of total time" column, which forces PostgreSQL to load every single row into memory before returning results. Replaced with a small CTE that computes the total once separately, so PostgreSQL can apply the row limit without buffering everything first. This was the main cause of page crashes on databases with a large query history. - slowQueriesCount bug fix: added missing as statements alias - queryMetrics WHERE clause fix: ${where} was producing WHERE ... WHERE ..., now uses .replace(/^WHERE/, 'AND')
I'm relatively new to supabase, but in my current understanding the SQL selects are inconsistent with the given example schema as the column is named `room_topic` there. ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. Yes. ## What kind of change does this PR introduce? Updates documentation. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **Documentation** * Corrected authorization policy examples in realtime guides to use accurate column references for topic-based access control in Broadcast and Presence features. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
github-actions
bot
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )