[pull] master from supabase:master#661
Merged
pull[bot] merged 6 commits intocode:masterfrom Feb 9, 2026
Merged
Conversation
…data (#42602) Issue: - When opening the peek record foreign key viewer, a full screen React error would happen Change: - Uses the preexisting formatters for the `<ReferenceRecordPeek />` component To test: - Create two tables with a foreign key reference. I did `posts <- comments` - On your "posts" table, create a column with a jsonb array column and **add at least one item to the array** - On your "comments" table, open the foreign row peek and make sure no errors occur <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Refactor** * Optimized grid component performance through improved column rendering and enhanced caching mechanisms. * Added specialized formatters for binary and JSON data types to improve display quality. * Improved memory efficiency and rendering speed, particularly when working with large datasets. * Streamlined cell rendering logic for more responsive data grids. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Context Fix missing loader in table grid editor while the rows are loading - the loading UI was rendering, but its width was 0 hence not showing up <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Style** * Improved grid layout styling to utilize full-width display configuration. * Enhanced loading skeleton container styling with better absolute positioning and spacing. * Refined empty state container layout for improved visual presentation. * **Refactor** * Removed unused internal dependencies. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Context Tiny UX behaviour that we came across - just prevents the double click action when peeking a foreign row in the table editor Feels odd that double clicking the `ReferenceRecordPeek` opens the side panel to select a new foreign row to reference <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Enhanced double-click handling to prevent unintended actions in the foreign key selection popover. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Context Related prior work was making edge functions page accessible while project is restoring - however the status of the project gets flipped to COMING_UP while it's restoring hence why the functions page was still inaccessible. ## Changes involved - Update `NavigationBar.utils` to have edge functions link to `/functions` irregardless of project status - (Unrelated) Disable (with tooltip) deploy new function CTA on edge functions page if project is not active <img width="403" height="108" alt="image" src="https://github.com/user-attachments/assets/88479247-999b-4d41-a444-6705f8c3993e" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Deploy Edge Function button now disables and shows a tooltip when the project is inactive to make deployment status clear. * **Bug Fixes** * Edge Functions link now points consistently to the functions view regardless of project build state. * **Refactor** * Consolidated project-active check and reorganized related UI wiring to standardize inactive-state handling across settings and controls. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
… incident banner dismissible (#42551) ## Context PR mainly adds a change to allow users to dismiss an incident banner Am also taking this time to consolidate `IncidentBanner` and `MaintenanceBanner` into a single component `StatusPageBanner` so that the logic for rendering either component is more clearer. ## Intended behaviour (should be covered by e2e tests) - Incident banner shows if there are incidents with impact !== 'none' - Incident banner still takes precedence over Maintanence banner (if there's both incident + maintenence events) - Dismissing the incident banner will subsequently show the maintenance banner if the maintenance hasn't been dismissed before (just to make sure that the user doesn't miss any comms) - Incident banner will not be dismissible if there's an override (via feature flag or env var) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Unified status page banner showing incident or maintenance notifications, with dismissible banners that persist across sessions; incident notices take precedence over maintenance. * **Refactor** * Replaced separate incident and maintenance banners with a single consolidated StatusPageBanner component. * **Tests** * Added end-to-end tests covering banner visibility, precedence, and dismissal behavior. <!-- 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? Quick change to the webinar metadata to highlight that the Bolt CEO will be co-hosting with us. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated event marketing materials for the 2026 Enterprise Innovation webinar with enhanced branding and messaging featuring Bolt.new. * **Style** * Code formatting improvements. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.
3 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 : )