[pull] master from supabase:master#993
Merged
Merged
Conversation
## Details of change
Adds Snowflake to the Studio replication destination flow:
- destination selection and display
- create/edit form fields
- validate/create/update payload serialization
- generated Platform API types
Snowflake remains gated behind `etlEnableSnowflakePrivateAlpha`.
**Note:** I have configured `etlEnableSnowflakePrivateAlpha` in
ConfigCat ("all" in staging and tied to my own org id in prod).
## Details of Verification Process
- Studio focused Vitest coverage for form serialization and diagram
mapping
- Studio typecheck
- ESLint on changed Studio replication files
- Local `mise fullstack:dev` smoke test to confirm the Snowflake form
renders ok.
<img width="937" height="569" alt="image"
src="https://github.com/user-attachments/assets/8d6b3a87-1f9d-4a59-91da-be719714ea49"
/>
Full create/validate E2E depends on the Platform PR and ETL runtime
rollout.
## Review Requests
Please check the Snowflake wire payload matches the Platform/ETL
contract and that gating/edit/display behavior follows the existing ETL
destination patterns.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Snowflake added as a supported replication destination (private-alpha
gated), including UI for selecting and configuring connection and auth
(account, user, database, schema, role, private key, optional
passphrase).
* **Validation**
* Form validation and submission now handle Snowflake-specific
required/optional fields.
* **Tests**
* Unit tests added for Snowflake form behavior and replication-type
detection.
* **API**
* Destination create/update/validate flows extended to accept Snowflake
payloads.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
…6811) ## Summary Follow-up to the upgrade CTA placement experiment (#45858). The `PlanUsageCard` count metrics (Monthly active users) were abbreviated to `50k`, which reads ambiguously. This shows them in full with thousands separators (`50,000`) to match the pricing page. - `Monthly active users` row now renders e.g. `8,200 / 50,000` instead of `8.2k / 50k`. - Collapses the two count formatters (`formatCount` / `formatCountLimit`) into one `toLocaleString()` call so the current value and limit always use the same format. - GB metrics (Egress, Database size, File storage) are unchanged. ## Test plan - [ ] On the org projects page with the `org_projects_list` variant, the Monthly active users row shows full numbers (`0 / 50,000`). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Updated plan usage display formatting to show full numbers with thousands separators instead of abbreviated notation, improving clarity when viewing usage limits. <!-- 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 CLI installation guidance to recommend “global CLI usage” phrasing and link to platform-specific installation pages * Removed duplicate legacy note in the npm install guidance * Reworded CLI update guidance to state updates use the “same channels” * Expanded “Running Supabase locally” walkthrough with clear post-init steps, start instructions, and clarified credentials output * Clarified analytics schema wording from “will be stored” to “are stored” <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Before <img width="514" height="84" alt="Screenshot 2026-06-11 at 10 57 33" src="https://github.com/user-attachments/assets/7a06d713-d0f1-48b6-947a-e7c1f0716083" /> ## After <img width="490" height="78" alt="Screenshot 2026-06-11 at 10 57 54" src="https://github.com/user-attachments/assets/31bfe360-fae1-42e3-bac3-83b5648da398" />
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.
6 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 : )