[pull] master from supabase:master#709
Merged
pull[bot] merged 5 commits intocode:masterfrom Feb 26, 2026
Merged
Conversation
## What kind of change does this PR introduce? - Feature - Resolves DEPR-355 ## What is the current behavior? Only one email address can be invited to an organization at a time. ## What is the new behavior? - Multiple email addresses can be invited (at a single scope) to an organization at one time - List of email addresses detected via comma-separation - Pluralization on fields and labels - Table and copywriting cleanup | Before | After | | --- | --- | | <img width="808" height="691" alt="Supabase" src="https://github.com/user-attachments/assets/f6450c26-968c-4ee8-bb7c-d6f6a3af1209" /> | <img width="808" height="691" alt="8298" src="https://github.com/user-attachments/assets/2d7e3869-b9d4-4a4f-89aa-ae55d67e794b" /> | | <img width="1024" height="560" alt="Supabase" src="https://github.com/user-attachments/assets/9a255167-fcd3-4294-ba3a-9160bd500cff" /> | <img width="1024" height="560" alt="Supabase" src="https://github.com/user-attachments/assets/daba5bb8-eb12-43dc-86de-217e9baf0b72" /> | <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added support for inviting multiple team members simultaneously via comma-separated emails. * **Improvements** * Enhanced member management interface with clearer status indicators (You, Invited, SSO, MFA enabled/disabled). * Improved feedback messages for invitation outcomes and member status changes. * Updated member table layout with summary footer displaying member count. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Context Adjust advisor panel to not show "Project required" UI for the "All" panel since messages do not require to be in a specific project <img width="434" height="251" alt="image" src="https://github.com/user-attachments/assets/8a999ca7-1a81-4c63-a6f7-c73cbdd676e3" /> Also adjusts the red dot for advisor center button to show if there's critical notifications
…rage Explorer (#43086) ## Context Renaming folders on the Storage Explorer has a tendency to be flaky as we're using the `POST /objects/move` storage API to move files to the renamed folder which handles one file per request. For a big folder (e.g 100+ files), users will easily hit rate limits and run into 429s with the API, in which the current behaviour just shows toast errors as the error handler, leaving an odd state upon running through every file in the folder where some files are in the old folder, and others in the new one ## Changes involved Main solution is to implement an automatic retry logic for `renameFolder`, but changes involved are: - Remove batching logic for renaming folders (Which fires `n` requests per batch) - The batch logic was negligible anyways since our batch size was only 2 😅 - Instead we now handle moving of files sequentially - If a file runs into an error during the `POST` request, retry the request after `n` seconds - If the error was a 429, retry after 60 seconds, otherwise just 5 seconds - Will attempt the request for a total of 3 times - Toast progress description will also be updated to show the message (timer will also count down to keep the UI interactive and not look stuck) <img width="362" height="98" alt="image" src="https://github.com/user-attachments/assets/52ba685a-2f35-42f1-8fcf-98351184fd56" /> - After the whole process is completed, if any file ran into an error, toast description will add a CTA to retry the rename ## Demo https://github.com/user-attachments/assets/d65b3c22-f9f8-4984-9521-6fc83a69f82e ## To test Have a folder in your project's storage bucket with 100+ files (can stress test with nested folders) - [ ] Verify that you can rename the folder, and the dashboard automatically handles errors
…unhealthy + project status is coming up (#43117) ## Context With the new home page, we have a stat to show the overall status of the project + individual service health, both of which data is pulled from an endpoint <img width="283" height="400" alt="image" src="https://github.com/user-attachments/assets/c7cbfdc6-b46b-41ce-9a89-59a3df98b586" /> At the time of project creation, some of the services start of as UNHEALTHY, which results in the status stat here showing a label of "Unhealthy" (while accurate in the sense that we're showing what's coming from the API, its inaccurate as the services are still spinning up) ## Changes involved For each service, am opting to show their status as "COMING_UP" if the service status is UNHEALTHY + the project's status is COMING_UP or UNKNOWN. The overall status label should also show "Coming up" if the project's status is COMING_UP or UNKNOWN as well
## Context Should've removed the `status` prop when fetching notifications in `AdvisorButton` for a more accurate indication of `hasCriticalNotifications` as we should show that dot for read critical notifications too (not just new)
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.
2 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 : )