[pull] master from supabase:master #630
Merged
Conversation
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
Depends on supabase/platform#28639 ### Changes - Add entitlement check for auth.mfa_enhanced_security feature in MFA settings - Disable the "Limit duration of AAL1 sessions" toggle when user lacks entitlement - Show upgrade prompt when Enhanced MFA Security is not available on user's plan <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Enhanced MFA Security option with upgrade availability * Cloud Marketplace contract linking eligibility checks * New entitlements: SOC2 reports, Private Link, realtime concurrency controls, function limits, project-scoped roles <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Adding myself, AJ to the list ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES/NO ## What kind of change does this PR introduce? Bug fix, feature, docs update, ... ## What is the current behavior? Please link any relevant issues here. ## What is the new behavior? Feel free to include screenshots if it includes visual changes. ## Additional context Add any other context or screenshots. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated team member credits. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Context Resolves #42304 Realised that the Inline Editor behaves differently from the SQL Editor in which [`isStatementTimeoutDisabled`](#36367) is not set to true for the former which hence runs queries within a transaction. PR here sets that to true which should align the behaviour between both editors IMO though - the long term fix is just consolidating the editors so that the behaviours are the same <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * SQL statements in the editor can now execute without timeout restrictions, allowing long-running queries to complete successfully. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…42307) ## Context Clicking "Restore" on a scheduled backup shows the confirmation modal, in which the backup date does not align with what's shown on the back up row (the latter is the correct one) <img width="1812" height="292" alt="image" src="https://github.com/user-attachments/assets/7ec159af-5826-4364-8066-2de6840243dc" /> <img width="400" height="586" alt="image" src="https://github.com/user-attachments/assets/12c6f2d1-1dfb-4c90-9a79-5fa1a99dd688" /> Am opting to use the same `TimestampInfo` component in the confirmation modal - which will align the values shown in both UI <img width="578" height="350" alt="image" src="https://github.com/user-attachments/assets/54ad8b76-c535-403e-b976-41b9b1fc05bd" />
## 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? Removes Convex comparison pages from www <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Removed Supabase vs Convex comparison guide * Removed Convex from available migration solutions * Removed Convex solution information page <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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 : )