From 48df98258ea2f8b2b42a36404e6b09d6c6e5d58d Mon Sep 17 00:00:00 2001 From: Joshen Lim Date: Wed, 24 Sep 2025 13:37:39 +0800 Subject: [PATCH 1/4] Reinstate ignoreBuildErrors as false for studio prod (#38969) --- apps/studio/next.config.js | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/apps/studio/next.config.js b/apps/studio/next.config.js index 37c55f2be285a..dceef89f31480 100644 --- a/apps/studio/next.config.js +++ b/apps/studio/next.config.js @@ -531,8 +531,9 @@ const nextConfig = { pagesBufferLength: 100, }, typescript: { - // Typechecking is run via GitHub Action only for efficiency. - ignoreBuildErrors: true, + // On previews, typechecking is run via GitHub Action only for efficiency + // On production, we turn it on to catch errors from typecheck due to conflicting PRs getting into prod + ignoreBuildErrors: process.env.NEXT_PUBLIC_VERCEL_ENV === 'production' ? false : true, }, eslint: { // We are already running linting via GH action, this will skip linting during production build on Vercel From ef4d203d76aade9585f35ad4dc8e6f9d596b99c8 Mon Sep 17 00:00:00 2001 From: Prateek Bisht <143113996+prateekbisht23@users.noreply.github.com> Date: Wed, 24 Sep 2025 12:29:07 +0530 Subject: [PATCH 2/4] docs: update import-data guide to reflect dashboard UI change (#38675) --- apps/docs/content/guides/database/import-data.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/guides/database/import-data.mdx b/apps/docs/content/guides/database/import-data.mdx index 4d32ed592e7cb..df2a6cc0b644a 100644 --- a/apps/docs/content/guides/database/import-data.mdx +++ b/apps/docs/content/guides/database/import-data.mdx @@ -27,7 +27,7 @@ If you're importing a large dataset or importing data into production, plan ahea Supabase dashboard provides a user-friendly way to import data. However, for very large datasets, this method may not be the most efficient choice, given the size limit is 100MB. It's generally better suited for smaller datasets and quick data imports. Consider using alternative methods like pgloader for large-scale data imports. 1. Navigate to the relevant table in the [Table Editor.](/dashboard/project/_/editor) -2. Click on “Insert” then choose "Import Data from CSV" and follow the on-screen instructions to upload your CSV file. +2. Click on _+ New table_ (for new, empty projects) or _Insert_ (for existing tables), then choose _Import Data from CSV_ and follow the on-screen instructions to upload your CSV file. ### Option 2: Bulk import using pgloader From 767d65e0f56437f0c93257b41b370d1df6f12665 Mon Sep 17 00:00:00 2001 From: Joshen Lim Date: Wed, 24 Sep 2025 16:20:52 +0800 Subject: [PATCH 3/4] Revert ignoreBuildErrors (#38970) --- apps/studio/next.config.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/studio/next.config.js b/apps/studio/next.config.js index dceef89f31480..abdaf93531c3b 100644 --- a/apps/studio/next.config.js +++ b/apps/studio/next.config.js @@ -531,9 +531,9 @@ const nextConfig = { pagesBufferLength: 100, }, typescript: { - // On previews, typechecking is run via GitHub Action only for efficiency - // On production, we turn it on to catch errors from typecheck due to conflicting PRs getting into prod - ignoreBuildErrors: process.env.NEXT_PUBLIC_VERCEL_ENV === 'production' ? false : true, + // Typechecking is run via GitHub Action only for efficiency + // For production, we run typechecks separate from the build command (pnpm typecheck && pnpm build) + ignoreBuildErrors: true, }, eslint: { // We are already running linting via GH action, this will skip linting during production build on Vercel From db918bda3a3e1ed637eddb89ffc1f38c92a8c3a5 Mon Sep 17 00:00:00 2001 From: Ulme Wennberg <32614557+ulmewennberg@users.noreply.github.com> Date: Wed, 24 Sep 2025 11:55:21 +0200 Subject: [PATCH 4/4] docs: fix typo in ssl-enforcement guide (#38895) --- apps/docs/content/guides/platform/ssl-enforcement.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/guides/platform/ssl-enforcement.mdx b/apps/docs/content/guides/platform/ssl-enforcement.mdx index ee2e29fd6d552..3bb6ebaf33239 100644 --- a/apps/docs/content/guides/platform/ssl-enforcement.mdx +++ b/apps/docs/content/guides/platform/ssl-enforcement.mdx @@ -27,7 +27,7 @@ export SUPABASE_ACCESS_TOKEN="your-access-token" export PROJECT_REF="your-project-ref" # Get current SSL enforcement status -curl -X GET "https://api.supabase.com/v1/projects/$PROJECT_REF/ssl-enforceemnt" \ +curl -X GET "https://api.supabase.com/v1/projects/$PROJECT_REF/ssl-enforcement" \ -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" # Enable SSL enforcement