[pull] master from supabase:master#994
Merged
Merged
Conversation
This PR improves the replication UI in the following ways: - Adds a new selecion picker for destinations which is split by the destination location and it's clearer and can scale more when we add more destinations. - Adds a much improved section on lag, highlighting new metrics that could help debug issues more easily. - Improves the copy across the whole code. - Fixes the 2d topological view of replication with better status handling. ### Screenshots <img width="1270" height="777" alt="image" src="https://github.com/user-attachments/assets/0ffc890e-2f80-47e5-bdb1-75071adda024" /> <img width="1665" height="656" alt="image" src="https://github.com/user-attachments/assets/23a27a02-acb2-4891-af95-5bc1d6ec7bfe" /> <img width="1454" height="247" alt="image" src="https://github.com/user-attachments/assets/c8799983-aa63-42b2-9370-ae4e009c1573" /> <img width="1120" height="340" alt="image" src="https://github.com/user-attachments/assets/20a18ad6-e5a9-40ec-80d4-42d6f783d868" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Live slot health indicators, legend, and connection badges. * Grouped destination type dropdown with alpha badges. * **Improvements** * Clearer UI copy for external destinations, alpha disclaimers, and onboarding flows. * Consolidated "n/a" handling for lag displays and richer metric tooltips. * Simplified replication diagram visuals and clearer table/row status/lag presentation. * Replication status responses now include expanded slot health and lag metrics. * **Tests** * New test suites covering destination selection and destination row states. <!-- 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 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated navigation links in the getting started guide to direct users to the correct documentation pages. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This PR syncs the latest troubleshooting guides from the supabase/troubleshooting repository. --------- Co-authored-by: github-docs-bot <github-docs-bot@supabase.com> Co-authored-by: Chris Chinchilla <chris.ward@supabase.io> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
- closes #46818 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Improved truncation detection in the table row editor to consider column data formats, yielding more accurate handling of JSON and array field values and avoiding incorrect truncation/skipped updates. * **Tests** * Updated and added tests to validate format-aware truncation behavior, including multidimensional array cases. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Add proper og image to studio app.
…ter group (#46849) The 'New Group' action used value `'group'` which collided with any column named `'group'`. Changed to unique sentinel `'__new_group__'`. ## How to test Create a table with the column Group ``` create table public.test_group_filter ( id bigint generated always as identity primary key, name text, "group" text ); insert into public.test_group_filter (name, "group") values ('Alice', 'admin'), ('Bob', 'member'), ('Charlie', 'guest'); ``` Try to filter on Group, it should work <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Resolved a naming collision in FilterBar where properties named "group" conflicted with the group creation action, preventing users from accurately filtering by properties with this name. * **Tests** * Added comprehensive test coverage for FilterBar's property selection and group creation features, verifying correct handling of edge cases and reserved property names. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…ses (#46830) ## 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? Closes #46829. When a cron job's command uses `jsonb_build_object(...)` header syntax, `parseCronJobCommand` captures the argument list with `([^)]*)` (stopping at the first `)`) and splits it on every `,`. A header name or value that legitimately contains a comma or parenthesis is split into the wrong pairs, shifting every following header and leaving a trailing header with an undefined value. Because the edit sheet rebuilds the command from these parsed fields, saving a job (even just changing its schedule) silently rewrites its stored headers. ## What is the new behavior? The `jsonb_build_object` argument list is parsed with a scanner that respects single-quoted SQL literals (`''` escapes) and nested parentheses, splitting only on top-level commas. Header names and values containing commas or parentheses now round-trip unchanged. Added four regression tests in `CronJobs.utils.test.ts`. ## Additional context Verified locally: `vitest` cron suite 48/48 pass (the 4 new tests fail without the fix), `tsc --noEmit` clean, ESLint clean, Prettier clean, and `next build` succeeds. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Corrected HTTP header parsing in cron jobs so header values with commas, parentheses, escaped quotes, or escape-string prefixes are preserved and don't corrupt adjacent arguments. * Ensured commas inside header values no longer swallow following body arguments. * **New Features** * Added robust SQL-literal and JSONB-argument parsing to reliably extract name/value pairs from JSONB-style headers. * **Tests** * Added tests covering complex header value cases and whitespace/escaping edge cases. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
## 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? Closes #46824 In the Studio table editor, when inserting a new row into a table with an auto-generated primary key (or any non-text column with a default value), clearing the field after editing it sends an empty string `""` in the insert payload. This causes Postgres to reject the insert with: ```txt ERROR: 22P02: invalid input syntax for type bigint: "" ``` ## What is the new behavior? When inserting a new row, cleared fields that are identity/default-backed and non-text are now omitted from the insert payload, so Postgres applies the column default or identity generation instead of receiving an empty string. For example: - id bigint generated by default as identity cleared → omitted, Postgres auto-generates id. - created_at timestamptz default now() cleared → omitted, Postgres applies now(). - name text cleared → preserved as "", because empty string is a valid explicit text value. ## Additional context After the fix: https://github.com/user-attachments/assets/78e9eb9c-9518-4894-8547-d18ffa78869a <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * New-record saving now respects column defaults and identity behavior: empty inputs for identity or defaulted non-text columns are omitted so defaults are applied, while intentional empty strings for text fields are preserved. * **Tests** * Added test coverage validating new-row creation behavior with default/identity handling and empty-text preservation. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Ali Waseem <waseema393@gmail.com>
## Problem We lost the button focus state design while migrating to tailwind v4 See https://supabase.com/design-system/docs/components/button and move to each buttons with the _Tab_ key. ## Solution Restore it. ## How to test - Open https://design-system-git-fix-button-focus-state-supabase.vercel.app/design-system/docs/components/button - Move to each buttons with the _Tab_ key. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Style** * Updated Button component styling for improved layout, typography, and transitions. * Refined focus state and outline styling for better visual consistency. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…ost (#46853) The Supabase Studio blog post (`/blog/supabase-studio`) receives a high volume of visits but contains outdated information from its original 2021 publish date. This PR makes minimal surgical fixes — no rewriting. ## Changes **Broken links (4 fixes)** — the repo was reorganised into a monorepo and `/studio` moved to `/apps/studio`: - Opening sentence link - "Build in public" section link - Tech stack `package.json` link - "How to contribute" section link **Stale text removed:** - `(Saved queries are unavailable for now)` — saved queries have been available for years - `Over time we'll expose a lot more of the codebase in the self-hosted Dashboard, this was as much as we could do for this Launch Week!` — the promise has been fulfilled, leaving it implies Studio is still a stub <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated Supabase Studio blog post with refreshed feature highlights emphasizing Table & SQL editors, database management, and API documentation. * Corrected internal repository and deployment links to point to the current studio location. * Removed outdated notes about unavailable features and an obsolete paragraph following the feature list. * Kept the existing Product Hunt section intact. <!-- 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? Adds a one time banner to the `<BannerStack />` to promote Unified Logs becoming available. This also fixes the `<BannerStack />` components issue with stacking varying height banners. https://github.com/user-attachments/assets/40f02709-0d67-43a9-ab95-750d9a4a582a <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added a dismissible "Unified Logs" banner with an animated sample-log carousel, CTA to Unified Logs, and a preview/enable flow for non-enabled users. Dismissal is persisted locally and telemetry is recorded for CTA and dismiss actions; banner appears only for eligible projects. * **Refactor** * Banner stack UI updated to display a single front banner with animated "peek" slivers and refined hover/animation behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
github-actions
Bot
added
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.
11 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 : )