[pull] master from supabase:master#980
Merged
Merged
Conversation
Extracts the Cancellation Flow from the subscriptions side panel and adds a new button that initiates the flow (old journey is still possible): (screenshots see below) Verified manually: - ✅ confirmed the old downgrade flow works, Team -> Pro; Pro -> Free - ✅ confirmed the new downgrade flow works - ✅ button does not show up when on free plan; no flicker - ✅ button does not show up on enterprise/platform plan - ✅ verified button is disabled when managed by AWS marketplace (hardcoded in `useSelectedOrganizationQuery`) - ✅ verified button is disabled if `canUpdateSubscriton` is false, hardcoded in `useAsyncCheckPermissions` - ✅ modal for exceeding-free-projects shows up <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added a guided subscription cancellation flow with confirmation steps, member/usage checks, and an exit survey. * Exposed a visible "Cancel Subscription" control in billing settings, enabled/disabled with contextual tooltip messaging. * **Improvements** * Downgrade/exit survey confirm action can be disabled when appropriate; exit survey confirm label updated to "Downgrade Now". * **Chores** * Added frontend telemetry for cancellation button interactions. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…46653) ## 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? Docs update ## What is the current behavior? Currently, this doc outlines how to restore a dashboard backup which only applies to projects that still use logical backups. Newer projects cannot follow this process. ## What is the new behavior? Adds an admonition to direct users with projects that use physical backups to the correct guide. Keeping the legacy guide content for now for older projects that may still be using logical backups. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added clarification that dashboard backups are only available for Supabase projects using logical backups. Projects using physical backups are directed to refer to the CLI backup and restore guide instead. <!-- 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? New landing page for an upcoming webinar with Perplexity. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * New webinar event now available: "Workflows That Scale: Supabase + Perplexity Computer for Small Businesses" with event details, agenda, speaker information, and registration link. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Problem In the Logs Explorer, clicking the Run button after editing the SQL did not execute the latest query. It ran a stale version. Pressing Cmd+Enter ran the correct, latest query. The Run button's handler read the query from the `editorValue` React state, which can lag behind the most recent keystroke. Cmd+Enter works because Monaco's keybinding reads the live value directly off the editor instance. ## Fix `handleRun` now reads the live value from the editor instance (`editorRef.current.getValue()`), falling back to `editorValue`. This makes the Run button consistent with the Cmd+Enter keybinding. ## How to test - Open the Logs Explorer (Project > Logs > query/explorer). - Type or edit a SQL query in the editor. - Without clicking elsewhere, click the Run button. - Expected result: the query that runs reflects your latest edit, matching the behavior of Cmd+Enter. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Fixed an issue in the logs explorer where SQL queries would not execute with the most recent code changes you've typed. The query runner now uses the latest content from the editor to ensure your most recent edits are run. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
github-actions
Bot
added
the
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 : )