-
) : (
@@ -182,11 +178,7 @@ export const DestinationTypeSelection = () => {
{group.options.map((option) => (
-
{option.label}
diff --git a/apps/studio/components/interfaces/Database/Replication/DestinationRow.tsx b/apps/studio/components/interfaces/Database/Replication/DestinationRow.tsx
index a8498f19a8e..8b553a625c5 100644
--- a/apps/studio/components/interfaces/Database/Replication/DestinationRow.tsx
+++ b/apps/studio/components/interfaces/Database/Replication/DestinationRow.tsx
@@ -15,7 +15,7 @@ import {
import { ShimmeringLoader } from 'ui-patterns/ShimmeringLoader'
import { DeleteDestination } from './DeleteDestination'
-import { DestinationIcon } from './DestinationIcon'
+import { DestinationLogo } from './DestinationLogo'
import { PipelineStatus } from './PipelineStatus'
import { PipelineStatusName, STATUS_REFRESH_FREQUENCY_MS } from './Replication.constants'
import { getFormattedLagValue } from './ReplicationPipelineStatus/ReplicationPipelineStatus.utils'
@@ -149,11 +149,7 @@ export const DestinationRow = ({ destinationId }: DestinationRowProps) => {
)}
{isPipelineSuccess && (
-
- {type ? (
-
+ {type ?
{isPipelineLoading ? (
diff --git a/apps/studio/components/interfaces/Database/Replication/Destinations.tsx b/apps/studio/components/interfaces/Database/Replication/Destinations.tsx
index a37139e5f1e..c2cc0cc96f0 100644
--- a/apps/studio/components/interfaces/Database/Replication/Destinations.tsx
+++ b/apps/studio/components/interfaces/Database/Replication/Destinations.tsx
@@ -277,7 +277,7 @@ export const Destinations = () => {
diff --git a/apps/studio/components/interfaces/Database/Replication/Destinations.tsx b/apps/studio/components/interfaces/Database/Replication/Destinations.tsx
index 2ae5b186ef3..1516ae4b5aa 100644
--- a/apps/studio/components/interfaces/Database/Replication/Destinations.tsx
+++ b/apps/studio/components/interfaces/Database/Replication/Destinations.tsx
@@ -15,7 +15,6 @@ import {
DropdownMenuTrigger,
Table,
TableBody,
- TableCell,
TableHead,
TableHeader,
TableHeadSort,
@@ -42,6 +41,7 @@ import {
import { useRedirectLegacyReadReplicaDestination } from './useRedirectLegacyReadReplicaDestination'
import { AlertError } from '@/components/ui/AlertError'
import { Shortcut } from '@/components/ui/Shortcut'
+import { TableRowNoResults } from '@/components/ui/TableRowNoResults'
import { useReplicationDestinationsQuery } from '@/data/replication/destinations-query'
import { replicationKeys } from '@/data/replication/keys'
import {
@@ -404,16 +404,7 @@ export const Destinations = () => {
{!isDestinationsLoading &&
filteredDestinations.length === 0 &&
- hasDestinations && (
-
-
-
-
- )}
+ hasDestinations &&
)}
{entities.length === 0 && filterString.length > 0 && (
-
-
-
-
+
-
-
-
- )
- }
-
if (orderedTriggers.length === 0 && (filterString.length > 0 || ownerFilter.length > 0)) {
- return (
-
-
-
-
- )
+ return
-
-
-
- )
+ return
-
-
-
+
{analyticsBuckets.length === 0 && filterString.length > 0 && (
-
-
-
-
+
-
-
-
- )
-}
-
type BucketTableRowProps = {
mode: BucketTableMode
bucket: Bucket
diff --git a/apps/studio/components/interfaces/Storage/BucketsPickerDialog/BucketsTable.tsx b/apps/studio/components/interfaces/Storage/BucketsPickerDialog/BucketsTable.tsx
index a73e9f3c7ef..19b36cbc940 100644
--- a/apps/studio/components/interfaces/Storage/BucketsPickerDialog/BucketsTable.tsx
+++ b/apps/studio/components/interfaces/Storage/BucketsPickerDialog/BucketsTable.tsx
@@ -3,8 +3,9 @@ import { Table, TableBody } from 'ui'
import { LoadMoreRow } from './BucketsTable.LoadMoreRow'
import { BucketTableHeader } from './BucketTableHeader'
-import { BucketTableEmptyState, BucketTableRow } from './BucketTableRow'
+import { BucketTableRow } from './BucketTableRow'
import type { AllowedBucketType, BucketsTablePaginationProps } from './types'
+import { TableRowNoResults } from '@/components/ui/TableRowNoResults'
import { VirtualizedTable, VirtualizedTableBody } from '@/components/ui/VirtualizedTable'
import { type Bucket } from '@/data/storage/buckets-query'
@@ -47,7 +48,11 @@ const BucketsTableUnvirtualized = ({
0} />
{showSearchEmptyState ? (
-
-
-
-
- )
+ if (mode === 'standard') {
+ return (
+
+
+
+
+ )
+ }
}
type BucketTableRowProps = {
diff --git a/apps/studio/components/interfaces/Storage/FilesBuckets/BucketsTable.tsx b/apps/studio/components/interfaces/Storage/FilesBuckets/BucketsTable.tsx
index 6cedc17b17b..be21a3782a5 100644
--- a/apps/studio/components/interfaces/Storage/FilesBuckets/BucketsTable.tsx
+++ b/apps/studio/components/interfaces/Storage/FilesBuckets/BucketsTable.tsx
@@ -3,7 +3,8 @@ import { Table, TableBody } from 'ui'
import { LoadMoreRow } from './BucketsTable.LoadMoreRow'
import type { BucketsTablePaginationProps } from './BucketsTable.types'
-import { BucketTableEmptyState, BucketTableHeader, BucketTableRow } from './BucketTable'
+import { BucketTableHeader, BucketTableRow } from './BucketTable'
+import { TableRowNoResults } from '@/components/ui/TableRowNoResults'
import { VirtualizedTable, VirtualizedTableBody } from '@/components/ui/VirtualizedTable'
import { Bucket } from '@/data/storage/buckets-query'
@@ -15,8 +16,16 @@ type BucketsTableProps = {
pagination: BucketsTablePaginationProps
}
+// [Joshen] To investigate: There's a lot of duplicate logic + components between
+// this FilesBuckets/BucketsTable and BucketsPickerDialog/BucketsTable. Check separately
+// if they can be cleaned up and consolidated. The latter should take precedence as it aims to
+// reduce footprint on the giant StorageExplorerState.
+
export const BucketsTable = (props: BucketsTableProps) => {
+ // [Joshen] To investigate: Can't we just default to virtualized?
+ // Do we need to dynamically decide whether to use a virtualized or unvirtualized one?
const isVirtualized = props.buckets.length > 50
+
return isVirtualized ? (
0} />
{showSearchEmptyState ? (
-
{filteredList.length === 0 ? (
-
-
- {filterString.length > 0 ? (
- <>
-
-
+
+ {filterString.length === 0 ? (
+ <>
+
) : (
filteredList.map((index, idx: number) => {
const id = `index-${idx}`
@@ -225,6 +221,7 @@ export const VectorBucketDetails = () => {
}
onClick={(e) => e.stopPropagation()}
diff --git a/apps/studio/components/interfaces/Storage/VectorBuckets/index.tsx b/apps/studio/components/interfaces/Storage/VectorBuckets/index.tsx
index ffb23a83cd3..492168504f1 100644
--- a/apps/studio/components/interfaces/Storage/VectorBuckets/index.tsx
+++ b/apps/studio/components/interfaces/Storage/VectorBuckets/index.tsx
@@ -16,6 +16,7 @@ import { CreateBucketButton } from '../NewBucketButton'
import { CreateVectorBucketDialog } from './CreateVectorBucketDialog'
import { VectorBucketsErrorState } from './VectorBucketsErrorState'
import { AlphaNotice } from '@/components/ui/AlphaNotice'
+import { TableRowNoResults } from '@/components/ui/TableRowNoResults'
import { useVectorBucketsQuery } from '@/data/storage/vector-buckets-query'
import { createNavigationHandler } from '@/lib/navigation'
@@ -107,14 +108,11 @@ export const VectorsBuckets = () => {
{filteredBuckets.length === 0 && filterString.length > 0 && (
-
-
-
-
+ ) => {
+ return (
+
+
+ {children ?? (
+ <>
+
+
+ )
+}
diff --git a/apps/studio/pages/project/[ref]/functions/index.tsx b/apps/studio/pages/project/[ref]/functions/index.tsx
index 994374b978b..a84ec48ffe1 100644
--- a/apps/studio/pages/project/[ref]/functions/index.tsx
+++ b/apps/studio/pages/project/[ref]/functions/index.tsx
@@ -3,7 +3,7 @@ import { ExternalLink, RefreshCw, Search, X } from 'lucide-react'
import { useRouter } from 'next/router'
import { parseAsString, parseAsStringLiteral, useQueryState } from 'nuqs'
import React, { useMemo, useRef, type PropsWithChildren } from 'react'
-import { Button, Card, Table, TableBody, TableCell, TableHead, TableHeader, TableRow } from 'ui'
+import { Button, Card, Table, TableBody, TableHead, TableHeader, TableRow } from 'ui'
import { Admonition } from 'ui-patterns/Admonition'
import { Input } from 'ui-patterns/DataInputs/Input'
import { PageContainer } from 'ui-patterns/PageContainer'
@@ -35,6 +35,7 @@ import EdgeFunctionsLayout from '@/components/layouts/EdgeFunctionsLayout/EdgeFu
import { AlertError } from '@/components/ui/AlertError'
import { DocsButton } from '@/components/ui/DocsButton'
import { ShortcutTooltip } from '@/components/ui/ShortcutTooltip'
+import { TableRowNoResults } from '@/components/ui/TableRowNoResults'
import { useEdgeFunctionsQuery } from '@/data/edge-functions/edge-functions-query'
import { useIsProjectActive } from '@/hooks/misc/useSelectedProject'
import { DOCS_URL, IS_PLATFORM } from '@/lib/constants'
@@ -145,6 +146,7 @@ const EdgeFunctionsPage: NextPageWithLayout = () => {
actions={[
search && (
From c52fca134028dfd993e2871d19f1ba84f6d67d86 Mon Sep 17 00:00:00 2001
From: Gildas Garcia <1122076+djhi@users.noreply.github.com>
Date: Wed, 16 Sep 2026 10:46:07 +0200
Subject: [PATCH 084/107] MFA Recovery codes: enforce recovery codes generation
after setting up an MFA (#50343)
## What kind of change does this PR introduce?
Afters users set up an MFA, automatically generate recovery codes
## How to test
- On an account that doesn't have recovery codes generated yet, add a
new MFA
- When you finished verifying the MFA, it should automatically open the
recovery codes modal introduced in previous PRs
## Summary by CodeRabbit
- **Bug Fixes**
- Improved the two-factor authentication setup flow by checking the
latest recovery-code enrollment status before generating codes.
- Recovery codes are now generated and displayed after verification when
they are enabled but not yet enrolled.
- Loading indicators now reflect recovery-code status checks, providing
clearer feedback during setup.
- **Improvements**
- Updated the recovery-code confirmation message to explain how codes
can restore access after losing access to an MFA app and remind users to
store them securely.
---
.../Account/TOTPFactors/AddNewFactorModal.tsx | 35 +++++++++++++++++--
.../TOTPFactors/RecoveryCodesModal.tsx | 5 ++-
2 files changed, 36 insertions(+), 4 deletions(-)
diff --git a/apps/studio/components/interfaces/Account/TOTPFactors/AddNewFactorModal.tsx b/apps/studio/components/interfaces/Account/TOTPFactors/AddNewFactorModal.tsx
index 5f3accd726d..2b18106f3ed 100644
--- a/apps/studio/components/interfaces/Account/TOTPFactors/AddNewFactorModal.tsx
+++ b/apps/studio/components/interfaces/Account/TOTPFactors/AddNewFactorModal.tsx
@@ -1,5 +1,6 @@
import { zodResolver } from '@hookform/resolvers/zod'
import { useQueryClient } from '@tanstack/react-query'
+import { useFlag } from 'common'
import { useEffect, useState } from 'react'
import { useForm, type SubmitHandler } from 'react-hook-form'
import { toast } from 'sonner'
@@ -10,11 +11,14 @@ import { FormItemLayout } from 'ui-patterns/form/FormItemLayout/FormItemLayout'
import { GenericSkeletonLoader } from 'ui-patterns/ShimmeringLoader'
import { z } from 'zod'
+import { RecoveryCodesModal } from './RecoveryCodesModal'
import InformationBox from '@/components/ui/InformationBox'
import { organizationKeys } from '@/data/organizations/keys'
import { useMfaChallengeAndVerifyMutation } from '@/data/profile/mfa-challenge-and-verify-mutation'
import { useMfaEnrollMutation } from '@/data/profile/mfa-enroll-mutation'
import { useMfaUnenrollMutation } from '@/data/profile/mfa-unenroll-mutation'
+import { useRecoveryCodesGenerateMutation } from '@/data/recovery-codes/recovery-codes-generate-mutation'
+import { useRecoveryCodesStatusQuery } from '@/data/recovery-codes/recovery-codes-status-query'
import { useLastVisitedOrganization } from '@/hooks/misc/useLastVisitedOrganization'
type TOTP = { qr_code: string; secret: string; uri: string }
@@ -26,6 +30,15 @@ interface AddNewFactorModalProps {
export const AddNewFactorModal = ({ visible, onClose }: AddNewFactorModalProps) => {
const { data, mutate: enroll, isPending: isEnrolling, reset } = useMfaEnrollMutation()
+ const enableAuthRecoveryCodes = useFlag('enableAuthRecoveryCodes')
+ const { isPending: isRecoveryCodesStatusPending, refetch: refetchRecoveryCodesStatus } =
+ useRecoveryCodesStatusQuery({
+ enabled: enableAuthRecoveryCodes,
+ })
+
+ const recoveryCodesGenerateMutation = useRecoveryCodesGenerateMutation()
+
+ const [isRecoveryCodesModalOpen, setIsRecoveryCodesModalOpen] = useState(false)
useEffect(() => {
if (!visible) reset()
@@ -35,7 +48,7 @@ export const AddNewFactorModal = ({ visible, onClose }: AddNewFactorModalProps)
<>
}
- isLoading={isEnrolling}
- onClose={onClose}
+ isLoading={isEnrolling || (enableAuthRecoveryCodes && isRecoveryCodesStatusPending)}
+ onClose={async () => {
+ if (enableAuthRecoveryCodes) {
+ const { data: currentRecoveryCodesStatus } = await refetchRecoveryCodesStatus()
+ const shouldGenerateRecoveryCodes = currentRecoveryCodesStatus?.status === 'unenrolled'
+
+ if (shouldGenerateRecoveryCodes) {
+ recoveryCodesGenerateMutation.mutate({})
+ setIsRecoveryCodesModalOpen(true)
+ }
+ }
+ onClose()
+ }}
+ />
+ setIsRecoveryCodesModalOpen(open)}
+ mutation={recoveryCodesGenerateMutation}
/>
)
diff --git a/apps/studio/components/interfaces/Account/TOTPFactors/RecoveryCodesModal.tsx b/apps/studio/components/interfaces/Account/TOTPFactors/RecoveryCodesModal.tsx
index ddfc9ee1ed8..4efec68cf56 100644
--- a/apps/studio/components/interfaces/Account/TOTPFactors/RecoveryCodesModal.tsx
+++ b/apps/studio/components/interfaces/Account/TOTPFactors/RecoveryCodesModal.tsx
@@ -132,7 +132,10 @@ const GenerateRecoveryCodesModalContent = ({
if (status === 'success') {
return (
+ anchorKey: string | null
+ targetKey: string
+}): Set {
+ const next = new Set(selectedKeys)
+
+ const anchorIndex = anchorKey === null ? -1 : orderedKeys.indexOf(anchorKey)
+ const targetIndex = orderedKeys.indexOf(targetKey)
+ const hasUsableAnchor = anchorIndex !== -1 && targetIndex !== -1
+
+ if (!hasUsableAnchor) {
+ if (next.has(targetKey)) {
+ next.delete(targetKey)
+ } else {
+ next.add(targetKey)
+ }
+ return next
+ }
+
+ const startIndex = Math.min(anchorIndex, targetIndex)
+ const endIndex = Math.max(anchorIndex, targetIndex)
+ const rangeKeys = orderedKeys.slice(startIndex, endIndex + 1)
+ const isRangeFullySelected = rangeKeys.every((key) => selectedKeys.has(key))
+
+ rangeKeys.forEach((key) => {
+ if (isRangeFullySelected) {
+ next.delete(key)
+ } else {
+ next.add(key)
+ }
+ })
+
+ return next
+}
diff --git a/apps/studio/tests/features/logs/LogTable.test.tsx b/apps/studio/tests/features/logs/LogTable.test.tsx
index d44212c9390..27d9f1541ef 100644
--- a/apps/studio/tests/features/logs/LogTable.test.tsx
+++ b/apps/studio/tests/features/logs/LogTable.test.tsx
@@ -307,3 +307,80 @@ test('custom error message: Resources exceeded during query execution', async ()
await screen.findByText(/Avoid querying across a large datetime range/)
await screen.findByText(/Please contact support if this error persists/)
})
+
+const createLogRow = (index: number) => ({
+ id: `log-id-${index}`,
+ timestamp: fakeMicroTimestamp - index,
+ event_message: `event message ${index}`,
+})
+
+const MULTI_SELECT_LOGS = Array.from({ length: 6 }, (_, index) => createLogRow(index))
+
+const getRowCheckboxes = () => screen.getAllByRole('checkbox')
+
+const expectCheckedIndexes = (checkedIndexes: number[]) => {
+ const checkboxes = getRowCheckboxes()
+ checkboxes.forEach((checkbox, index) => {
+ expect(checkbox.getAttribute('aria-checked')).toBe(
+ checkedIndexes.includes(index) ? 'true' : 'false'
+ )
+ })
+}
+
+const shiftClick = async (user: ReturnType, element: Element) => {
+ await user.keyboard('{Shift>}')
+ await user.click(element)
+ await user.keyboard('{/Shift}')
+}
+
+test('shift-click selects the range between the anchor row and the clicked row', async () => {
+ const user = userEvent.setup()
+ render(
Print a unified diff for each mismatched file with line numbers and
committed/production labels. Append escaped, bounded previews to the
GitHub Actions summary, with full diffs in the step logs, while
preserving the failing check.
## How to test
- Run `node --test
packages/api-types/scripts/verify-production-types.test.mjs` (all six
tests pass).
- Tests cover diff direction and line numbers, multiple files, summary
appending and escaping, preview truncation, local logging without an
Actions summary, and diff command failures.
- Both changed files were formatted with the repository Prettier
configuration.
## Summary by CodeRabbit
* **New Features**
* Added detailed difference reporting when generated production types do
not match committed types.
* CI logs now include readable unified diffs, with large outputs safely
truncated and escaped.
* GitHub Actions summaries can include mismatched type files and their
differences while preserving existing summary content.
* **Bug Fixes**
* Improved diagnostics for missing type files and type verification
failures.
---
.../scripts/verify-production-types.mjs | 53 ++++++++++++++++-
.../scripts/verify-production-types.test.mjs | 58 ++++++++++++++++++-
2 files changed, 109 insertions(+), 2 deletions(-)
diff --git a/packages/api-types/scripts/verify-production-types.mjs b/packages/api-types/scripts/verify-production-types.mjs
index 80fa563beb0..3451a824853 100644
--- a/packages/api-types/scripts/verify-production-types.mjs
+++ b/packages/api-types/scripts/verify-production-types.mjs
@@ -1,5 +1,5 @@
import { execFile } from 'node:child_process'
-import { mkdir, mkdtemp, readFile, rm, writeFile } from 'node:fs/promises'
+import { appendFile, mkdir, mkdtemp, readFile, rm, writeFile } from 'node:fs/promises'
import { tmpdir } from 'node:os'
import { dirname, join } from 'node:path'
import { fileURLToPath } from 'node:url'
@@ -66,6 +66,56 @@ export async function findMismatchedTypes(
return mismatches.filter((filename) => filename !== undefined)
}
+export async function reportTypeDifferences(
+ filenames,
+ {
+ generatedTypesDirectory,
+ typesDirectory,
+ summaryPath = process.env.GITHUB_STEP_SUMMARY,
+ log = console.log,
+ }
+) {
+ const summary = [
+ '## Production API type differences',
+ '',
+ 'Committed types differ from production. `-` lines are committed; `+` lines are production.',
+ '',
+ ]
+
+ for (const filename of filenames) {
+ let diff
+ try {
+ const result = await run(
+ 'diff',
+ [
+ '-u',
+ '--label',
+ `committed/${filename}`,
+ '--label',
+ `production/${filename}`,
+ join(typesDirectory, filename),
+ join(generatedTypesDirectory, filename),
+ ],
+ { maxBuffer: 32 * 1024 * 1024 }
+ )
+ diff = result.stdout
+ } catch (error) {
+ if (error.code !== 1) throw error
+ diff = error.stdout
+ }
+
+ log(`${filename}\n${diff}`)
+ const preview = diff.slice(0, 60_000)
+ const escaped = preview.replaceAll('&', '&').replaceAll('<', '<').replaceAll('>', '>')
+ summary.push(`### ${filename}`, '', `\n')
+ await writeFile(join(typesDirectory, 'platform.d.ts'), 'old\n')
+ await writeFile(join(generatedTypesDirectory, 'platform.d.ts'), 'new\n'.repeat(20_000))
+ const logs = []
+ await reportTypeDifferences(['api-v1.d.ts', 'platform.d.ts'], {
+ typesDirectory,
+ generatedTypesDirectory,
+ summaryPath,
+ log: (value) => logs.push(value),
+ })
+ assert.equal(logs.length, 2)
+ assert.match(logs[0], /--- committed\/api-v1.d.ts\n\+\+\+ production\/api-v1.d.ts/)
+ assert.match(logs[0], /@@ -1 \+1 @@/)
+ assert.match(logs[0], /-type A = string\n\+type A = Array/)
+ assert.ok(logs[1].length > 60_000)
+ const summary = await readFile(summaryPath, 'utf8')
+ assert.ok(summary.startsWith('Existing summary\n'))
+ assert.match(summary, /Array<number>/)
+ assert.match(summary, /### platform.d.ts/)
+ assert.match(summary, /Diff preview truncated/)
+ assert.ok(summary.length < 62_000)
+
+ await reportTypeDifferences(['api-v1.d.ts'], {
+ typesDirectory,
+ generatedTypesDirectory,
+ summaryPath: '',
+ log: () => {},
+ })
+ await assert.rejects(
+ reportTypeDifferences(['missing.d.ts'], {
+ typesDirectory,
+ generatedTypesDirectory,
+ summaryPath: '',
+ log: () => {},
+ }),
+ (error) => error.code === 2
+ )
+})
const specifications = [
{ name: 'api-v1', url: 'https://example.com/api/v1-json' },
From 4432a8beb472fa5d054e46755e586ca642e90ad6 Mon Sep 17 00:00:00 2001
From: Saxon Fletcher
Date: Wed, 16 Sep 2026 21:18:01 +1000
Subject: [PATCH 090/107] chore(studio): update Explorer feature preview copy
(#50250)
Updates the Explorer feature preview copy to explain the SQL Editor
transition, Notebooks, and Snippet migration plans. Adds feedback
questions and moves the preview image above the content.
Validation: Prettier and `git diff --check` passed.
## Summary by CodeRabbit
- **Documentation**
- Updated the Explorer preview layout by moving the preview image below
the introductory text.
- Replaced feedback questions with a clear overview of what enabling the
preview provides, including SQL Editor replacement and Notebooks
management through the dashboard and Assistant.
---------
Co-authored-by: Joshen Lim
---
.../App/FeaturePreview/ExplorerPreview.tsx | 29 ++++++++++++++-----
1 file changed, 22 insertions(+), 7 deletions(-)
diff --git a/apps/studio/components/interfaces/App/FeaturePreview/ExplorerPreview.tsx b/apps/studio/components/interfaces/App/FeaturePreview/ExplorerPreview.tsx
index f64d5fef769..6d37dcd18ac 100644
--- a/apps/studio/components/interfaces/App/FeaturePreview/ExplorerPreview.tsx
+++ b/apps/studio/components/interfaces/App/FeaturePreview/ExplorerPreview.tsx
@@ -12,13 +12,14 @@ export const ExplorerPreview = () => {
return (
{
className="rounded-sm border"
/>
+
-
No results found
-- Your search for “{filterString}” did not return any results. -
-No results found
-- Your search for "{filterString}" did not return any results -
-No event triggers created yet
-- There are no event triggers configured for this database -
-No results found
-- {filterString.length > 0 - ? `Your search for "${filterString}" did not return any results` - : 'No event triggers match the current filters'} -
-No results found
-- Your search for "{filterString}" did not return any results -
-No results found
-- Your search for "{searchString}" did not return any results -
-No results found
-- Your search for "{filterString}" did not return any results -
-No results found
-- Your search for “{filterString}” did not return any results -
-No results found
-- Your search for “{filterString}” did not return any results -
-No results found
++ Your search for “{filterString}” did not return any results +
+No results found
-- Your search for "{filterString}" did not return any results -
- - ) : ( - <> -No tables yet
-- Create your first table to get started -
- - )} -No tables yet
++ Create your first table to get started +
+ + ) : undefined} +No results found
-- Your search for "{filterString}" did not return any results -
-No results found
++ Your search for "{search}" did not return any results +
+ + )} +
-
diff --git a/apps/studio/components/interfaces/Settings/Logs/Logs.utils.test.ts b/apps/studio/components/interfaces/Settings/Logs/Logs.utils.test.ts
index 6091e922362..5c3820c4ea7 100644
--- a/apps/studio/components/interfaces/Settings/Logs/Logs.utils.test.ts
+++ b/apps/studio/components/interfaces/Settings/Logs/Logs.utils.test.ts
@@ -13,6 +13,7 @@ import {
genChartQuery,
genDefaultQuery,
getAuthLogSeverity,
+ getShiftClickSelection,
parseMultigresEventMessage,
} from './Logs.utils'
@@ -351,4 +352,120 @@ describe('Logs.utils', () => {
).not.toThrow()
})
})
+
+ describe('getShiftClickSelection', () => {
+ const orderedKeys = ['a', 'b', 'c', 'd', 'e']
+
+ test('selects the range downward from the anchor', () => {
+ const result = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(['b']),
+ anchorKey: 'b',
+ targetKey: 'd',
+ })
+ expect([...result].sort()).toEqual(['b', 'c', 'd'])
+ })
+
+ test('selects the range upward from the anchor', () => {
+ const result = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(['d']),
+ anchorKey: 'd',
+ targetKey: 'b',
+ })
+ expect([...result].sort()).toEqual(['b', 'c', 'd'])
+ })
+
+ test('toggles just the anchor when it is also the target', () => {
+ const added = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(),
+ anchorKey: 'c',
+ targetKey: 'c',
+ })
+ expect([...added]).toEqual(['c'])
+
+ const removed = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(['c']),
+ anchorKey: 'c',
+ targetKey: 'c',
+ })
+ expect([...removed]).toEqual([])
+ })
+
+ test('removes the range when it is already fully selected, keeping keys outside it', () => {
+ const result = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(['a', 'b', 'c', 'd']),
+ anchorKey: 'b',
+ targetKey: 'd',
+ })
+ expect([...result].sort()).toEqual(['a'])
+ })
+
+ test('selects the whole range when it is only partially selected', () => {
+ const result = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(['c']),
+ anchorKey: 'b',
+ targetKey: 'd',
+ })
+ expect([...result].sort()).toEqual(['b', 'c', 'd'])
+ })
+
+ test('falls back to adding the target when there is no anchor', () => {
+ const result = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(['a']),
+ anchorKey: null,
+ targetKey: 'c',
+ })
+ expect([...result].sort()).toEqual(['a', 'c'])
+ })
+
+ test('falls back to removing the target when there is no anchor and it is selected', () => {
+ const result = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(['a', 'c']),
+ anchorKey: null,
+ targetKey: 'c',
+ })
+ expect([...result].sort()).toEqual(['a'])
+ })
+
+ test('falls back to a plain toggle when the anchor is no longer in the rows', () => {
+ const result = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(),
+ anchorKey: 'gone',
+ targetKey: 'd',
+ })
+ expect([...result]).toEqual(['d'])
+ })
+
+ test('falls back to a plain toggle when the target is not in the rows', () => {
+ const result = getShiftClickSelection({
+ orderedKeys,
+ selectedKeys: new Set(['a']),
+ anchorKey: 'a',
+ targetKey: 'gone',
+ })
+ expect([...result].sort()).toEqual(['a', 'gone'])
+ })
+
+ test('does not mutate its inputs', () => {
+ const selectedKeys = new Set(['b'])
+ const keys = [...orderedKeys]
+ const result = getShiftClickSelection({
+ orderedKeys: keys,
+ selectedKeys,
+ anchorKey: 'b',
+ targetKey: 'd',
+ })
+ expect(result).not.toBe(selectedKeys)
+ expect([...selectedKeys]).toEqual(['b'])
+ expect(keys).toEqual(orderedKeys)
+ })
+ })
})
diff --git a/apps/studio/components/interfaces/Settings/Logs/Logs.utils.ts b/apps/studio/components/interfaces/Settings/Logs/Logs.utils.ts
index 68c318dca37..72e98b9487f 100644
--- a/apps/studio/components/interfaces/Settings/Logs/Logs.utils.ts
+++ b/apps/studio/components/interfaces/Settings/Logs/Logs.utils.ts
@@ -957,3 +957,52 @@ export function buildLogsPrompt(rows: LogData[], queryType?: string, sqlQuery?:
'\n\nWhat do these logs indicate? What steps can I take to resolve it? Keep your answer very concise and actionable. Max 2 or 3 bullet points.'
)
}
+
+/**
+ * Computes the next multi-select set after a shift-click on `targetKey`, extending
+ * the selection from `anchorKey` (the last row the user clicked). Every key between
+ * anchor and target (inclusive, in `orderedKeys` order) is added. If the whole range is
+ * already selected, the range is removed instead. Falls back to a plain toggle of
+ * `targetKey` when there is no usable anchor (null, or no longer in `orderedKeys`).
+ */
+export function getShiftClickSelection({
+ orderedKeys,
+ selectedKeys,
+ anchorKey,
+ targetKey,
+}: {
+ orderedKeys: string[]
+ selectedKeys: SetSave your recovery codes somewhere safe.
++ Recovery codes allow you to recover your account in case you lost access to your MFA apps. + Save them somewhere safe. +
{codes?.map((code) => (
From 5e8e551e2c05440bf4624500609fe3c6061a8eac Mon Sep 17 00:00:00 2001
From: Pamela Chia
Date: Wed, 16 Sep 2026 16:54:42 +0800
Subject: [PATCH 085/107] fix(www): include app routes in sitemap (#50277)
I added static App Router pages to the www sitemap, including the
homepage, pricing, and product pages. The generator previously scanned
only Pages Router and content files; it now strips route groups,
excludes dynamic segments, and emits these URLs without lastmod.
**Note:** The pre-existing Pages Router `/opt-out/[ref]` entry remains
outside this change.
## To test
Tested on the [www
preview](https://zone-www-dot-com-git-pamela-growth-1214-app-rou-1d4879-supabase.vercel.app/sitemap_www.xml):
- [x] Open `/sitemap_www.xml`: expect the homepage, `/pricing`, and
product routes once each, without route-group names or lastmod on those
entries.
- [x] Compare the sitemap's changelog URLs with `/changelog-rss.xml`:
expect every RSS item link to remain included, including text-slug
entries.
- [x] Open `/sitemap.xml`: expect the existing www and docs sitemap
links.
## Linear
- fixes GROWTH-1214
## Summary by CodeRabbit
- **New Features**
- Sitemap generation now includes static pages built with the Next.js
App Router.
- Route groups are correctly omitted from generated URLs.
- Dynamic App Router routes are excluded from the sitemap.
- **Bug Fixes**
- Improved sitemap coverage and URL accuracy for applications using both
App Router and Pages Router pages.
---
apps/www/generate-sitemap.test.ts | 40 +++++++++++++++++++++++++
apps/www/internals/generate-sitemap.mjs | 8 +++++
2 files changed, 48 insertions(+)
diff --git a/apps/www/generate-sitemap.test.ts b/apps/www/generate-sitemap.test.ts
index 7778886cf17..42be8704b6d 100644
--- a/apps/www/generate-sitemap.test.ts
+++ b/apps/www/generate-sitemap.test.ts
@@ -189,6 +189,46 @@ describe('generate-sitemap lastmod', () => {
})
})
+describe('generate-sitemap App Router pages', () => {
+ it.each(['app/page.tsx', 'app/(home)/page.tsx'])(
+ 'includes only static page URLs without lastmod, with homepage at %s',
+ (homepage) => {
+ const dir = writeFixture({
+ [homepage]: '',
+ 'app/(group)/example/page.tsx': '',
+ 'app/(marketing)/guides/(topics)/start/page.tsx': '',
+ 'app/blog/example/page.tsx': '',
+ 'app/events/example/page.tsx': '',
+ 'app/reference/index/page.tsx': '',
+ 'app/things/[slug]/page.tsx': '',
+ 'app/things/[slug]/details/page.tsx': '',
+ 'app/(group)/[...slug]/page.tsx': '',
+ 'app/optional/[[...slug]]/page.tsx': '',
+ 'app/example/layout.tsx': '',
+ 'app/api/route.ts': '',
+ 'app/loading.tsx': '',
+ 'pages/company.tsx': '',
+ })
+ const result = runGenerator(dir)
+ expect(result.status, result.stderr).toBe(0)
+ const entries = urlEntries(fs.readFileSync(path.join(dir, 'public/sitemap_www.xml'), 'utf-8'))
+ expect(entries.sort((a, b) => a.loc.localeCompare(b.loc))).toEqual(
+ [
+ '',
+ '/blog/example',
+ '/company',
+ '/evals',
+ '/events/example',
+ '/example',
+ '/guides/start',
+ '/reference/index',
+ ].map((route) => ({ loc: `https://supabase.com${route}`, lastmod: undefined }))
+ )
+ },
+ SPAWN_TIMEOUT_MS
+ )
+})
+
describe('frontmatter dates in sitemap and blog JSON-LD', () => {
it.each([
['2026-01-14T09:30:00', '2026-01-14'],
diff --git a/apps/www/internals/generate-sitemap.mjs b/apps/www/internals/generate-sitemap.mjs
index 2a879479f1c..0f64bfca847 100644
--- a/apps/www/internals/generate-sitemap.mjs
+++ b/apps/www/internals/generate-sitemap.mjs
@@ -65,6 +65,7 @@ async function generate() {
'pages/*.tsx',
'pages/*.mdx',
'pages/**/*.tsx',
+ 'app/**/page.tsx',
'_blog/*.mdx',
'_case-studies/*.mdx',
'_customers/*.mdx',
@@ -90,6 +91,13 @@ async function generate() {
// Generate URLs for static pages
const staticUrls = pages
.map((page) => {
+ if (page.startsWith('app/')) {
+ const segments = page.split('/').slice(1, -1)
+ if (segments.some((segment) => segment.includes('['))) return null
+ const path = segments.filter((segment) => !/^\(.*\)$/.test(segment)).join('/')
+ return urlEntry(`https://supabase.com${path ? `/${path}` : ''}`)
+ }
+
const path = page
.replace('.next/server/pages', '')
.replace(/^pages/, '')
From adca15deabe854b9f19be71976fc8c595dd86388 Mon Sep 17 00:00:00 2001
From: "claude[bot]" <209825114+claude[bot]@users.noreply.github.com>
Date: Wed, 16 Sep 2026 17:26:21 +0800
Subject: [PATCH 086/107] chore(www): add Privacy Policy v4 (data controller
entity, Freebuff cookie) (#50392)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
_Requested by **Sofia Calado** · [Slack
thread](https://supabase.slack.com/archives/C0161K73J1J/p1789462983606899)_
## 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?
Content update — a new version (v4) of the Privacy Policy legal page,
added following the existing versioned-legal-page pattern (v1-v3 already
present, selectable via a version dropdown).
## What is the current behavior?
Before: On `/privacy`, the latest selectable version is "Version 3 — May
13, 2026". That text names "Supabase, Inc" as the entity you're dealing
with — both in the opening paragraph ("Thank you for your interest in
Supabase, Inc., ...") and again as the named data controller in the
EEA/UK/Switzerland disclosures section ("Supabase, Inc is the data
controller..."). The Section 8 cookie table (EEA cookies) lists nine
cookies/rows (Stripe x3, Cloudflare x2, Youtube, hCaptcha, Posthog,
Google Analytics 4, Google Ads, `_sb_first_referrer`) and does not
mention Freebuff anywhere.
## What is the new behavior?
After: `/privacy` gains a new "Version 4" entry in the dropdown, at the
top of the list (selected by default). Reading Version 4, the same two
passages instead name "Supabase Pte. Ltd." as the entity/data
controller. The Section 8 cookie table gains one additional row for
"Freebuff" (Type: Advertising; dropped when you visit the Site after
interacting with a Freebuff ad; 30-day duration; purpose: measuring ad
campaign performance and attributing conversions to ad clicks upon
consent; linking to the Freebuff Privacy Policy), formatted identically
to the existing rows. Versions 1-3 are unchanged and remain selectable.
## Additional context
Two changes, scoped exactly as requested:
1. **Data controller entity**: every "Supabase, Inc" / "Supabase Inc."
reference that names the data controller is replaced with "Supabase Pte.
Ltd." — at the top of the policy and in the EEA disclosures section. No
other "Supabase" references (e.g. plain brand mentions) were touched.
2. **Freebuff cookie row**: added to the Section 8 (EEA cookies) table,
matching the existing table's markdown formatting exactly.
**Open question — effective date needs Sofia/Nicole's input before
merge.** No effective date was given for v4. The version-selector
component (`LegalDocVersions`) requires a non-empty `effectiveDate`
string per version to render (used both in the dropdown label and, for a
single-version page, an on-page line) — there's no way to add the
version without wiring some string. Following the pattern's convention
of never inventing a plausible-looking date, `effectiveDate` is set to
the literal placeholder `'TBD'` for v4 in `apps/www/pages/privacy.tsx`.
**This must be replaced with a real effective date before this PR
merges** — flagging for Sofia Calado / Nicole Kramer to confirm.
**Validation**: `pnpm --filter=www build` fails in this sandbox due to
an unrelated prebuild step (`docs` app's `build:federated-content`
script needs live GitHub API credentials to fetch tags — 401 Bad
credentials — not related to this change). `tsc --noEmit` on `apps/www`
ran clean of any error touching `privacy.tsx` or the privacy `.mdx`
files (all reported errors are pre-existing, about unrelated missing
generated assets/images). As a direct substitute, all four
`apps/www/data/legal/privacy/*.mdx` files (v1-v4) were compiled through
the app's actual MDX pipeline (`@mdx-js/mdx` with the same
`remark-code-hike` + `remark-gfm` + `rehype-slug` config as
`next.config.mjs`) and all compiled successfully, confirming the new
table syntax and content are valid MDX/GFM.
Files touched:
- `apps/www/data/legal/privacy/v4.mdx` (new)
- `apps/www/pages/privacy.tsx` (added v4 to the `versions` array)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01BzHiVEUzjvrwxgnxCrrER1
---------
Co-authored-by: Claude
---
apps/www/data/legal/privacy/v4.mdx | 336 +++++++++++++++++++++++++++++
apps/www/pages/privacy.tsx | 2 +
2 files changed, 338 insertions(+)
create mode 100644 apps/www/data/legal/privacy/v4.mdx
diff --git a/apps/www/data/legal/privacy/v4.mdx b/apps/www/data/legal/privacy/v4.mdx
new file mode 100644
index 00000000000..3ef9ed44d84
--- /dev/null
+++ b/apps/www/data/legal/privacy/v4.mdx
@@ -0,0 +1,336 @@
+import { PrivacySettings } from 'ui-patterns/PrivacySettings'
+
+Thank you for your interest in Supabase Pte. Ltd., ("**_Supabase_**," "**_we_**", "**_our_**" or "**_us_**"). Supabase provides a suite of open source tools, stitched together to build a seamless developer experience. This Privacy Notice explains how information about you, that directly identifies you, or that makes you identifiable ("**_personal information_**") is collected, used and disclosed by Supabase in connection with our website at [supabase.com](https://supabase.com) (the "**_Site_**") and our services offered in connection with the Site (collectively with the Site, the "**_Service_**").
+
+## What Does This Privacy Notice Apply To?
+
+This Privacy Notice explains how we use your personal information when you use the Service, either as an individual customer or when you access the Service through one of our enterprise customers' accounts. We are the data controller of your personal information when we use it as described in this Privacy Notice, meaning that we determine and are responsible for how your personal information is processed.
+
+Our Service allows customers to submit, manage or otherwise use content relating to others, such as end users of applications built and managed through the Service or their employees and contractors (“**_Customer Data_**”). We use such Customer Data primarily as a processor, meaning we process such Customer Data on behalf of and under the instructions of the relevant customer, in accordance with our [data processing addendum](/legal/customer-resources/data-processing-addendum). This Privacy Notice does not apply to such processing; if you believe your personal information has been included in any Customer Data, we recommend you read the Privacy Notice of the respective customer.
+
+This Privacy Notice sets out how we use personal information. It does not cover our use of information that is not "personal information", "personal information" or similar terms under applicable law. This means that it does not cover our use of aggregated or anonymized information.
+
+Where applicable law permits, it also does not cover deidentified information, meaning information that is maintained in a form that is not reasonably capable of being associated with or linked to an individual (please note that this exception would not apply to personal information collected from you if you are in the UK, EEA or Switzerland).
+
+We may also provide you with additional privacy notices or disclosures where the scope of the inquiry, request, or personal information we require falls outside the scope of this Privacy Notice. In that case, the additional Privacy Notice or disclosures will set out how we may process the information you provide at that time. Please note that this Privacy Notice does not cover or apply to our processing of information about our employees or contractors or applicants for positions at Supabase.
+
+## Region-specific Disclosures
+
+- **California - Your California Privacy Rights:** If you are a California resident, California Civil Code Section 1798.83 permits you to request information regarding the disclosure of personal information to third parties for their direct marketing purposes during the immediately preceding calendar year. We may use tracking tools to measure the performance of our advertising campaigns and help deliver personalized ads. You can manage your preferences in the Privacy Settings .
+- **Nevada:** Chapter 603A of the Nevada Revised Statutes permits a Nevada resident to opt out of future sales of certain covered information that a website operator has collected or will collect about the resident. Note we do not sell your personal information within the meaning of Chapter 603A. However, if you would still like to submit such a request, please contact us at privacy@supabase.com.
+- **European Economic Area, United Kingdom or Switzerland:** If you are located in the European Economic Area ("**_EEA_**"), United Kingdom or Switzerland, or otherwise engage with Supabase’s European operations, please see the **[Privacy Disclosures for the European Economic Area, United Kingdom and Switzerland](#privacy-disclosures-for-the-european-economic-area-united-kingdom-and-switzerland)** for additional European-specific privacy disclosures, including the lawful bases we rely on to process your personal information, how we use cookies when you access our Sites from the EEA, UK or Switzerland and your rights in respect of your personal information.
+
+**Note for International Visitors:** Personal information may be transferred to, stored and processed in a country other than the one in which it was collected. For example, the Sites are primarily hosted in and provided from the United States. Please note the country to which personal data is transferred may not provide the same level of protection for personal information as the country from which it was transferred.
+
+Click on the links below to jump to each section:
+
+1. [Information we collect and our use](#1-information-we-collect-and-our-use)
+2. [How we share personal information](#2-how-we-share-personal-information)
+3. [Control over your information](#3-control-over-your-information)
+4. [How we use cookies and other tracking technology to collect information](#4-how-we-use-cookies-and-other-tracking-technology-to-collect-information)
+5. [Data retention and security](#5-data-retention-and-security)
+6. [Links to third-party websites and services](#6-links-to-third-party-websites-and-services)
+7. [Children's privacy](#7-childrens-privacy)
+8. [Changes to this privacy notice](#8-changes-to-privacy-notice)
+9. [Contact us](#9-contact-us)
+
+[Privacy disclosures for the European Economic Area, United Kingdom and Switzerland](#privacy-disclosures-for-the-european-economic-area-united-kingdom-and-switzerland)
+
+## 1. Information we collect and our use
+
+We collect personal information in connection with your visits to and use of the Service. This collection includes information that you provide in connection with the Service, information from third parties, and information that is collected automatically such as through the use of cookies and other technologies.
+
+### Information That You Provide
+
+We collect personal information that you submit directly to us. The categories of information we collect can include:
+
+- **_Registration information._** We collect personal and/or business information that you provide when you register for an account on the Site. This information may include your name, email address, and GitHub username. We use this information to administer your account, provide you with the relevant services and information, communicate with you regarding your account, the Site and for customer support purposes.
+- **_Payment information._** If you make a purchase or payment on the Site, such as for a subscription, we collect transactional information provided in connection with your purchase or payment. Please note that we use third party payment processors, including Stripe, to process payments made to us. As such, we do not retain any personally identifiable financial information such as credit card numbers. Rather, all such information is provided directly by you to our third-party processor. The payment processor’s use of your personal information is governed by their privacy notice. To view Stripe’s privacy notice, please visit: [https://stripe.com/privacy](https://stripe.com/privacy).
+- **_Communications._** If you communicate with us through any paper or electronic form, we may collect your name, email address, mailing address, phone number, or any other personal information you choose to provide to us. We use this information to investigate and respond to your inquiries, and to communicate with you, to enhance the services we offer to our users and to manage and grow our organization. If you register for our newsletters or updates, we may communicate with you by email. To unsubscribe from promotional messages, please follow the instructions within our messages and review the **[Control Over Your Information section](#3-control-over-your-information)** below. If you become a contributor, we may also collect your GitHub name and feature you on our website.
+- **_Inquiries and Feedback._** If you contact us, we will collect the information that you provide us, such as your contact information and the contents of your communication with us.
+
+You are free to choose which personal information you want to provide to us or whether you want to provide us with personal information at all. However, some information, such as your name, address, payment transaction information, and information on your requested Services may be necessary for the performance of our contractual obligations.
+
+After registration, you may create, upload or transmit files, documents, videos, images, data or information as part of your use of the Service (collectively, “**_User Content_**”). This includes any inputs you provide to our AI-powered support tools and outputs generated in response to your inputs. User Content and any information contained in the User Content, including personal information you may have included, is stored and collected as part of the Service. You have full control of the information included in the User Content.
+
+### Information from Third Party Sources
+
+We may receive personal information about you from our business partners and service providers and combine this information with other data we collect from you. The third-parties may include website and service operators, payment processors, and marketing partners. The information may include contact information, demographic information, information about your communications and related activities, and information about your orders. We may use this information to administer and facilitate our services, your orders and our marketing activities.
+
+- **_Single Sign-On._** We use single sign-on ("**SSO**") such as GitHub to allow a user to authenticate their account using one set of login information. We will have access to certain information from those third parties in accordance with the authorization procedures determined by those third parties, including, for example, your name, username, email address, language preference, and profile picture. We use this information to operate, maintain, and provide to you the features and functionality of the Service. We may also send you service-related emails or messages (e.g., account verification, purchase confirmation, customer support, changes or updates to features of the Site, technical and security notices).
+- **_Social Media._** When you interact with our Site through various social media, such as when you click on the social media icon on the Site, follow us on a social media site, or post a comment to one of our pages, we may receive information from the social network such as your profile information, profile picture, user name, user ID associated with your social media account, and any other information you permit the social network to share with third parties. The data we receive is dependent upon your privacy settings with the social network. We use this information to operate, maintain, and provide to you the features and functionality of the Service, as well as to communicate directly with you, such as to send you email messages about products and services that may be of interest to you.
+- **_Information from Other Sources._** We may obtain information from other sources, including through third-party information providers, our shareholders, customers, or through transactions such as mergers and acquisitions. We may combine this information with other information we collect from or about you. In these cases, our Privacy Notice governs the handling of the combined personal information. We use this information to operate, maintain, and provide to you the features and functionality of the Service, as well as to communicate directly with you, such as to send you email messages about products and services that may be of interest to you.
+
+### Other Uses of Personal Information
+
+In addition to the uses described above, we may collect and use personal information for the following purposes:
+
+- For our business activities, including to operate the Service and to provide you with the features and functionality of the Service;
+- To communicate with you and respond to your requests, such as to respond to your questions, contact you about changes to the Service, and communicate about account related matters;
+- For marketing and advertising purposes, such as to market to you or offer you with information and updates on our products or services we think that you may be interested in, unless you have opted not to receive such information. We may use business contact information, including email domains, to identify organizations that may be interested in our Services and to conduct sales and marketing outreach. While we may use your personal information in this manner, please note that we do not use User Content to send you ads, and we will never share User Content with any third parties for marketing or advertising purposes, unless you have explicitly submitted it to us for that purpose;
+- For analytics and research purposes;
+- To enforce our **[Terms of Service](/terms)**, to resolve disputes, to carry out our obligations and enforce our rights, and to protect our business interests and the interests and rights of third parties;
+- To comply with contractual and legal obligations and requirements;
+- To fulfill any other purpose for which you provide personal information; and
+- For any other lawful purpose, or other purpose that you consent to.
+
+## 2. How we share personal information
+
+We may share your personal information in the instances described below. For further information on your choices regarding your information, see **[Control Over Your Information](#3-control-over-your-information)**.
+
+- We may share your personal information with third-party service providers or business partners who help us deliver or improve our Site or services, or who perform services on our behalf. These third parties _are subject to reasonable confidentiality terms and provisions restricting their use of your personal information_, and may include parties that process payments and coordinate billing, provide web hosting services, assist with our AI powered services, provide analytics, or help us send and segment marketing communications.
+- Third parties as required by law or subpoena or if we reasonably believe that such action is necessary to (a) comply with the law and the reasonable requests of law enforcement; (b) to enforce our **[Terms of Service](/terms)** or other agreements or to protect the security or integrity of the Supabase services, including to prevent harm or financial loss, or in connection with preventing fraud or illegal activity; and/or (c) to exercise or protect the rights, property, or personal safety of Supabase, our Customers, visitors, or others.
+- We may share with other companies and brands owned or controlled by Supabase, and other companies owned by or under common ownership as Supabase. These companies will use your personal information in the same way as we can under this Privacy Notice.
+- We may transfer any information we collect in the event we sell or transfer all or a portion of our business or assets (including any shares in the company) or any portion or combination of our products, services, businesses and/or assets. Should such a transaction occur (whether a divestiture, merger, acquisition, bankruptcy, dissolution, reorganization, liquidation, or similar transaction or proceeding), we will use reasonable efforts to ensure that any transferred information is treated in a manner consistent with this Privacy Notice.
+- We may disclose your information publicly or with another third party with your prior authorization.
+- With others in an aggregated or otherwise anonymized form that does not reasonably identify you directly or indirectly as an individual.
+
+**Advertising and Audience Management.** We may share limited personal information, such as contact identifiers (including email addresses or cryptographic hashes of email addresses), with advertising and marketing partners to create, manage, and measure advertising audiences. This may include using hashed identifiers to match or exclude existing users from marketing campaigns, measure advertising effectiveness, or prevent ads from being shown to individuals who have already registered for our services. These partners may use this information in accordance with their applicable terms and privacy policies for advertising audience management and related measurement purposes.
+
+## 3. Control over your information
+
+### Email Communications
+
+From time to time, we may send you emails regarding updates to our Service, products or services, notices about our organization, or information about products/services we offer (or promotional offers from third parties) that we think may be of interest to you. Our marketing emails may include tracking technologies to help us understand whether an email was opened or a link was clicked within the email. This helps us assess engagement and improve the relevance of our communications to you. If you wish to unsubscribe from such emails, simply click the “unsubscribe link” provided at the bottom of the email communication. Note that you cannot unsubscribe from certain services-related email communications (e.g., account verification, confirmations of transactions, technical or legal notices).
+
+### Modifying Account Information
+
+If you have an online account with us, you have the ability to modify certain information in your account (e.g., your contact information) through the account options provided on the Site. If you have provided consent to share certain data with third-party partners in relation to our AI-powered services, you can update your preferences or withdraw your consent at any time through your account settings. If there is personal information in your User Content, you can use the features and functionality of the Service to edit or delete the personal information or User Content. Not all personal information is maintained in a format that you can access or change. If you would like to request access to, or correction or deletion of personal information, you may send your request to us at the email provided below. We will review your request and may require you to provide additional information to identify yourself, but we do not promise that we will be able to satisfy your request.
+
+## 4. How We Use Cookies and Other Tracking Technology to Collect Information
+
+We, and our third-party partners, automatically collect certain types of usage information when you visit our Site. We typically collect this information through a variety of tracking technologies, including cookies, web beacons, embedded scripts, location-identifying technologies, file information, and similar technology (collectively, “**tracking technologies**”).
+
+We, and our third-party partners, use tracking technologies to automatically collect usage and device information, such as:
+
+- Information about your device and its software, such as your IP address, browser type, Internet service provider, device type/model/manufacturer, operating system, date and time stamp, and a unique ID that allows us to uniquely identify your browser or your account (including, for example, a persistent device identifier), and other such information.
+- When you access our sites from a mobile device, we may collect unique identification numbers associated with your device or our mobile application mobile carrier, device type, model and manufacturer, mobile device operating system brand and model, and depending on your mobile device settings, we may be able to approximate a device’s location by analyzing other information, like an IP address.
+- Information about the way you access and use our services, for example, the site from which you came and the site to which you are going when you leave our services, the pages you visit, the links you click, whether you open emails or click the links contained in emails, whether you access the services from multiple devices, and other actions you take on the Site.
+- We use the data collected through tracking technologies to: (a) remember information so that you will not have to re-enter it during your visit or the next time you visit the site; (b) provide custom content and information; (c) identify you across multiple devices; (d) provide and monitor the effectiveness of our services; (e) monitor aggregate metrics such as total number of visitors, traffic, usage, and demographic patterns on our Site; (f) diagnose or fix technology problems; and (g) to provide, plan for, and enhance our services.
+
+We may use tracking technologies to measure the effectiveness of our advertising campaigns and to help deliver personalized ads. These tools may collect information about your interactions with our ads and websites, which can be used to analyze advertising metrics and tailor ads specifically to you. You can manage your preferences for such tracking technologies in the Privacy Settings .
+
+**Cookies and Other Tracking Technologies Opt-Out.** Depending on your browser or mobile device, you may be able to set your browser to delete or notify you of cookies and other tracking technology by actively managing the settings on your browser or mobile device.
+
+If you would prefer not to accept cookies, most browsers will allow you to: (i) change your browser settings to notify you when you receive a cookie, which lets you choose whether or not to accept it; (ii) disable existing cookies; or (iii) set your browser to automatically reject cookies. Please note that doing so may negatively impact your experience using the sites, as some features and services on our sites may not work properly. Depending on your mobile device and operating system, you may not be able to delete or block all cookies. You may also set your e-mail options to prevent the automatic downloading of images that may contain technologies that would allow us to know whether you have accessed our e-mail and performed certain functions with it.
+
+## 5. Data Retention and Security
+
+We will retain your personal information for the length of time needed to fulfill the purposes outlined in this Privacy Notice, unless a longer retention period is required or permitted by law. We store data on servers in the U.S. or any other country in which Supabase or its affiliates, subsidiaries, agents or contractors maintain facilities. Your personal information may be transferred to and stored outside of your state, province, country, or other governmental jurisdiction where the data protection laws may differ from those in your jurisdiction. When you register for use with Supabase you have the option to select where you store your information and we will not transfer it without providing information to you in advance.
+
+Supabase cares about the security of your information and uses commercially reasonable physical, technical and organizational measures designed to preserve the integrity and security of all information we collect. However, no security system is impenetrable, and we cannot guarantee the security of our systems 100%. In the event that any information under our control is compromised as a result of a breach of security, we will take reasonable steps to investigate the situation and where appropriate, notify those individuals whose information may have been compromised and take other steps, in accordance with any applicable laws and regulations.
+
+## 6. Links to Third-Party Websites and Services
+
+For your convenience, our Site may provide links to third-party websites or services that we do not own or operate. We are not responsible for the practices employed by any websites or services linked to or from the services, including the information or content contained within them. Your browsing and interaction on any other website or service are subject to the applicable third party’s rules and policies, not ours. If you are using a third-party website or service, you do so at your own risk. We encourage you to review the privacy policies of any site or service before providing any personal information.
+
+## 7. Children’s Privacy
+
+Our services are not intended for children under the age of 13. We do not knowingly solicit or collect personal information from children under the age of 13. If we learn that any personal information has been collected inadvertently from a child under 13, we will delete the information as soon as possible. If you believe that we might have collected information from a child under 13, please contact us at privacy@supabase.com.
+
+## 8. Changes to Privacy Notice
+
+We reserve the right to change this Privacy Notice from time to time in our sole discretion. We will notify you about material changes in the way we treat personal information in an appropriate manner, such as by sending a notice to the primary email address specified in your Supabase account, placing a prominent notice on our Site and/or other appropriate methods. It is your responsibility to review this Privacy Notice periodically. When we do change the Privacy Notice, we will also revise the “last modified” date.
+
+## 9. Contact Us
+
+For additional inquiries about this Privacy Notice, please send us an email at privacy@supabase.com.
+
+## Privacy disclosures for the European economic area, United Kingdom, and Switzerland.
+
+The following disclosures (“**Privacy Disclosures**”) apply to you if you access or use the Site or the Services from the European Economic Area, United Kingdom or Switzerland.
+
+Supabase Pte. Ltd. is the data controller of your personal information when we use it as described in these Privacy Disclosures, meaning that we determine and are responsible for how your personal information is processed.
+
+### 1. Personal Information You Provide To Us
+
+We collect the following categories of personal information that you submit directly to us when you use the Service:
+
+(a) **Contact information**, such as first name, last name and email address
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| When you create an account and access the Service as an individual, we use this information to set up and authenticate your account on the Service. | The processing is necessary for the performance of a contract with you and to take steps prior to entering into a contract with you, namely our Terms of Service. | We may share this information with the following service providers through the provision of the Service: Stripe, Orb, Hubspot, Amazon Web Services, Google Cloud, Postmark, Twilio, Fly.io, PandaDoc, Atlassian, front.com, Clazar, Hex.tech, and Clay. |
+| We use this information to communicate with you, including sending service-related communications. | The processing is necessary for the performance of a contract with you, namely our Terms of Service. | |
+| We use this information to deal with enquiries and complaints made by or about you relating to the Service. | The processing is necessary for our legitimate interests, namely administering the Service, and for communicating with you effectively to respond to your queries or complaints. | |
+| We use this information to send you marketing communications in accordance with your preferences. | We will only use your personal information in this way to the extent you have given us consent to do so. | We may share this information with the following service providers through the provision of the Service: Customer.io. |
+
+(b) **Your registration / account information**. When you create an account and access the Service as an individual, or if you use an email and password to sign up to the service, we will collect your email address, and password. If you use GitHub we offer a single sign-on ("**_SSO_**") to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| -------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
+| We use this information to create your account on the Service. | The processing is necessary for the performance of a contract with you. | We may share this information with the following service providers through the provision of the Service: GitHub, Amazon Web Services. |
+
+(c) **Payment transaction and billing information**. When you make a purchase through your own individual account on the Service, we collect information such as your billing address and Tax ID and other information such as date and time of your transaction and products / services purchased.
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| We use this information to process your orders through the Service and collect payment. | The processing is necessary for the performance of a contract. | We may share this information with the following service providers through the provision of the Service: Stripe, Orb, Tableau, PandaDoc, Hubspot, Clay, Clazar, and Amazon Web Services. |
+| We use this information to verify your identity in connection with the detection and prevention of fraud or financial crime. | The processing is necessary for our and third parties' legitimate interests, namely the detection and prevention of fraud and financial crime. | |
+
+(d) **Chat, comments and opinions**. When you contact us directly, e.g. by email or phone or through our feedback form we will record your comments and opinions.
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| When you contact us about your own individual account, or contact us as a prospective customer, we use this information to address your questions, issues and concerns. | The processing is necessary for our legitimate interests, namely communicating with you and responding to queries, complaints and concerns. | We may share this information with the following service providers through the provision of the Service: Hubspot, Tableau, Google Gsuite, Notion, Amazon Web Services, Slack, Clay, front.com, Amazon Bedrock, and OpenAI. |
+| We use this information to improve the Service. | The processing is necessary for our legitimate interests (to develop and improve our service). | |
+
+(e) **Information you submit through our Supabase AI tool**. When you submit a query through our Supabase AI tool, we will collect the content of your query (i.e. your inputs or prompts), and the corresponding generated output. We also collect information about the databases and other content you manage through the Service, but only the information about the structure of your databases and metadata, such as column and row headings or other information about how that content is organized. We will not access the content of the databases itself or the information you manage through the Service without your consent.
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| When you use the Supabase AI to submit queries through your own individual account, we will use this information to generate automated responses to your query. | The processing is necessary for the performance of a contract with you, namely our Terms of Service. | We may share this information with the following service providers through the provision of the Service: OpenAI, LLC and its affiliates, Amazon Bedrock, Fly.io, and AWS. |
+| We use this information to assess the performance of the chatbot tool and improve the Service. | The processing is necessary for our legitimate interests (to develop and improve our service). | |
+
+(f) **Information received from third parties, such as social networks**. If you interact with us through a social network, we may receive information from the social network such as your name, profile information, and any other information you permit the social network to share with third parties. We use single sign-on ("**_SSO_**") such as GitHub to allow a user to authenticate their account using one set of login information. The data we receive is dependent on your privacy settings with the social network.
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| We use this information to reshare content created through the use of the Service. | The processing is necessary for our legitimate interests (to develop our service and inform our marketing strategy). | We may share this information with the following service providers through the provision of the Service: Commonroom, GitHub, and Slack. |
+| We use this information to authenticate you and allow you to access the Service. | The processing is necessary for the performance of a contract with you. | |
+
+### 2. Information we collect about your Use of the Site and Service.
+
+We also automatically collect the following personal information about how you access and use the Service, and information about the device you use to access the Service:
+
+(a) **Approximate Location information**. When you visit our Service, we may collect information about your location. This information may be derived from WiFi positioning or your IP address.
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| We use information to present the Service to you on your device, including localizing features of the Service. | The processing is necessary for performance of a contract with you, namely our Terms of Service. If you access the Service as an authorized user of another customer, the processing is necessary for our and the customer's legitimate interests, namely presenting the Service to you on your device. | We may share this information with the following service providers through the provision of the Service: Sentry, Tableau, Posthog, Plausible, Google LLC, Fly.io, Vercel, Cloudflare, Configcat, Stape.io, Hex.tech, and Amazon Web Services. |
+| We use this information to determine content that may be of interest to you. | We will only use your personal information in this way to the extent you give us your consent to do so. | We may share this information with the following service providers through the provision of the Service: Customer.io. |
+
+(b) **Information about how you access and use the Service**. For example, how frequently you access the Service, the time you access the Service and how long you use it for, the approximate location that you access the Service from, the site from which you came and the site to which you are going when you leave our website, the website pages you visit, the links you click, whether you opened a marketing email or clicked the links within the email, whether you clicked on an ad or interacted with our ads, whether you access the Service from multiple devices, and other actions you take on the Service.
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| We use information about how you use and connect to the Service to present the Service to you on your device. | The processing is necessary for performance of a contract with you, namely our Terms of Service. If you access the Service as an authorized user of another customer, the processing is necessary for our and the customer's legitimate interests, namely presenting the Service to you on your device. | We may share this information with the following service providers through the provision of the Service: Posthog, Plausible, Fly.io, Sentry, Hubspot, Google LLC, Vercel, Hex.tech, and Amazon Web Services. |
+| We use this information to monitor and improve the Service and business, resolve issues, measure the effectiveness of our advertising campaigns, deliver personalized advertisements, and to inform the development of new products and services. | We will only use your personal information in this way to the extent you give us your consent to do so. | |
+
+(c) **Log files and information about your device**. We also collect information about the tablet, smartphone or other electronic device you use to connect to the Service. This information can include details about the operating systems, browsers and applications connected to the Service through the device and your IP address.
+
+| **How we may use the Personal Information** | **Legal Bases for Processing** | **Recipients of Personal Information** |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| We use information about how you use and connect to the Service to present the Service to you on your device. | The processing is necessary for performance of a contract with you, namely our Terms of Service. If you access the Service as an authorized user of another customer, the processing is necessary for our and the customer's legitimate interests, namely presenting the Service to you on your device. | We may share this information with the following service providers through the provision of the Service: Posthog, Plausible, Hubspot, Fly.io, Vercel, Sentry, Google LLC, Hex.tech, and Amazon Web Services. |
+| We use this information to identify and detect multiple attempts to access the Service to detect fraudulent use of the Service, attempts to breach the security of the Service and to ensure that the Service does not get overloaded. | The processing is necessary for our legitimate interests, namely maintaining the security and integrity of the Service. | |
+| We use this information to monitor and improve the Service and business, resolve issues and to inform the development of new products and services. | We will only use your personal information in this way to the extent you give us your consent to do so. | |
+
+We may link or combine the personal information we collect about you and the information we collect automatically.
+
+We may anonymize and aggregate any of the personal information we collect (so that it does not directly identify you). We may use anonymized information for purposes that include testing our IT systems, research, data analysis, and improving the Service. We may also share such anonymized and aggregated information with others.
+
+### 3. How long will we store your personal information
+
+We will usually store the personal information we collect about you for no longer than necessary for the purposes set out above, in accordance with our legal obligations and legitimate business interests.
+
+The criteria used to determine the period for which personal information about you will be retained varies depending on the legal basis under which we process the personal information:
+
+(a) **Legitimate Interests**. Where we are processing personal information based on our legitimate interests, we generally will retain such information for a reasonable period of time based on the particular interest, taking into account the fundamental interests and the rights and freedoms of data subjects.
+
+(b) **Consent**. Where we are processing personal information based on your consent, we generally will retain the information until you withdraw your consent, or otherwise for the period of time necessary to fulfill the underlying agreement with you or provide you with the applicable service for which we process that personal information.
+
+(c) **Contract**. Where we are processing personal information based on contract, we generally will retain the information for the duration of the contract plus some additional limited period of time that is necessary to comply with law or that represents the statute of limitations for legal claims that could arise from the contractual relationship.
+
+(d) **Legal Obligation**. Where we are processing personal information based on a legal obligation, we generally will retain the information for the period of time necessary to fulfill the legal obligation.
+
+(e) **Legal Claim**. We may need to apply a “legal hold” that retains information beyond our typical retention period where we face threat of legal claim. In that case, we will retain the information until the hold is removed, which typically means the claim or threat of claim has been resolved.
+
+(f) **Contact information** – if you have an account with us, we retain this for as long as you have an account on our services, and for 60 days after you close your account.
+
+In all cases, in addition to the purposes and legal bases, we consider the amount, nature and sensitivity of the personal information, as well as the potential risk of harm from unauthorized use or disclosure of your personal information.
+
+### 4. Recipients of Personal Information
+
+In addition to the recipients listed above, we may also share your personal information with the following:
+
+| **Recipients** | **Why we share your personal information with these recipients** | **How these recipients will use your personal information** |
+| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Service providers | We will share your personal information with third party vendors and other service providers that perform services for us or on our behalf, which may include mailing, email or chat services, payment and billing services, fraud prevention, web hosting, or providing analytic services. | These recipients will use your personal information as processors on our instructions. |
+| Advisors | We may share your personal information with companies that provide professional and advisory services to us, such as legal and accounting services. | These recipients will use your personal information to provide professional services to us. The lawful basis we rely on for sharing personal information with these recipients is that the sharing is necessary for our legitimate interests, namely receiving professional advice. |
+| Affiliates | We will share personal information with other companies owned by or under common ownership as Supabase, including our subsidiaries (i.e., any organization we own or control) and our ultimate holding company (i.e., any organization that owns or controls us) and any subsidiaries it owns. | These companies will use your personal information in the same way as we can under these Privacy Disclosures. The lawful basis we rely on for sharing your personal information is that it is necessary for our legitimate interests, namely providing global support and management of the Service. |
+| Purchasers and third parties in connection with a business transaction. | Your personal information may be disclosed to third parties in connection with a transaction, such as a merger, sale of assets or shares, reorganization, financing, change of control or acquisition of all or a portion of our business. For instance, if we sell the Service to a third party, we will share the personal information we have collected through the Service with that buyer. | These recipients will use your personal information to complete a transaction to buy all or the part of our business that includes the Service. The lawful basis for sharing personal information with these recipients is that it is necessary for our and the recipient's legitimate interests, namely completing a transaction to buy all or part of our business. |
+| Law enforcement, regulators and other parties for legal reasons. | we may share your personal information with third parties as required by law or if we reasonably believe that such action is necessary to (i) comply with the law and the reasonable requests of law enforcement; (ii) detect and investigate illegal activities and breaches of agreements, including our Terms; and/or (iii) exercise or protect the rights, property, or personal safety of Supabase, its users or others. | These recipients will use your personal information in the performance of their regulatory or law enforcement role. The lawful basis we rely on for sharing personal information with these recipients is that the processing is either necessary to comply with a legal obligation to which we are subject, or is necessary for our legitimate interests, namely enforcing our rights or complying with requests from regulatory authorities. |
+
+### 5. Marketing and Advertising
+
+From time to time we may contact you with information about our services, including sending you marketing messages and asking for your feedback on our services. Most marketing messages we send will be by email.
+
+We rely on your consent for the following marketing-related purposes: (a) sending you marketing communications; (b) using approximate location information to determine which communications are relevant to you; and (c) combining personal information we have collected from different sources to determine which communications are relevant to you. These consents are independent of one another, and you may give or withdraw any of them without affecting the others.
+
+Our marketing emails may include tracking technologies to help us understand whether an email was opened or a link was clicked within the email. We may also use tracking technologies to measure the effectiveness of our advertising campaigns and tailor ads specifically to you.
+
+We will only use these tracking technologies if you have given us your consent to do so. You can withdraw your consent at a later date by clicking on the unsubscribe link at the bottom of our marketing emails.
+
+### 6. Storing and Transferring your Personal Information
+
+**Security**. We implement appropriate technical and organizational measures to protect your personal information against accidental or unlawful destruction, loss, change or damage. All personal information we collect will be stored by our cloud hosting provider on secure servers. We will never requesting credit or debit card information or national identification numbers from you through unsolicited emails or phone calls.
+
+**International Transfers of your Personal Information**. The personal information we collect may be transferred to and stored in countries outside of the jurisdiction you are in where we and our third party service providers have operations, including the United States and Singapore.
+
+These international transfers of your personal information will be made pursuant to appropriate safeguards in accordance with applicable law:
+
+| Where we may transfer your personal information | Safeguards that apply to that transfer |
+| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| United States | The transfer is subject to standard contractual clauses approved by the European Commission or the UK Information Commissioner for the transfer of personal information. |
+| Singapore | The transfer is subject to standard contractual clauses approved by the European Commission or the UK Information Commissioner for the transfer of personal information. |
+
+If you wish to enquire further about these safeguards used, please contact us using the details set out at the end of these Privacy Disclosures.
+
+### 7. Your rights in respect of your personal information
+
+In accordance with applicable privacy law, you have the following rights in respect of your personal information that we hold:
+
+1. **Right of access**. You have the right to obtain:
+ 1. confirmation of whether, and where, we are processing your personal information;
+ 2. information about the categories of personal information we are processing, the purposes for which we process your personal information and information as to how we determine applicable retention periods;
+ 3. information about the categories of recipients with whom we may share your personal information; and
+ 4. a copy of the personal information we hold about you.
+2. **Right of portability**. You have the right, in certain circumstances, to receive a copy of the personal information you have provided to us in a structured, commonly used, machine-readable format that supports re-use, or to request the transfer of your personal information to another person.
+3. **Right to rectification**. You have the right to obtain rectification of any inaccurate or incomplete personal information we hold about you without undue delay.
+4. **Right to erasure**. You have the right, in some circumstances, to require us to erase your personal information without undue delay if the continued processing of that personal information is not justified.
+5. **Right to restriction**. You have the right, in some circumstances, to require us to limit the purposes for which we process your personal information if the continued processing of the personal information in this way is not justified, such as where the accuracy of the personal information is contested by you.
+6. **Right to withdraw consent**. There are certain circumstances where we require your consent to process your personal information. In these instances, and if you have provided consent, you have the right to withdraw your consent. If you withdraw your consent, this will not affect the lawfulness of our use of your personal information before your withdrawal.
+
+**You also have the right to object to any processing based on our legitimate interests where there are grounds relating to your particular situation. There may be compelling reasons for continuing to process your personal information, and we will assess and inform you if that is the case. You can object to marketing activities for any reason.**
+
+You also have the right to lodge a complaint to your local data protection authority. If you are based in the European Union, information about how to contact your local data protection authority is available [here](http://ec.europa.eu/justice/data-protection/bodies/authorities/index_en.htm). If you are based in the UK or Switzerland, your local data protection authorities are the UK Information Commissioner's Office (https://ico.org.uk/global/contact-us/) and the Swiss Federal Data Protection and Information Commissioner (https://www.edoeb.admin.ch/edoeb/en/home/the-fdpic/contact/address.html).
+
+If you wish to exercise one of these rights, please contact us using the contact details at the end of these Privacy Disclosures.
+
+Due to the confidential nature of data processing we may ask you to verify your identity when exercising the above rights.
+
+### 8. Cookies and similar technologies used on our European Services
+
+**Cookies**
+
+We use the following types of cookies:
+
+| Cookie | Type of cookie | When is the cookie dropped? | How long does the cookie stay on my device? | Purpose of the cookie | Links to respective privacy notices |
+| ------------------- | ------------------ | -------------------------------------------------------------- | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Stripe | Strictly necessary | When you access the payment interface on our Service. | 30 minutes | Detecting and preventing fraudulent payments and transactions. | [Stripe Cookie Settings](https://stripe.com/en-gb-sg/cookie-settings) |
+| Stripe | Strictly necessary | When you access the payment interface on our Service. | 1 year | Detecting and preventing fraudulent payments and transactions. | [Stripe Cookie Settings](https://stripe.com/en-gb-sg/cookie-settings) |
+| Stripe | Strictly necessary | When you access the payment interface on our Service. | 2 years | Detecting and preventing fraudulent payments and transactions. | [Stripe Cookie Settings](https://stripe.com/en-gb-sg/cookie-settings) |
+| Cloudflare | Strictly necessary | When you first access the Site. | 30 minutes | Identify and block bots from accessing the Service. | [Cloudflare Cookies](https://developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies/) |
+| Cloudflare | Strictly necessary | When you first access the Site. | End of Session | Manage traffic to our Service to ensure that it does not get overloaded. | [Cloudflare Cookies](https://developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies/) |
+| Youtube | Strictly necessary | When you view a Youtube embedded video on our Site. | End of Session | To display embedded videos to you on our Site. | [Google Cookie Policy](https://policies.google.com/technologies/cookies) |
+| hCaptcha | Strictly necessary | When you respond to a CAPTCHA to prove you are not a robot. | End of Session | To record your responses to the CAPTCHA and grant you access to certain areas of the Service. | [hCaptcha Privacy Policy](https://www.hcaptcha.com/privacy) |
+| Posthog | Analytics | When you access the Service. | 1 year | To monitor and analyze how you use the Service. | [Posthog Privacy Policy](https://posthog.com/privacy) |
+| Google Analytics 4 | Analytics | When you first access the Site. | 2 years (\_ga, FPID), 20 hours (\_ga\*\_, FPLC) | To measure ad campaign performance and deliver personalized ads upon consent. | [Google Analytics Privacy](https://support.google.com/analytics/answer/6004245) and [Google's use of cookies](https://policies.google.com/technologies/cookies) |
+| Google Ads | Advertising | When you visit the Site after interacting with one of our ads. | 90 days | To measure ad campaign performance and deliver personalized ads upon consent. | [Google Ads Privacy](https://policies.google.com/technologies/partner-sites) |
+| \_sb_first_referrer | Analytics | When you first visit the Site from an external source. | 365 days | Preserves original external referrer, UTM parameters, and ad-network click identifiers (e.g. gclid, fbclid) when navigating from marketing site to dashboard. Used for internal analytics only; no third-party sharing. | N/A (first-party) |
+| Freebuff | Advertising | When you visit the Site after interacting with Freebuff ads. | 30 days | To measure ad campaign performance and attribute conversions to ad clicks upon consent. | [Freebuff Privacy Policy](https://freebuff.com/privacy-policy) |
+
+Cookies are pieces of code that we transfer to your computer's hard disk for record-keeping purposes. The cookies listed as strictly necessary are required for the operation of the Service, such as cookies that enable you to log in to secure areas of the Service.
+
+We use Analytics cookies to collect information to assess how our Service is used. We will only do so, however, only if you give us your consent to do so. Manage preferences
+
+Most browsers also allow you to change your cookie settings to block certain cookies. Depending on your mobile device and operating system, you may not be able to delete or block all cookies. Please note that if you choose to refuse all cookies you may not be able to use the full functionality of our Service. These settings will typically be found in the "options" or "preferences" menu of your browser. In order to understand these settings, the following links may be helpful, otherwise you should use the "Help" option in your browser for more details.
+
+- [Cookie settings in Internet Explorer](https://support.microsoft.com/en-gb/help/278835/how-to-delete-cookie-files-in-internet-explorer)
+- [Cookie settings in Firefox](http://support.mozilla.org/en-US/kb/cookies)
+- [Cookie settings in Chrome](https://support.google.com/chrome/answer/95647?hl=en)
+- [Cookies settings in Safari web](https://support.apple.com/en-gb/guide/safari/manage-cookies-and-website-data-sfri11471/mac) and [iOS](https://support.apple.com/en-gb/HT201265).
+
+If you would like to find out more about cookies and other similar technologies, please visit [allaboutcookies.org](http://www.allaboutcookies.org).
+
+Please note that deleting or blocking cookies may not be effective for all types of tracking technologies, such as Local Storage Objects (LSOs) like HTML5.
diff --git a/apps/www/pages/privacy.tsx b/apps/www/pages/privacy.tsx
index 11940a8c612..070b2b11d15 100644
--- a/apps/www/pages/privacy.tsx
+++ b/apps/www/pages/privacy.tsx
@@ -7,6 +7,7 @@ import PageHeader from '~/components/Sections/PageHeader'
import V1 from '~/data/legal/privacy/v1.mdx'
import V2 from '~/data/legal/privacy/v2.mdx'
import V3 from '~/data/legal/privacy/v3.mdx'
+import V4 from '~/data/legal/privacy/v4.mdx'
import mdxComponents from '~/lib/mdx/mdxComponents'
import { NextSeo } from 'next-seo'
@@ -16,6 +17,7 @@ const meta = {
}
const versions: LegalDocVersion[] = [
+ { id: 'v4', label: 'Version 4', effectiveDate: 'September 16, 2026', Component: V4 },
{ id: 'v3', label: 'Version 3', effectiveDate: 'May 13, 2026', Component: V3 },
{ id: 'v2', label: 'Version 2', effectiveDate: 'March 16, 2026', Component: V2 },
{ id: 'v1', label: 'Version 1', effectiveDate: 'May 28, 2025', Component: V1 },
From 99be7f92ced91cf0ac4f542f9490d51cda36da47 Mon Sep 17 00:00:00 2001
From: "claude[bot]" <209825114+claude[bot]@users.noreply.github.com>
Date: Wed, 16 Sep 2026 17:51:25 +0800
Subject: [PATCH 087/107] feat(studio): add Privacy Policy update notice
(#50397)
## Summary
Adds a compact Privacy Policy update notice for signed-in Studio users
on organization landing pages.
- Shows on `/org`, `/organizations`, and `/org/:slug`
- Opens the approved policy explanation in a dialog
- Links to the Privacy Policy and `privacy@supabase.com`
- Persists acknowledgement in a dated local storage key
- Stays off project and organization settings routes so it cannot cover
product controls
## Why
The Privacy Policy changes the data controller from Supabase, Inc. to
Supabase Pte. Ltd. User rights and protections are unchanged.
This restores the established authenticated Studio notification pattern:
- [#35923](https://github.com/supabase/supabase/pull/35923): May 2025
Privacy Policy notice
- [#43681](https://github.com/supabase/supabase/pull/43681) and
[#43889](https://github.com/supabase/supabase/pull/43889): March 2026
Privacy Policy notice and design pass
- [#45632](https://github.com/supabase/supabase/pull/45632): May 2026
Terms of Service notice
- [#48524](https://github.com/supabase/supabase/pull/48524): current
reusable Studio banner stack
## Release order
The policy content and Studio notice deploy independently. Keep this PR
in draft until [#50392](https://github.com/supabase/supabase/pull/50392)
is approved, merged, and live. The notice appears immediately when this
Studio change deploys.
## To test
1. Open Studio on `/organizations` or an organization project-list page.
2. Confirm the compact Privacy Policy notice appears.
3. Open **Learn more** and confirm the dialog copy and both links.
4. Select **Understood** or close the notice.
5. Reload and confirm the notice remains dismissed.
6. Remove `privacy-policy-update-2026-09-16-dismissed` from local
storage and confirm the notice returns.
7. Open a project route and confirm the notice is absent.
## Verification
- Prettier passes on changed files.
- ESLint passes on changed Studio files.
- Focused Vitest suites pass: 25 tests.
- Studio Unit Tests & Build Check passes.
- TypeScript & Lint, UI Tests, Studio Docker Build, dead-code, ratchet,
and validation workflows pass.
- All four self-hosted Studio E2E shards pass for both router
implementations.
- All deploy previews pass.
- The Studio preview rendered the compact notice on the organization
landing page without console errors. The dialog and dismissal flow still
need an authenticated browser pass after the session redirected to
sign-in.
A direct local Studio TypeScript check reaches one existing unrelated
error in
`packages/ui-patterns/src/McpUrlBuilder/components/InstructionBlocks.tsx`;
no changed file reports an error and the required TypeScript CI workflow
passes.
## Measurement
Success means signed-in users can find the updated policy from the
organization landing experience without interrupting project work. The
dated dismissal key confirms acknowledgement locally. CI protects the
non-blocking route scope, and Privacy can monitor questions sent to
`privacy@supabase.com` after release.
---------
Co-authored-by: Claude
Co-authored-by: Pamela Chia
---
.../interfaces/App/AppBannerWrapper.tsx | 27 +++++-
.../interfaces/App/AppBannerWrapper.utils.ts | 8 ++
.../ui/BannerStack/BannerStackProvider.tsx | 1 +
.../BannerPrivacyPolicyUpdate.test.tsx | 55 +++++++++++
.../Banners/BannerPrivacyPolicyUpdate.tsx | 95 +++++++++++++++++++
.../App/AppBannerWrapper.utils.test.ts | 18 +++-
packages/common/constants/local-storage.ts | 1 +
7 files changed, 203 insertions(+), 2 deletions(-)
create mode 100644 apps/studio/components/ui/BannerStack/Banners/BannerPrivacyPolicyUpdate.test.tsx
create mode 100644 apps/studio/components/ui/BannerStack/Banners/BannerPrivacyPolicyUpdate.tsx
diff --git a/apps/studio/components/interfaces/App/AppBannerWrapper.tsx b/apps/studio/components/interfaces/App/AppBannerWrapper.tsx
index 2c05bd85b65..370fd7d968d 100644
--- a/apps/studio/components/interfaces/App/AppBannerWrapper.tsx
+++ b/apps/studio/components/interfaces/App/AppBannerWrapper.tsx
@@ -8,11 +8,12 @@ import {
} from 'ui-patterns/Banners/Select26Promotion'
import { OrganizationResourceBanner } from '../Organization/HeaderBanner'
-import { isLogsOrObservabilityPath } from './AppBannerWrapper.utils'
+import { isLogsOrObservabilityPath, isOrganizationLandingPath } from './AppBannerWrapper.utils'
import { ClockSkewBanner } from '@/components/layouts/AppLayout/ClockSkewBanner'
import { NoticeBanner } from '@/components/layouts/AppLayout/NoticeBanner'
import { StatusPageBanner } from '@/components/layouts/AppLayout/StatusPageBanner'
import { BannerLogsAllDeprecation } from '@/components/ui/BannerStack/Banners/BannerLogsAllDeprecation'
+import { BannerPrivacyPolicyUpdate } from '@/components/ui/BannerStack/Banners/BannerPrivacyPolicyUpdate'
import { BannerSelect2026 } from '@/components/ui/BannerStack/Banners/BannerSelect2026'
import {
SELECT_26_BANNER_PRIORITY,
@@ -45,6 +46,9 @@ export const AppBannerWrapper = ({ children }: PropsWithChildren<{}>) => {
false
)
+ const [privacyPolicyUpdateAcknowledged, , { isSuccess: isPrivacyPolicyDismissalLoaded }] =
+ useLocalStorageQuery(LOCAL_STORAGE_KEYS.PRIVACY_POLICY_UPDATE, false)
+
const [isSelect26BannerDismissed, , { isSuccess: isSelect26DismissalLoaded }] =
useLocalStorageQuery(SELECT_26_STUDIO_DISMISSAL_KEY, false)
const isSelect26PromotionActive = useSelect26PromotionActive()
@@ -92,6 +96,27 @@ export const AppBannerWrapper = ({ children }: PropsWithChildren<{}>) => {
}
}, [TOSUpdateAcknowledged, isSuccess, addBanner, dismissBanner])
+ useEffect(() => {
+ if (!isPrivacyPolicyDismissalLoaded || pathname == null) return
+
+ if (isOrganizationLandingPath(pathname) && !privacyPolicyUpdateAcknowledged) {
+ addBanner({
+ id: BANNER_ID.PRIVACY_POLICY_UPDATE,
+ isDismissed: false,
+ content:
+ {children}
+
+ )
+
+ return render(
+
+
+ Notice
+
+
+
+ We've updated our Privacy Policy
+
+ The data controller is now Supabase Pte. Ltd. Your rights and protections are unchanged.
+
+
+
+ )
+}
+
+const PrivacyPolicyUpdateDialog = ({ onAcknowledge }: { onAcknowledge: () => void }) => {
+ return (
+
+ )
+}
diff --git a/apps/studio/tests/components/interfaces/App/AppBannerWrapper.utils.test.ts b/apps/studio/tests/components/interfaces/App/AppBannerWrapper.utils.test.ts
index 12716cda236..bdb577a3881 100644
--- a/apps/studio/tests/components/interfaces/App/AppBannerWrapper.utils.test.ts
+++ b/apps/studio/tests/components/interfaces/App/AppBannerWrapper.utils.test.ts
@@ -1,6 +1,9 @@
import { describe, expect, test } from 'vitest'
-import { isLogsOrObservabilityPath } from '@/components/interfaces/App/AppBannerWrapper.utils'
+import {
+ isLogsOrObservabilityPath,
+ isOrganizationLandingPath,
+} from '@/components/interfaces/App/AppBannerWrapper.utils'
describe('isLogsOrObservabilityPath', () => {
test.each([
@@ -26,3 +29,16 @@ describe('isLogsOrObservabilityPath', () => {
expect(isLogsOrObservabilityPath(pathname)).toBe(false)
})
})
+
+describe('isOrganizationLandingPath', () => {
+ test.each(['/org', '/organizations', '/org/my-org', '/org/my-org/'])('matches %s', (pathname) => {
+ expect(isOrganizationLandingPath(pathname)).toBe(true)
+ })
+
+ test.each([undefined, null, '', '/project/abc', '/org/my-org/general', '/organizations/new'])(
+ 'does not match %s',
+ (pathname) => {
+ expect(isOrganizationLandingPath(pathname)).toBe(false)
+ }
+ )
+})
diff --git a/packages/common/constants/local-storage.ts b/packages/common/constants/local-storage.ts
index 0ffda24c5ca..23808138393 100644
--- a/packages/common/constants/local-storage.ts
+++ b/packages/common/constants/local-storage.ts
@@ -80,6 +80,7 @@ export const LOCAL_STORAGE_KEYS = {
// Notice banner keys
API_KEYS_FEEDBACK_DISMISSED: (ref: string) => `supabase-api-keys-feedback-dismissed-${ref}`,
TERMS_OF_SERVICE_UPDATE: 'terms-of-service-update-2026-08-01',
+ PRIVACY_POLICY_UPDATE: 'privacy-policy-update-2026-09-16-dismissed',
SUPAVISOR_MAINTENANCE: (ref: string) => `supavisor-maintenance-2026-06-09-${ref}`,
REPORT_DATERANGE: 'supabase-report-daterange',
PROJECT_PAUSING_STARTED_AT: (ref: string) => `supabase-project-pausing-started-at-${ref}`,
From 240bfce7f63ed4141fedb5ba9e2a3e85cc5992e6 Mon Sep 17 00:00:00 2001
From: Alaister Young
Date: Wed, 16 Sep 2026 20:18:28 +1000
Subject: [PATCH 088/107] [FE-4198] feat(studio): select a range of logs with
shift-click (#50381)
Shift-clicking a log row checkbox now selects every row between the last
clicked row and the clicked one, so you can grab a consecutive block of
logs to copy without checking each one. Applies everywhere the shared
`LogTable` renders: Postgres/API/Auth/Edge Functions logs and the Logs
Explorer.
**Added:**
- `getShiftClickSelection` in `Logs.utils.ts`: pure helper that computes
the next selection from the ordered row keys, the current selection, the
anchor row, and the clicked row. Adds the inclusive range in either
direction. If the whole range is already selected it deselects the range
instead. Falls back to a plain toggle when there's no usable anchor.
Covered by unit tests, plus `LogTable` component tests for range select,
the no-anchor fallback, anchor clearing, and range deselect.
**Changed:**
- `LogTable` tracks the last toggled row as the range anchor (a ref,
since it's only read in handlers). The anchor is set by plain clicks,
shift-clicks, and the Shift+Space row toggle, and cleared whenever the
selection becomes empty (toggling off the last row, plain row click,
Escape, action bar clear, select-all then deselect-all, or a new query
loading).
- The checkbox cell handles `onClick` instead of `onCheckedChange` so
the shift key is available. Keyboard Space on a focused checkbox still
toggles it, since Radix dispatches a click for it.
- A shift mousedown on the checkbox cell is prevented so the browser
doesn't start a text selection across rows.
Unified Logs has its own row selection (TanStack Table) and is not
changed here.
## To test
- Open any log page with a decent number of rows, e.g. Postgres logs.
Click one checkbox, then shift-click a checkbox several rows below.
Every row in between should be checked and the action bar should show
the count. Repeat upward.
- Shift-click a range that's already fully selected: the range should
clear, and rows outside it stay as they were.
- Plain-click a row's message text (not the checkbox): side panel opens
and the selection clears. A following shift-click should just toggle
that one row.
- Press Escape or the action bar's clear button, then shift-click: also
just a single toggle.
- Focus a row with the arrow keys, press Shift+Space, then shift-click a
lower checkbox: the range should extend from the keyboard-toggled row.
- Tab to a checkbox and press Space: it should still toggle.
- After a shift-click, confirm no text is highlighted across the rows.
- Copy as JSON/Markdown/CSV still copies the selected rows in display
order.
## Summary by CodeRabbit
- **New Features**
- Added shift-click range selection to the logs table for selecting or
deselecting consecutive rows.
- Preserved single-row selection when range selection is unavailable.
- Improved selection behavior when clearing selections or changing log
queries, preventing stale range anchors.
- **Tests**
- Added coverage for forward and reverse range selection, deselection,
partial selections, fallback behavior, and input immutability.
---------
Co-authored-by: Alaister Young <10985857+alaister@users.noreply.github.com>
---
.../interfaces/Settings/Logs/LogTable.tsx | 43 +++++--
.../Settings/Logs/Logs.utils.test.ts | 117 ++++++++++++++++++
.../interfaces/Settings/Logs/Logs.utils.ts | 49 ++++++++
.../tests/features/logs/LogTable.test.tsx | 77 ++++++++++++
4 files changed, 278 insertions(+), 8 deletions(-)
diff --git a/apps/studio/components/interfaces/Settings/Logs/LogTable.tsx b/apps/studio/components/interfaces/Settings/Logs/LogTable.tsx
index 4a23d3783b1..52826144ea3 100644
--- a/apps/studio/components/interfaces/Settings/Logs/LogTable.tsx
+++ b/apps/studio/components/interfaces/Settings/Logs/LogTable.tsx
@@ -30,6 +30,7 @@ import {
formatLogsAsCsv,
formatLogsAsJson,
formatLogsAsMarkdown,
+ getShiftClickSelection,
isDefaultLogPreviewFormat,
} from './Logs.utils'
import LogSelection from './LogSelection'
@@ -106,6 +107,8 @@ export const LogTable = ({
const [selectedLogId] = useSelectedLog()
const [selectedRow, setSelectedRow] = useState(null)
const [selectedRows, setSelectedRows] = useState>(new Set())
+ // Last row key the user toggled, used as the start of a shift-click range
+ const selectionAnchorRef = useRef(null)
const [copiedFormat, setCopiedFormat] = useState(null)
const triggerRef = useRef(null)
const [activeRow, setActiveRow] = useState(null)
@@ -196,13 +199,24 @@ export const LogTable = ({
minWidth: 32,
renderCell: ({ row }) => {
const key = getRowKey(row)
- const toggle = () => {
- const next = new Set(selectedRows)
- if (next.has(key)) {
- next.delete(key)
+ const toggle = (isShiftClick: boolean) => {
+ let next: Set
+ if (isShiftClick) {
+ next = getShiftClickSelection({
+ orderedKeys: logDataRows.map(getRowKey),
+ selectedKeys: selectedRows,
+ anchorKey: selectionAnchorRef.current,
+ targetKey: key,
+ })
} else {
- next.add(key)
+ next = new Set(selectedRows)
+ if (next.has(key)) {
+ next.delete(key)
+ } else {
+ next.add(key)
+ }
}
+ selectionAnchorRef.current = next.size > 0 ? key : null
setSelectedRows(next)
if (next.size > 0) {
setSelectedRow(null)
@@ -212,16 +226,23 @@ export const LogTable = ({
return (
{
+ if (e.shiftKey) e.preventDefault()
+ }}
onClick={(e) => {
e.stopPropagation()
- toggle()
+ toggle(e.shiftKey)
}}
>
e.stopPropagation()}
- onCheckedChange={toggle}
+ // use onClick instead of onCheckedChange so the shift key is available for range selection
+ onClick={(e: React.MouseEvent) => {
+ e.stopPropagation()
+ toggle(e.shiftKey)
+ }}
/>
)
@@ -292,6 +313,7 @@ export const LogTable = ({
(row: LogData) => {
// Regular single click — clear multi-select, open side panel
setSelectedRows(new Set())
+ selectionAnchorRef.current = null
setSelectedRow(row)
onSelectedLogChange?.(row)
},
@@ -367,6 +389,7 @@ export const LogTable = ({
() => {
if (selectedRows.size === logDataRows.length) {
setSelectedRows(new Set())
+ selectionAnchorRef.current = null
} else {
setSelectedRows(new Set(logDataRows.map((row) => getRowKey(row))))
setSelectedRow(null)
@@ -387,6 +410,7 @@ export const LogTable = ({
} else {
next.add(key)
}
+ selectionAnchorRef.current = next.size > 0 ? key : null
setSelectedRows(next)
},
{ enabled: selectedRow !== null }
@@ -405,6 +429,7 @@ export const LogTable = ({
SHORTCUT_IDS.LOGS_PREVIEW_EXIT_SELECTION,
() => {
setSelectedRows(new Set())
+ selectionAnchorRef.current = null
;(document.activeElement as HTMLElement | null)?.blur()
},
{ enabled: !selectionOpen && selectedRows.size > 0 }
@@ -427,6 +452,7 @@ export const LogTable = ({
useEffect(() => {
if (isLoading) {
setSelectedRows(new Set())
+ selectionAnchorRef.current = null
}
}, [isLoading])
@@ -583,6 +609,7 @@ export const LogTable = ({
sqlQuery={sqlQuery}
onClear={() => {
setSelectedRows(new Set())
+ selectionAnchorRef.current = null
}}
/>
${escaped}`, '')
+ if (preview.length < diff.length) {
+ summary.push('Diff preview truncated. See the verification step logs for the full diff.', '')
+ }
+ }
+
+ if (summaryPath) await appendFile(summaryPath, `${summary.join('\n')}\n`)
+}
+
export async function verifyProductionTypes() {
const temporaryDirectory = await mkdtemp(join(tmpdir(), 'api-types-'))
const generatedTypesDirectory = join(temporaryDirectory, 'types')
@@ -120,6 +170,7 @@ export async function verifyProductionTypes() {
})
if (changedTypes.length > 0) {
+ await reportTypeDifferences(changedTypes, { generatedTypesDirectory, typesDirectory })
throw new Error(`Committed API types do not match production: ${changedTypes.join(', ')}`)
}
} finally {
diff --git a/packages/api-types/scripts/verify-production-types.test.mjs b/packages/api-types/scripts/verify-production-types.test.mjs
index f2c67b2cecc..97f7e93932f 100644
--- a/packages/api-types/scripts/verify-production-types.test.mjs
+++ b/packages/api-types/scripts/verify-production-types.test.mjs
@@ -1,7 +1,63 @@
import assert from 'node:assert/strict'
+import { mkdir, mkdtemp, readFile, rm, writeFile } from 'node:fs/promises'
+import { tmpdir } from 'node:os'
+import { join } from 'node:path'
import test from 'node:test'
-import { fetchOpenApiSpecifications, findMismatchedTypes } from './verify-production-types.mjs'
+import {
+ fetchOpenApiSpecifications,
+ findMismatchedTypes,
+ reportTypeDifferences,
+} from './verify-production-types.mjs'
+
+test('reports unified diffs in logs and appends an escaped, bounded Actions summary', async (t) => {
+ const directory = await mkdtemp(join(tmpdir(), 'api-types-report-'))
+ t.after(() => rm(directory, { recursive: true, force: true }))
+ const typesDirectory = join(directory, 'committed')
+ const generatedTypesDirectory = join(directory, 'production')
+ const summaryPath = join(directory, 'summary.md')
+ await mkdir(typesDirectory)
+ await mkdir(generatedTypesDirectory)
+ await writeFile(summaryPath, 'Existing summary\n')
+ await writeFile(join(typesDirectory, 'api-v1.d.ts'), 'type A = string\n')
+ await writeFile(join(generatedTypesDirectory, 'api-v1.d.ts'), 'type A = Array- The Explorer is a new unified workspace for querying your data and chatting with the - Assistant, and is an early preview of where we're heading with the SQL Editor. -
-
- Notebooks are the first new feature of the Explorer — mix query cells and markdown notes in
- a single document, so your queries and context stay together. Use them to write runbooks,
- document incidents, build reusable reports, and more!
+ The Explorer is a unified workspace for interacting with your database and logs via SQL,
+ chat and a new feature we are calling Notebooks.{' '}
+
+ Notebooks aim to replace Snippets and Custom Reports. They can contain one or many SQL + queries with surrounding markdown content. You can query both your own database and project + logs which means they can be used for observability, growth tracking, recurring tasks that + need extra context etc. They can be managed and run in Studio as well as by the Supabase + Assistant and later your own agent via code or MCP. Snippets are not visible in + Explorer, we are instead looking at a migration path from Snippets -> Notebooks if + needed. +
++ Explorer is a glimpse at a future where reports and insights are generated on demand, + personalized to your needs, with Notebooks being the first primitive. +
+Enabling this preview will:
-
From 9cdd412babfa8eab995d74b348b1ae1cf313d94c Mon Sep 17 00:00:00 2001
From: Julian Domke <68325451+juleswritescode@users.noreply.github.com>
Date: Wed, 16 Sep 2026 14:16:46 +0200
Subject: [PATCH 091/107] feat(stripe-atlas): mock-up dashboard to enable live
testing (#50327)
---
apps/studio/TANSTACK_MIGRATION.md | 1 +
.../StripeAtlasApplication.tsx | 116 ++++++++++++++++++
.../StripeAtlasApplicationForm.tsx | 106 ++++++++++++++++
.../studio/pages/stripe-atlas-application.tsx | 25 ++++
apps/studio/routeTree.gen.ts | 21 ++++
.../routes/stripe-atlas-application.tsx | 11 ++
6 files changed, 280 insertions(+)
create mode 100644 apps/studio/components/interfaces/StripeAtlasApplication/StripeAtlasApplication.tsx
create mode 100644 apps/studio/components/interfaces/StripeAtlasApplication/StripeAtlasApplicationForm.tsx
create mode 100644 apps/studio/pages/stripe-atlas-application.tsx
create mode 100644 apps/studio/routes/stripe-atlas-application.tsx
diff --git a/apps/studio/TANSTACK_MIGRATION.md b/apps/studio/TANSTACK_MIGRATION.md
index 36861a50399..3eec2105199 100644
--- a/apps/studio/TANSTACK_MIGRATION.md
+++ b/apps/studio/TANSTACK_MIGRATION.md
@@ -144,6 +144,7 @@ These are the layout-only TanStack files. Most hold a single product layout comp
- [x] A `routes/aws-marketplace-onboarding.tsx` ← `pages/aws-marketplace-onboarding.tsx` **Delta vs plan:** placed at root rather than under `_app/` — page uses its own `LinkAwsMarketplaceLayout` and doesn't want `AppLayout` + `DefaultLayout` wrapping.
- [x] A `routes/claim-project.tsx` ← `pages/claim-project.tsx` **Delta vs plan:** placed at root rather than under `_app/` — page uses its own `` + `
+ Please head to the Stripe Atlas dashboard and use the "Pre-fill my application" + button. + + } + /> +
+
+
+
{isSearching && isPendingFolders && (
(
path: string,
- options?: { method?: 'GET' | 'POST' | 'PUT' | 'DELETE'; body?: Record }
+ options?: {
+ method?: 'GET' | 'POST' | 'PUT' | 'DELETE'
+ /** A JSON payload, or a string to send as a raw `text/plain` body (for object uploads) */
+ body?: Record | string
+ }
): Promise {
const storageUrl = `${env.API_URL}/storage/v1`
-
+
const headers: Record = {
apikey: env.SERVICE_ROLE_KEY,
Authorization: `Bearer ${env.SERVICE_ROLE_KEY}`,
}
- if (options?.body) {
- headers['Content-Type'] = 'application/json'
+ const isRawBody = typeof options?.body === 'string'
+ if (options?.body !== undefined) {
+ headers['Content-Type'] = isRawBody ? 'text/plain' : 'application/json'
}
const response = await fetch(`${storageUrl}${path}`, {
method: options?.method ?? 'GET',
headers,
- body: options?.body ? JSON.stringify(options.body) : undefined,
+ body: isRawBody
+ ? (options!.body as string)
+ : options?.body
+ ? JSON.stringify(options.body)
+ : undefined,
})
if (!response.ok) {
diff --git a/e2e/studio/utils/storage/index.ts b/e2e/studio/utils/storage/index.ts
index cffa68bfd69..8cfe7877a06 100644
--- a/e2e/studio/utils/storage/index.ts
+++ b/e2e/studio/utils/storage/index.ts
@@ -1,2 +1,9 @@
export { storageRequest } from './client.js'
-export { createBucket, deleteBucket, deleteAllBuckets, listBuckets } from './queries.js'
+export {
+ createBucket,
+ deleteBucket,
+ deleteAllBuckets,
+ listBuckets,
+ seedBucket,
+ uploadObject,
+} from './queries.js'
diff --git a/e2e/studio/utils/storage/queries.ts b/e2e/studio/utils/storage/queries.ts
index e518b8a3381..38e6742c647 100644
--- a/e2e/studio/utils/storage/queries.ts
+++ b/e2e/studio/utils/storage/queries.ts
@@ -52,3 +52,33 @@ export async function deleteAllBuckets(): Promise {
await deleteBucket(bucket.id)
}
}
+
+/**
+ * Uploads an object to a bucket, creating every folder in its path along the way. Storage has no
+ * standalone folders — a folder exists because an object sits under that prefix — so this is how
+ * a folder tree gets seeded.
+ *
+ * @param bucket - Bucket name / id
+ * @param objectPath - Path within the bucket, e.g. `reports/2024/q1/seed.txt`
+ * @param content - File contents (default: a short placeholder)
+ */
+export async function uploadObject(
+ bucket: string,
+ objectPath: string,
+ content: string = 'e2e fixture'
+): Promise {
+ await storageRequest(`/object/${bucket}/${objectPath}`, { method: 'POST', body: content })
+}
+
+/**
+ * Seeds a bucket with a set of object paths. Creates the bucket first when it does not exist.
+ *
+ * @param bucket - Bucket name / id
+ * @param objectPaths - Paths within the bucket to create
+ */
+export async function seedBucket(bucket: string, objectPaths: string[]): Promise {
+ await createBucket(bucket, false)
+ for (const objectPath of objectPaths) {
+ await uploadObject(bucket, objectPath)
+ }
+}
From dca96ae929fee9c6f9ab6672120186566d4d60ab Mon Sep 17 00:00:00 2001
From: Katerina Skroumpelou
Date: Wed, 16 Sep 2026 15:50:38 +0300
Subject: [PATCH 095/107] docs: add the Deno optional peer note to the server
installing page (#50412)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
## 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, one new section on the `@supabase/server` Installing page.
## What is the current behavior?
The Deno install instructions stop at `deno add jsr:@supabase/server`. A
user who then imports `@supabase/server/middleware/postgres` on Deno or
Edge Functions passes `deno check` and fails at startup with `Could not
find package 'pg'`, because Deno resolves an optional peer only when the
user's own code imports it. Nothing on the page says so.
## What is the new behavior?
A new "Optional peer dependencies on Deno" row under the JSR section
explains why, shows the bare `import 'pg'` at the top of the entry
module, gives the `deno info` check, and notes the
`--minimum-dependency-age 0` flag for same-day releases. Both
hand-maintained copies of the partial are updated and stay identical:
the spec partial for the reference site and the `docs/ref` copy for the
markdown build.
## Additional context
`pg` is the only optional peer a user can hit today. The MCP entry will
add another once it ships and gets documented then.
## Summary by CodeRabbit
* **Documentation**
* Added Deno installation guidance for Postgres middleware that requires
the optional `pg` dependency.
* Clarified that importing `pg` directly is necessary for Deno to
resolve it at runtime.
* Added commands for verifying package resolution and handling Deno’s
minimum dependency age checks.
---
apps/docs/docs/ref/server/installing.mdx | 27 +++++++++++++++++++
.../server/v1/partials/installing.mdx | 27 +++++++++++++++++++
2 files changed, 54 insertions(+)
diff --git a/apps/docs/docs/ref/server/installing.mdx b/apps/docs/docs/ref/server/installing.mdx
index 0f0df8a9b91..1da71c02eb8 100644
--- a/apps/docs/docs/ref/server/installing.mdx
+++ b/apps/docs/docs/ref/server/installing.mdx
@@ -82,3 +82,30 @@ slug: installing
+
+### Optional peer dependencies on Deno
+
+
+
+
+ Some entry points rely on optional peer dependencies. `@supabase/server/middleware/postgres` and `@supabase/server/middleware/postgres-admin` need `pg`. Deno resolves an optional peer only when your own code imports it. A pin in `deno.json` alone is not enough: `deno check` passes and the function fails at startup with `Could not find package 'pg'`.
+
+ Add a bare import once, at the top of your entry module — no separate `deno add npm:pg` or `package.json` entry is needed. `deno info` lists `npm:/pg@...` once the package is in the module graph.
+
+ Deno 2.9 and later apply a minimum dependency age to npm packages. To use a release published the same day, pass `--minimum-dependency-age 0` to `deno check`.
+
+
+
+
+
+ ```ts index.ts
+ import 'pg'
+ import { withPostgresClient } from '@supabase/server/middleware/postgres'
+ ```
+
+ ```sh Terminal
+ deno info index.ts | grep "npm:/pg@"
+ ```
+
+
+
diff --git a/apps/docs/spec/reference/server/v1/partials/installing.mdx b/apps/docs/spec/reference/server/v1/partials/installing.mdx
index 0f0df8a9b91..1da71c02eb8 100644
--- a/apps/docs/spec/reference/server/v1/partials/installing.mdx
+++ b/apps/docs/spec/reference/server/v1/partials/installing.mdx
@@ -82,3 +82,30 @@ slug: installing
+
+### Optional peer dependencies on Deno
+
+
+
+
+ Some entry points rely on optional peer dependencies. `@supabase/server/middleware/postgres` and `@supabase/server/middleware/postgres-admin` need `pg`. Deno resolves an optional peer only when your own code imports it. A pin in `deno.json` alone is not enough: `deno check` passes and the function fails at startup with `Could not find package 'pg'`.
+
+ Add a bare import once, at the top of your entry module — no separate `deno add npm:pg` or `package.json` entry is needed. `deno info` lists `npm:/pg@...` once the package is in the module graph.
+
+ Deno 2.9 and later apply a minimum dependency age to npm packages. To use a release published the same day, pass `--minimum-dependency-age 0` to `deno check`.
+
+
+
+
+
+ ```ts index.ts
+ import 'pg'
+ import { withPostgresClient } from '@supabase/server/middleware/postgres'
+ ```
+
+ ```sh Terminal
+ deno info index.ts | grep "npm:/pg@"
+ ```
+
+
+
From d82222747f2460cc2ff6e53cb975cd33c0d4dd4b Mon Sep 17 00:00:00 2001
From: "claude[bot]" <209825114+claude[bot]@users.noreply.github.com>
Date: Wed, 16 Sep 2026 12:52:08 +0000
Subject: [PATCH 096/107] Add apps/studio/public/* to misspell-fixer ignore
list (#50470)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
_Requested by **Ivan Vasilov** · [Slack
thread](https://supabase.slack.com/archives/C0161K73J1J/p1789562388651949?thread_ts=1789562388.651949&cid=C0161K73J1J)_
## 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?
Chore / CI config update.
## What is the current behavior?
**Before:** `apps/studio/public/*` files are checked by the
misspell-fixer workflow.
## What is the new behavior?
**After:** `apps/studio/public/*` files are excluded from the
misspell-fixer ignore list.
## Additional context
None.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_018p33HyRZ2GCWkmA44rJKkw
Co-authored-by: Claude
---
.misspell-fixer.ignore | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/.misspell-fixer.ignore b/.misspell-fixer.ignore
index 1b26bc40f97..a09557b4b1e 100644
--- a/.misspell-fixer.ignore
+++ b/.misspell-fixer.ignore
@@ -1,3 +1,4 @@
^./i18n
^./packages/api-types
-^./apps/www/lib/redirects.js
\ No newline at end of file
+^./apps/www/lib/redirects.js
+^./apps/studio/public/*
\ No newline at end of file
From 127e21b926726ed0044a2f39b8d46326c80d1e0e Mon Sep 17 00:00:00 2001
From: "supabase-supabase-autofixer[bot]"
<248690971+supabase-supabase-autofixer[bot]@users.noreply.github.com>
Date: Wed, 16 Sep 2026 13:03:20 +0000
Subject: [PATCH 097/107] Changes by create-pull-request action (#44860)
Automated changes by
[create-pull-request](https://github.com/peter-evans/create-pull-request)
GitHub action
Co-authored-by: ivasilov <568291+ivasilov@users.noreply.github.com>
---
apps/docs/content/guides/functions/error-codes.mdx | 2 +-
apps/studio/components/layouts/Tabs/Tabs.tsx | 2 +-
apps/studio/data/replication/rollback-tables-mutation.ts | 2 +-
apps/www/data/surveys/state-of-startups-data.json | 6 +++---
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/apps/docs/content/guides/functions/error-codes.mdx b/apps/docs/content/guides/functions/error-codes.mdx
index e6117c0592f..bcee3750644 100644
--- a/apps/docs/content/guides/functions/error-codes.mdx
+++ b/apps/docs/content/guides/functions/error-codes.mdx
@@ -159,7 +159,7 @@ export default {
body: req.body,
})
- // Creating a 'new Response()' ensures contructor checks
+ // Creating a 'new Response()' ensures constructor checks
return new Response(await res.body, {
headers: res.headers,
status: res.status,
diff --git a/apps/studio/components/layouts/Tabs/Tabs.tsx b/apps/studio/components/layouts/Tabs/Tabs.tsx
index 7191cbe0ac5..5e824df3cc2 100644
--- a/apps/studio/components/layouts/Tabs/Tabs.tsx
+++ b/apps/studio/components/layouts/Tabs/Tabs.tsx
@@ -44,7 +44,7 @@ interface EditorTabsProps {
}
// [Joshen] Will be adjusting this component to support Explorer
-// Will require quite a bit of cleaning up once Explorer supercedes SQL Editor
+// Will require quite a bit of cleaning up once Explorer supersedes SQL Editor
export const EditorTabs = ({
customTabs,
newTabButton,
diff --git a/apps/studio/data/replication/rollback-tables-mutation.ts b/apps/studio/data/replication/rollback-tables-mutation.ts
index c057baea7ff..bc6454a6c68 100644
--- a/apps/studio/data/replication/rollback-tables-mutation.ts
+++ b/apps/studio/data/replication/rollback-tables-mutation.ts
@@ -54,7 +54,7 @@ async function rollbackTables(
)
if (error) handleError(error)
- // Logic for starting the pipeline back up after a successfull rollback
+ // Logic for starting the pipeline back up after a successful rollback
if (pipelineStatusName) {
const shouldStartPipelineAfterRollback = [
PipelineStatusName.STOPPED,
diff --git a/apps/www/data/surveys/state-of-startups-data.json b/apps/www/data/surveys/state-of-startups-data.json
index 90614f9e904..5b5a78315d5 100644
--- a/apps/www/data/surveys/state-of-startups-data.json
+++ b/apps/www/data/surveys/state-of-startups-data.json
@@ -15083,7 +15083,7 @@
"count": 1
},
{
- "label": "Scaling, more demand than current solution (GAS) can accomodate",
+ "label": "Scaling, more demand than current solution (GAS) can accommodate",
"count": 1
},
{
@@ -17163,7 +17163,7 @@
"count": 1
},
{
- "label": "unkown",
+ "label": "unknown",
"count": 1
},
{
@@ -21474,7 +21474,7 @@
"count": 1
},
{
- "label": "Scaling, more demand than current solution (GAS) can accomodate",
+ "label": "Scaling, more demand than current solution (GAS) can accommodate",
"count": 1
},
{
From 795b67b6112dd8d2e953d93d41703e95fb6d1369 Mon Sep 17 00:00:00 2001
From: Maksym Ionutsa <123338468+peekknuf@users.noreply.github.com>
Date: Wed, 16 Sep 2026 15:52:33 +0200
Subject: [PATCH 098/107] Docs/clone project r2np clarifications (#50471)
## 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?
r2np docs clarifications to
https://supabase.com/docs/guides/platform/clone-project
## What is the new behavior?
## Summary by CodeRabbit
* **Documentation**
* Updated project restore guidance to clarify that binary restores copy
the entire database and may immediately run extensions, scheduled jobs,
webhooks, and wrappers.
* Added guidance for using logical restores when definitions need
inspection or removal beforehand.
* Documented that manual dead-tuple recovery is unsupported due to
potential constraint violations and data corruption.
* Added recommended recovery paths for deleted rows using physical
backups or point-in-time recovery.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
.../docs/content/guides/platform/clone-project.mdx | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/apps/docs/content/guides/platform/clone-project.mdx b/apps/docs/content/guides/platform/clone-project.mdx
index 3cbf16324d6..3b4e5f1ee20 100644
--- a/apps/docs/content/guides/platform/clone-project.mdx
+++ b/apps/docs/content/guides/platform/clone-project.mdx
@@ -57,10 +57,20 @@ Once the restoration is complete, the new project will be available in your dash
New projects are completely independent of their source, and as such can be modified and used as desired.
-
+
-As the entire database is copied to the new project, this will include all extensions that were enabled at the source. If the source project included extensions that are configured to carry out external operations—for example pg_net, pg_cron, wrappers—these should be disabled once the copy process has completed to avoid any unwanted actions from taking place.
+Restore to a new project is a binary restore: it copies the entire database, including any enabled extensions that carry out external operations (for example `pg_net`, `pg_cron`, wrappers). These jobs start running as soon as the restore completes. There's no way to exclude or pause them going into the restore.
+
+If you need to inspect or remove cron jobs, webhook triggers, or wrapper definitions before any external extension runs, use a [logical restore with the Supabase CLI](/docs/guides/platform/migrating-within-supabase/backup-restore) instead. This process is manual, and doesn't carry over the encryption root key, so Vault secrets and encrypted columns aren't readable unless you migrate the key separately.
Restoring to a new project is an excellent way to manage environments more effectively. You can use this feature to create staging environments for testing, experiment with changes without risk to production data, or swiftly recover from unexpected data loss scenarios.
+
+
+
+Recovering deleted rows by manually inspecting dead tuples (for example with `pageinspect` and `pg_surgery`) isn't supported on Supabase. It bypasses your table's constraint checks and can corrupt your data by restoring rows that violate a `CHECK`, `FOREIGN KEY`, or `UNIQUE` constraint.
+
+
+
+Restoring to a new project is the safe way to get deleted rows back. Restore from a physical backup that predates the deletion, or, if the deletion happened too recently for your last backup to have captured it, enable PITR and restore to the exact point in time before the deletion. Then copy the rows you need into your live project.
From 9bf43188f1b4fca7f3c24cfd5b82b66317e43406 Mon Sep 17 00:00:00 2001
From: Jeremias Menichelli
Date: Wed, 16 Sep 2026 13:41:16 -0300
Subject: [PATCH 099/107] feat: Create first scaffolding around search v2 and
feature flag addition (#50236)
---
.../Navigation/NavigationMenu/TopNavBar.tsx | 32 +++--
.../docs/features/SearchV2/SearchV2Dialog.tsx | 132 ++++++++++++++++++
.../features/SearchV2/SearchV2Trigger.tsx | 75 ++++++++++
apps/docs/features/SearchV2/constants.ts | 4 +
apps/docs/features/SearchV2/index.ts | 2 +
.../features/SearchV2/useSearchV2Variant.ts | 25 ++++
6 files changed, 261 insertions(+), 9 deletions(-)
create mode 100644 apps/docs/features/SearchV2/SearchV2Dialog.tsx
create mode 100644 apps/docs/features/SearchV2/SearchV2Trigger.tsx
create mode 100644 apps/docs/features/SearchV2/constants.ts
create mode 100644 apps/docs/features/SearchV2/index.ts
create mode 100644 apps/docs/features/SearchV2/useSearchV2Variant.ts
diff --git a/apps/docs/components/Navigation/NavigationMenu/TopNavBar.tsx b/apps/docs/components/Navigation/NavigationMenu/TopNavBar.tsx
index b41dbbe7896..db6ca275c1b 100644
--- a/apps/docs/components/Navigation/NavigationMenu/TopNavBar.tsx
+++ b/apps/docs/components/Navigation/NavigationMenu/TopNavBar.tsx
@@ -16,6 +16,7 @@ import { CommandMenuTriggerInput } from 'ui-patterns/CommandMenu'
import { getCustomContent } from '../../../lib/custom-content/getCustomContent'
import GlobalNavigationMenu from './GlobalNavigationMenu'
import useDropdownMenu from './useDropdownMenu'
+import { SearchV2Trigger, useSearchV2Variant } from '@/features/SearchV2'
const GlobalMobileMenu = dynamic(() => import('./GlobalMobileMenu'))
const TopNavDropdown = dynamic(() => import('./TopNavDropdown'))
@@ -28,6 +29,7 @@ const TopNavBar: FC = () => {
const [mobileMenuOpen, setMobileMenuOpen] = useState(false)
const user = useUser()
const menu = useDropdownMenu(user)
+ const searchVariant = useSearchV2Variant()
return (
<>
@@ -47,15 +49,27 @@ const TopNavBar: FC = () => {
- Search
- docs...
-
- }
- />
+ {searchVariant === 'search-v2-active' ? (
+
+ Search
+ docs...
+
+ }
+ />
+ ) : (
+
+ Search
+ docs...
+
+ }
+ />
+ )}