[pull] master from supabase:master#733
Merged
pull[bot] merged 12 commits intocode:masterfrom Mar 6, 2026
Merged
Conversation
fixes feature preview showing disabled features by flag. ## to test - go to feature previews - should not see unified logs
## 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? Small docs update to troubleshooting guide. Adds circuit breaker error to list of related errors that troubleshooting guide addresses.
## 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? Add my name to humans.txt ## What is the current behavior? n/a ## What is the new behavior? n/a ## Additional context n/a Co-authored-by: Cam Michie <cammichie@Cams-MacBook-Pro-2.local>
### Changes
- Replace plan-based checks (`LOG_RETENTION`, `availableIn`) with
`useCheckEntitlements('log.retention_days')` in the chart interval
dropdown
- `ChartIntervalDropdown` now calls the entitlements hook internally
instead of receiving plan props
- Remove `LOG_RETENTION` constant and `availableIn` from
`CHART_INTERVALS`
- Update consumer components (`ProjectUsage`, `ProjectUsageSection`,
`ObservabilityOverview`) to remove plan prop passing
### Testing
- Head to `/project/_/observability` with a Free plan org.
- Click on the time selector "Last 7 days" is disabled, default is "Last
60 minutes", tooltip shows retention limit and upgrade link
<img width="827" height="151" alt="image"
src="https://github.com/user-attachments/assets/20988398-8f0a-46b6-be3d-af4e9d530f81"
/>
- With a Pro Org and above the "Last 7 days" option should be enabled
Allows users to select logs and copy their contents for debugging, or pass them on to assistant with one click. ## To test - go to logs or log explorer - select some logs - try copying as json, markdown, or sending it to assistant.
…ings (#43280) Adds a feature flagged exposed tables config to postgrest settings: <img width="1158" height="589" alt="Screenshot 2026-03-02 at 17 04 13" src="https://github.com/user-attachments/assets/8fa8ab81-0bfa-4781-83bc-80ac52e180f8" /> To test: - make sure the existing (feature flag off) settings work as expected - make sure exposing and removing schemas works in the new mode - make sure exposing and removing tables works in the new mode - ideally try with a lot of tables to check search and infinite scroll work as expected - try exposing a schema without any tables (like `graphql_public`) and make sure it doesn't get removed randomly when editing tables - try with a table with custom permissions (for example `REVOKE SELECT ON public.posts FROM anon;`) and make sure the user is informed with the tooltip --------- Co-authored-by: Nick Babadzhanian <33933459+pgnickb@users.noreply.github.com>
This PR removes a duplicate `nz_gst` entry from the tax ID types list. **Testing** <img width="1217" height="614" alt="Screenshot 2026-03-06 at 5 25 38 PM" src="https://github.com/user-attachments/assets/2895ddbd-d124-4ee3-9135-2c08d6f1b0b3" />
## 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? Studio > Database > Schema Visualizer ## What is the current behavior? If a table has a description value then the value does not show on the visualizer ## What is the new behavior? <img width="393" height="243" alt="Screenshot 2026-03-04 at 19 09 47" src="https://github.com/user-attachments/assets/fcd61ecb-c1b8-4408-b753-62cc1d136c69" /> ## Additional context Closes #36072
### Changes - Replaces the isPaid plan-based check on the "Prevent use of leaked passwords" (PASSWORD_HIBP_ENABLED) setting with a proper entitlement check using the `password_hibp` entitlement key - Adds a new `useHasEntitlementAccess` hook that returns a reusable checker function for any entitlement key, backed by the same cached entitlements query ### Testing - Head to `/project/_/auth/providers?provider=Email` with an Org on the Free Plan - Assert that the "Prevent use of leaked passwords" toggle is disabled. - Head to `/project/_/auth/providers?provider=Email` with an Org on the Pro Plan - Assert that the "Prevent use of leaked passwords" toggle is enabled and can be toggled and saved. <img width="612" height="496" alt="image" src="https://github.com/user-attachments/assets/fc1ccc79-016c-4265-96ac-bdb458d2a8de" />
## Context Small adjustments to wildcard routes - Header logo to be consistent with other layouts - Before: <img width="463" height="172" alt="image" src="https://github.com/user-attachments/assets/217bb9d8-d4f9-4482-8c40-5f0c49afeee6" /> - After: <img width="523" height="229" alt="image" src="https://github.com/user-attachments/assets/707dd541-f0ab-4023-ba25-e244eb7c3e7a" /> - Project wildcard route list view to be consistent with org/[slug] page - project list shouldn't take full height if there's no need to, scroll behaviour should be on the page - Before: <img width="1224" height="868" alt="image" src="https://github.com/user-attachments/assets/6ff9f8a3-9f68-40a0-9a0b-e60fbef603cd" /> - After: <img width="1230" height="477" alt="image" src="https://github.com/user-attachments/assets/91d65969-9457-49f9-9ce2-d3befc4576ad" /> Co-authored-by: Ali Waseem <waseema393@gmail.com>
…40691) JSON column viewer looks fine on dark mode, but barely visible on light mode, especially when the value is of string type. There are no colors that can satisfy the 4.5:1 contrast ratio (minimum requirement for web and digital accessibility) on both white and black background, so I had to pick different classes for ight mode (dark mode is fine, I checked the colors against the dark background and the contrast is good). Even though the new colors may not look that contrasting to each other, I prioritized accessibility, and made sure they all complied with the 4.5:1 contrast ratio. Before: <img width="499" height="179" alt="112" src="https://github.com/user-attachments/assets/7f0821cf-6127-4246-a2c2-a78a5d31083a" /> After: <img width="499" height="211" alt="222" src="https://github.com/user-attachments/assets/0b5b2c35-9211-4a25-a9f5-eef4e5c8c8f3" /> Fixes #40633 --------- Co-authored-by: Ali Waseem <waseema393@gmail.com>
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.
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 : )