[pull] master from supabase:master#804
Merged
pull[bot] merged 18 commits intocode:masterfrom Apr 1, 2026
Merged
Conversation
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES/NO ## What kind of change does this PR introduce? docs update ## What is the new behavior? Adding 504 guide for edge functions
## 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? docs update ## What is the new behavior? Adds 500 code troubleshooting guide for Edge Functions <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * New troubleshooting guide for HTTP 500 errors in Edge Functions covering diagnostic workflows, SQL-based log analysis techniques, methods to distinguish between unhandled JavaScript errors and custom error responses, and targeted solutions for common error scenarios. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
…UG-50 (#44189) ## Problem The Compute and Disk settings page shows all 12+ instance sizes (Nano through >16XL) in a grid, which requires scrolling on smaller screens like a 13" MacBook. This makes it impossible to see all three sections (compute size, disk size, advanced settings) in a single view. Free tier users have no need to see 8XL, 12XL, or 16XL options. ## Fix Show only the first 6 compute sizes (Nano through XL) by default, cutting the grid from 4 rows to 2 rows. Larger sizes (2XL and above, plus the >16XL contact card) are revealed via a "Show all sizes" toggle button below the grid. The grid auto-expands if the project is already running on a large instance size so the selected option is always visible. ## How to test - Go to Settings > Compute and Disk on a project - Verify only 6 cards are visible by default (Nano, Micro, Small, Medium, Large, XL) - Verify the Disk size and Advanced settings sections are visible without scrolling on a 13" screen - Click "Show all sizes" and verify the remaining sizes appear (2XL through 16XL plus the >16XL contact card) - Click "Show fewer sizes" and verify the grid collapses back to 6 cards - On a project running 4XL or larger, verify the grid opens expanded by default so the selected card is visible <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Compute size options now display in a compact view with a toggle to expand and show all available sizes * Auto-expands to reveal the currently selected compute size when it's not visible in the initial view * Enhanced loading state for improved visual clarity <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.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? This PR introduces some visual indicators when a Nano project is exhausting resources on Pro plus plans. The indicator tells the user a free upgrade to Micro is available via a flashing Nano badge that guides them to Upgrade and a global banner that notifies them resources are near exhaustion, please upgrade for free. | Project List | Project View | |--------|--------| | <img width="412" height="223" alt="Screenshot 2026-03-31 at 16 11 19" src="https://github.com/user-attachments/assets/0d0e7727-e4eb-4ade-9024-528a2501596c" /> | <img width="1256" height="618" alt="Screenshot 2026-03-31 at 16 11 10" src="https://github.com/user-attachments/assets/b664e020-2b18-4842-8e64-4e49fac69eef" /> | <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Free Micro Upgrade banner appears for nano-tier projects near compute exhaustion with animated visuals and an “Upgrade for free” CTA. * Compute badge highlights near-exhaustion with glow/shimmer and an animated upgrade indicator; optional icon support added. * Per-project banner dismissal is saved locally; dismissed banners remain hidden. * **Tests** * Added tests covering banner display and dismissal scenarios. * **Chores** * Added local-storage keys and telemetry events for banner and upgrade interactions. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## 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? docs update ## What is the new behavior? Adds 503 troubleshooting doc <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added comprehensive troubleshooting guide for Edge Function 503 error responses, including diagnostic procedures to classify errors into three categories (app-level, boot-level, and internal failures) with detailed resolution instructions specific to each error type and links to complementary resources. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
## 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? Docs update: `supabaseR` is a structured, planned approach by @DeepanshKhurana and @maciekbanas to support all Supabase functionality through a package in R. We're moving with a fully open-source approach. A public Project board can be found [here](https://github.com/users/DeepanshKhurana/projects/6). The goal is to support all Supabase functionality and get the package on the official R CRAN soon. ## What is the current behavior? There is no Supabase package for R. ## What is the new behavior? We are introducing a new package for R. ## Additional context Add any other context or screenshots. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added new R language library entry to the community libraries table with documentation link * Enhanced table formatting and standardized column widths across all community library entries for improved readability <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This PR bumps various dependencies to fix vulnerabilities. The logic for bumping packages has been taken out of `fix-audit-vulnerability` into a `bump-package` script. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **Chores** * Removed unused development dependency from generator package * Updated package version overrides and vulnerability management configuration to address security concerns * Enhanced internal package dependency maintenance tooling for improved operational efficiency <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…visibility (#44293) ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES/NO ## What kind of change does this PR introduce? Includes 5 new variants to test pricing to solve cost flexibility and visibility concerns ## What is the current behavior? Current pricing page ## What is the new behavior? Variants: <img width="3840" height="2160" alt="CleanShot 2026-03-30 at 19 32 02@2x" src="https://github.com/user-attachments/assets/a4f3b048-fa0d-4137-9f24-2eb6d431f3c8" /> <img width="3840" height="2160" alt="CleanShot 2026-03-30 at 19 33 34@2x" src="https://github.com/user-attachments/assets/a9045a33-b8c3-4df1-a47d-00cf58495bb3" /> <img width="3840" height="2160" alt="CleanShot 2026-03-30 at 19 32 22@2x" src="https://github.com/user-attachments/assets/10511fc8-5e88-4e3c-baa1-56798009d86f" /> <img width="3840" height="2160" alt="CleanShot 2026-03-30 at 19 33 09@2x" src="https://github.com/user-attachments/assets/aa01aaf6-0e41-4466-bfc7-77ae912b6043" /> <img width="3840" height="2160" alt="CleanShot 2026-03-30 at 19 32 43@2x" src="https://github.com/user-attachments/assets/21834f7d-43cb-4981-9c29-934f44986714" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes **New Features** - Launched A/B testing variants on the pricing page featuring customized pricing plan layouts, descriptions, and billing options based on your assigned experiment group. - Certain plan tiers now display optional flexibility information, hourly billing rates, and project scaling details to help optimize your cost estimation and plan selection. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## 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? Bug fix ## What is the current behavior? search is passed in un-escaped ## What is the new behavior? escapes to ensure correct query format <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Bug Fixes - Enhanced query safety and reliability in performance monitoring with improved parameter handling - Fixed query condition handling for edge cases with non-finite values ## Refactor - Simplified query generation logic and streamlined internal implementation <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…mation (#43898) ## Release Notes * **New Features** * Added project acknowledgement flow when deleting organizations. Users with 10 or fewer projects must confirm each project individually; users with more than 10 projects can confirm all at once. * Organizations now display project counts and compute sizes during deletion confirmation to help users understand what will be deleted. ## What kind of change does this PR introduce? **Improvements to the delete organization workflow:** * Added a checklist that requires users to acknowledge each project before deleting organizations with up to 10 projects, and a single bulk acknowledgement for organizations with more than 10 projects. This helps prevent accidental deletion of projects. * Extracted acknowledgement UI into dedicated sub-components (`DeleteOrganizationButton.ListAck.tsx` and `DeleteOrganizationButton.SingleAck.tsx`). **Error handling and validation:** * Acknowledgement state (`checkedProjects`/`acknowledgedAll`) is reset synchronously in the button's click handler before the modal opens, preventing any stale checked state from briefly appearing on re-open. * Acknowledgement state is also reset when the organization changes (`orgSlug` effect), ensuring a fresh confirmation when switching orgs. * Deletion is blocked while projects are loading **or fetching** (including background refetches triggered by `refetchOnMount: 'always'`), preventing deletion from proceeding on stale or incomplete project data. * Added error handling for project loading failures, and prevented deletion if projects are not fully acknowledged or if there is a loading/error/fetching state. ## What is the current behavior? No explicit confirmation from the user to acknowledge all the projects: <img src="https://github.com/user-attachments/assets/68840781-467b-41ef-a821-50e471e93cc5" width="500"> ## What is the new behavior? Small org (≤10): all projects load and checklist works <img src="https://github.com/user-attachments/assets/9869e94c-6a6f-4d65-8550-55da58a388f2" width="500"> Large org (>10): show one checkbox <img src="https://github.com/user-attachments/assets/8420dfd1-814a-4656-acad-7fa00b088e83" width="500"> ## Additional context * Projects are fetched lazily (`enabled: isOpen`) so no unnecessary network requests occur until the delete modal is opened. * The delete guard now checks both `isLoading`, `isProjectsDataPending` and `isFetching` to cover background refetch scenarios where cached data may be stale. * Added explicit handling for the “pending but not loading” case to avoid misleading users with acknowledgement errors before projects are loaded. * Limited project fetch size to MAX_PROJECT_ACKNOWLEDGEMENTS + 1 to reduce payload and improve modal load performance. * Acknowledgement state is reset both on modal open and when the organization changes (orgSlug), ensuring consistent behavior across org switches. --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@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? Updates the tooltip copy for `public` pills in Storage. More accurate description. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Refactor** * Unified the tooltip text for "Public" buckets across the storage interface so the same explanatory message appears consistently on bucket listings, badges, and bucket pages. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Adds blog post for supabase.sh. ## Preview https://zone-www-dot-com-git-blog-supabase-ssh-supabase.vercel.app/blog/supabase-docs-over-ssh <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added a new blog post, "Supabase docs over SSH," describing SSH-based browsing of Supabase docs, agent setup commands, and navigation tips. * Updated the site RSS feed to include the new post and refreshed the feed build date. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
#44174) ## Problem Project cards on the home page showed resource exhaustion warnings twice: once as a badge in the card header, and again as an alert in the card footer. This created a confusing, redundant UI as seen when a project has disk IO, CPU, or other resource warnings active. ## Fix Removed `resourceWarnings` from the footer `ProjectCardStatus` render in `ProjectCard.tsx`. Resource exhaustion state now only appears as the header badge (which already shows a tooltip with the description on hover). Project status indicators such as paused or restarting still appear in the footer since those do not depend on resource warnings. Also removed the dead `showResourceExhaustionWarnings = false` flag from `ProjectCardStatus.tsx`, which was hardcoded to false and only gated description text that was no longer reachable. ## How to test - Navigate to the org home page with a project that has an active resource warning (disk IO, disk space, CPU, memory, or read-only mode). - Confirm the warning badge appears in the card header with the correct color (warning or critical). - Confirm no duplicate alert appears in the card footer area. - Confirm that paused or restarting projects still show the status alert in the footer. - Confirm the table view still shows the badge correctly in the status column. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes **Style** - Project status information now displays exclusively in the project card footer, removing redundant header display for a cleaner interface. - Simplified resource warning notification logic for more consistent and straightforward warning presentation. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
## Summary - Adds 6 Playwright E2E tests for queue integration: view page, create basic queue, create unlogged queue, delete queue, purge messages, and send test message - Adds `aria-label` to icon-only Purge and Delete buttons in `QueueTab.tsx` for reliable test selectors - Follows existing `cron-jobs.spec.ts` patterns for setup/teardown and API helpers ## Test plan - [x] All 6 queue integration tests pass locally against self-hosted Supabase - [x] Tests run stably in parallel (3 workers) - [x] Cleanup via `withSetupCleanup` ensures no leftover test queues
* **Chores** * Updated internal module import paths across hook files to use standardized path aliases for improved code consistency and maintainability.
## Problem - The legacy jwt settings still uses `formik` and we want to remove it in favour of `react-hook-form` to keep only one form library - The legacy jwt settings does not follow the design system guidelines ## Solution - Migrate to `react-hook-form` - Apply the design system guidelines ## How to test To test the custom JWT secret, I haven't found a better way than inverting the condition at L337 (`!legacyKey` to `legacyKey`). This allowed me to ensure the process worked at least up to the API call which fails with my local instance as legacy tokens aren't supported anymore. ## Screenshots Before: <img width="1199" height="599" alt="image" src="https://github.com/user-attachments/assets/1c6e0bb1-0698-4238-847f-d2c72adf3462" /> After: <img width="1228" height="646" alt="image" src="https://github.com/user-attachments/assets/3b2a45a9-aa43-4c3e-9653-2b2610616889" /> --------- Co-authored-by: Copilot <175728472+Copilot@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? dev-workflows => cli <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated code ownership configuration for Docker-related files. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.
14 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 : )