[pull] master from supabase:master#690
Merged
pull[bot] merged 9 commits intocode:masterfrom Feb 19, 2026
Merged
Conversation
## Context Related to FE-2461 More refactoring to clean up usage of `useQueryStateWithSelect`, mainly in the database pages - Roles - Triggers - Functions - Enumerated Types ## To test In each of those pages, verify that - [ ] Clicking the "new" cta updates the URL params, and refreshing should re-open the sheet - [ ] Editing an existing item should update URL params, and refreshing should re-open the sheet with the right item - Verify that if the URL param has the wrong id, page should not open the sheet, show a toast, and reset the URL param - [ ] Deleting an existing item should update URL params, and refreshing should re-open the sheet with the right item - Verify that if the URL param has the wrong id, page should not open the sheet, show a toast, and reset the URL param --------- Co-authored-by: Ali Waseem <waseema393@gmail.com>
## Context In database/tables (Schema visualizer), if the schema has no tables, clicking on "Auto layout" causes a client error as we're trying to run the `dagre.layout` on a graph with 0 nodes and edges Opting to hide all actions on the Schema Visualizer if there's no tables (understandably we've been leaning towards disabled states rather than hiding, but in this case i was thinking hiding is better since that's an empty state - unless some actions were applicable in the empty state, but in this case none of the actions are) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **Bug Fixes** * Improved reliability of the database schema interface by strengthening empty state handling * Ensured database actions are properly hidden when no tables exist in the schema * **Refactor** * Consolidated schema state validation logic for better code maintainability <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Context Final clean up of `useQueryStateWithSelect` - removes the hook
## What kind of change does this PR introduce? Documentation fix ## What is the current behavior? In `apps/docs/content/guides/platform/billing-on-supabase.mdx`, the "Control your costs" link has an empty URL (`[Control your costs]()`), making it non-functional. Users clicking this link are not taken to the cost control documentation. ## What is the new behavior? The link now correctly points to `/docs/guides/platform/cost-control`, which is the existing page that covers Spend Cap, Billing Alerts, and other cost control features. ## Additional context The other two links in the same list (`Your monthly invoice` and `Manage your usage`) already have correct URLs. This appears to be an oversight where the cost-control page was created but the link in the billing overview was not updated.
…ausing (#43004) ## Context Related to this previous PR [here](#42321) Table Editor: Adding a CTA to the `HighQueryCost` UI to allow users to proceed with fetching data despite the high query cost warning, to prevent completely blocking the users from their workflows (realised that certain heavy queries are required and this safeguard shouldn't be creating dead-ends for users) <img width="1159" height="264" alt="image" src="https://github.com/user-attachments/assets/5fa01f7f-4442-4349-91f2-f4275e177f89" /> Clicking "Load more" will open a confirmation dialog, in which proceeding to load the data will thereafter suppress this preflight check for the table, for the rest of the browser session <img width="450" height="305" alt="image" src="https://github.com/user-attachments/assets/d3197a5d-a861-47a8-95da-e157972ce092" /> ## Other changes - Also bumped the query cost threshold from 100,000 to 200,000 - the former might have been too aggressive 😓 - (Unrelated) Added query cost tooltip for cron jobs high query cost warning <img width="450" height="230" alt="image" src="https://github.com/user-attachments/assets/d2c66972-7c4c-4f99-818c-e90a0991c2f5" />
## What kind of change does this PR introduce? Documentation improvement for Realtime Presence. ## What is the current behavior? The Presence documentation doesn't explain that during a `sync` event, clients may receive `join` and `leave` events simultaneously even when no users are actually joining or leaving. This can be confusing for developers new to Presence. ## What is the new behavior? Added an explanatory note clarifying that: - During `sync`, you may receive `join` and `leave` events at the same time - This is normal and expected - It reflects state reconciliation with the server, not real user movement This helps developers understand this behavior upfront rather than having to discover it through debugging. ## Additional context As mentioned in the issue, this behavior is discussed in [this community discussion](https://github.com/orgs/supabase/discussions/26748) where the solution had to be discovered by users. Fixes #41175 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Clarified behavior during sync events in the Realtime Presence guide. Added explanation that simultaneous join and leave events may occur due to state reconciliation rather than actual user movement changes. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- 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? <img width="300" height="300" alt="image" src="https://github.com/user-attachments/assets/dd39485d-0c04-43c9-bed4-bd21db0ebdcd" /> It allows you to attempt to create a branch even when that branch is used. We then get a vague error that the branch creation has failed. <img width="200" height="50" alt="image" src="https://github.com/user-attachments/assets/7d7c9d1f-93d1-4278-ac88-766bb02c5aa3" /> ## What is the new behavior? <img width="350" height="400" alt="image" src="https://github.com/user-attachments/assets/fc0562cb-4478-417b-9a1b-f192ba24076a" /> ## Additional context Add any other context or screenshots. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Prevented users from linking the same GitHub branch to multiple local branches, with clear error messages shown during both branch creation and editing. * Enhanced validation checks to ensure branch linkage uniqueness and provide real-time feedback on invalid selections. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Ali Waseem <waseema393@gmail.com>
…3010) ## Context Ensure that project's logs pages are accessible irregardless of project's status, given that logs are mutually exclusive from the project's database and doesn't require the database to be online for it to be functional. ## Other changes Mainly around simplifying some logic within ProjectLayout - Remove `disabled` prop in `SideBarNavLink` component, given that `route` prop already has a `disabled` param - Define `disabled` within `NavigationBar.utils.tsx` -> just have one place to define the "configuration" of a route - Minimize manually declaring specific routes to render specific UI (for Restore failed) - All of these can be grouped under `routesToIgnoreDBConnection` ## To test - [ ] Verify that you can access the logs page while the project is coming up - [ ] Verify that you can access the logs page on a paused project (and also use it)
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 : )