[pull] master from supabase:master#706
Merged
pull[bot] merged 6 commits intocode:masterfrom Feb 25, 2026
Merged
Conversation
…iting a cron job (#43138) ## Problem Finding a specific edge function is cumbersome when you have many of then. ## Solution Use a combobox instead of a select to allow filtering ## How to test - Enable the cron extension - Enable the pg_net extension - Create a few edge functions - Create a new cron job and select _Supabase edge functions_ You should be able to: - select/unselect an edge function - filter the list to reduce the number of edge functions displayed
#43034) Fixes #42192 Replaces the deprecated `getSession` call with `getClaims` in the SolidJS tutorial documentation (`with-solidjs.mdx`). Changes: - `supabase.auth.getSession()` → `supabase.auth.getClaims()` - `data.session` → `data.claims` This follows the recommended migration pattern per the Supabase auth docs, and is consistent with the same fix applied to the Refine tutorial in #43006. --------- Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
…43167) ## Context Since moving notifications to the Advisors Panel, we've been sending `org_slug` and `project_ref` to the GET notifications endpoint, which resulted in certain notifications not being returned such as those that are user specific (no org slug nor project ref) Am opting to remove both slug and ref filters for the notifications as the notifications should be on a user level (irregardless if you're within a project or not) - the Advisor's Panel's button in the layout header would also suggest that notifications in there are not tied to an org or project ## To test This one's a bit tricky to test unless you have notifications on staging, but i've double checked on prod with a curl command that removing the org slug and project ref filters returns the correct notifications
## What kind of change does this PR introduce? UI improvement ## What is the current behavior? The session expired dialog is quite hard to parse when, for most people, the ask is simple. ## What is the new behavior? Improved session expired dialog: - Refactored to use AlertDialog - Clarified copywriting - Uses the new AlertCollapsible to hide all the complicated debugging steps under a toggle - This component is documented in the design-system | Before | After | | --- | --- | | <img width="1024" height="563" alt="Supabase-B1728A05-DDD2-4A50-AED4-D62EAA2E7D7C" src="https://github.com/user-attachments/assets/771f85d8-21ea-42b5-99f5-b9b05f5617dd" /> | <img width="1024" height="563" alt="Storage Supabase" src="https://github.com/user-attachments/assets/b2fcab68-fb29-4cb9-bd42-aecc57b9fa32" /> | | <img width="1024" height="563" alt="Supabase-B1728A05-DDD2-4A50-AED4-D62EAA2E7D7C" src="https://github.com/user-attachments/assets/771f85d8-21ea-42b5-99f5-b9b05f5617dd" /> | <img width="1024" height="563" alt="Storage Supabase" src="https://github.com/user-attachments/assets/babd3711-5fdf-43b9-be06-d96268a191fd" /> | ## To test In apps/studio/hooks/misc/withAuth.tsx: ```diff - const [isSessionTimeoutModalOpen, setIsSessionTimeoutModalOpen] = useState(false) + const [isSessionTimeoutModalOpen, setIsSessionTimeoutModalOpen] = useState(true) // Mocked as true for UI testing ``` --------- Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
## What kind of change does this PR introduce? UI update ## What is the current behavior? - The vast majority of projects now have physical backups, not logical - Physical backups are not downloadable - But we show a disabled `Download` button for each physical backup - This button has confusing multi-step instructions about `pg_dump` that are [inaccurate](https://supabase.slack.com/archives/C02BJ2239GA/p1771979586829419?thread_ts=1771887878.203199&cid=C02BJ2239GA) ## What is the new behavior? - We only show the (enabled) `Download` button for logical backups | Before | After | | --- | --- | | <img width="1024" height="563" alt="AWS Healthy Toolshed Supabase-6FE7C23F-29D6-47B6-819A-84BC49927F3A" src="https://github.com/user-attachments/assets/167441bf-3ead-4c86-89df-60ab89ce8b98" /> | <img width="1024" height="563" alt="AWS Healthy Toolshed Supabase-C9E763B7-B447-468E-B928-BB9AD5ABC588" src="https://github.com/user-attachments/assets/3fccdf12-ba4e-424a-87ae-2294f1a3b7b1" /> | ## Additional context Support believes removing the button entirely will have less of a burden than a better tooltip explanation.
## 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? Chore / dead code removal ## What is the current behavior? The `apps/docs/components/Flag/` directory contained legacy feature flag code that was never wired up: - `FlagProvider.tsx` — all ConfigCat logic commented out; only wraps children in an empty context - `FlagContext.ts` — an empty `createContext({})` with no values ever set - `Flag.tsx` — a gate component that reads from the above empty context, so flags always evaluate to falsy - `hooks/useFlag.ts` — references the dead local `FlagContext` instead of `common`'s `FeatureFlagContext` The docs app already uses `FeatureFlagProvider` from the `common` package (configured in `apps/docs/features/app.providers.tsx`), making this entire local implementation obsolete. Closes [GROWTH-611](https://linear.app/supabase/issue/GROWTH-611/clean-up-deadlegacy-flag-code-in-docs-app) ## What is the new behavior? The dead code is removed: - `apps/docs/components/Flag/` directory deleted - `apps/docs/hooks/useFlag.ts` deleted Any code needing feature flags should import `useFlag` directly from `common`. ## Additional context No flag-gated features were affected — the old local implementation was non-functional (context always resolved to `{}`), so removing it has no behavioral impact.
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.
5 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 : )