[pull] master from supabase:master#737
Merged
pull[bot] merged 10 commits intocode:masterfrom Mar 9, 2026
Merged
Conversation
## Context Taking a slightly different approach to [this PR](#43370) Original problem was that if you opened some folders while in a bucket and then switched to a different bucket, the folder UI will persists (folders from Bucket A will render when landing on Bucket B) ## Changes involved - Shift `StorageExplorerStateContextProvider` into `[bucketId].tsx]` instead of `ProjectContext` - The valtio store here only applies for the storage explorer so having it so high in the project's context was unnecessary - This also just implies that the valtio store will automatically reset whenever the bucket changes - Simplify storage explorer valtio store by initializing the store with the bucket - We'll initialize the selected bucket with the store now (Same as previous PR) - Removes unnecessary `setSelectedBucket` method which required a separate `useEffect` in `StorageExplorer.tsx` ## To test - [ ] Verify that the original is resolved - [ ] General smoke test of the storage explorer - i've also re-added the e2e test that Gildas wrote up in his PR
## What kind of change does this PR introduce? - UI fix ## What is the current behavior? - The _New project_ button overflows to the right on smaller (phone-sized) breakpoints - Due to addition of _Sort by_ dropdown last week ## What is the new behavior? - All actions now wrap on smaller breakpoint | Before | After | | --- | --- | | <img width="393" height="852" alt="Supabase-383C523F-0BF1-48CD-8052-F6D68301DA4E" src="https://github.com/user-attachments/assets/3983a815-16ff-48cd-857f-b84b82bfc923" /> | <img width="393" height="852" alt="Supabase-ED7AD923-E837-4D48-B7D1-6DA3C6E45BFA" src="https://github.com/user-attachments/assets/fe19f9cc-f832-4c5d-b412-0aa1a0c16d5b" /> |
#43530) ## 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? Currently, the SMTP Host input field in the Project Dashboard (Authentication > Email > SMTP Settings) does not sanitize whitespace. If a user accidentally pastes a hostname with leading or trailing spaces (e.g., " smtp.resend.com "), the DNS lookup fails during the OTP delivery process. This results in the following error in the Auth logs: ```"dial tcp: lookup smtp.resend.com on 127.0.0.53:53: server misbehaving"``` Noticed, the other input fields of Sender details and Host, Username and Password under SMTP Provider settings take leading and trailing whitespaces as well. ## What is the new behavior? Input sanitization has been applied across the SMTP configuration schema. The following fields now utilize .trim() to ensure data integrity: - SMTP_HOST - SMTP_ADMIN_EMAIL & SMTP_SENDER_NAME - SMTP_USER - SMTP_PASS ## Screenshots: Before Fix: <img width="604" height="198" alt="Screenshot 2026-03-09 at 2 04 49 AM" src="https://github.com/user-attachments/assets/76ae23a6-3ad8-4f82-8f0f-ab12f4168e81" /> After Fix: <img width="594" height="194" alt="Screenshot 2026-03-09 at 1 58 48 AM" src="https://github.com/user-attachments/assets/03f64294-0bfe-4fca-a82b-12ee07a6d218" /> This fixes the issue #43529 --------- Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
## What kind of change does this PR introduce? - Resolves FE-1960 - Resolves FE-1983 - Resolves DEPR-207 ## What is the current behavior? Page titles between surfaces are inconsistent and vague. Sometimes they say the product name: ``` My Project | My Org | Supabase ``` ...even when on a specific surface like Database > Tables. Other times they show the entity name but skip over the project or org name : ``` Edge Functions | Supabase ``` ## What is the new behavior? Page titles *mostly* (see below) follow the same format: ``` users | Table Editor | My Project | My Org | Supabase hello-world | Logs | Edge Functions | My Project | My Org | Supabase Backups | Database | My Project | My Org | Supabase Authentication | My Project | My Org | Supabase ``` That format is: entity, section, surface, project, org, brand ## Additional context This is stacked PR 1/5 for page title improvements. Includes the core title utility and ProjectLayout integration/tests. Follow-up stacked PRs are based on this branch: - #43534 - #43535 - #43536 - #43537 This one should be merged first. The others (listed right above) can _then_ be merged in any order.
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES
## 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? doc update ## What is the current behavior? Error description states that realtime breaks when a message is JSON parsable. Should state when it is "not" JSON parsable ## What is the new behavior? Added not key word to description: ``` Payload sent in NOTIFY operation was "NOT" JSON parsable. ```
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.
7 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 : )