@supacloud/cli 0.71.1 → 0.72.0

package/README.md

@@ -532,6 +532,7 @@ supacloud-cli database query --sql "select now()"
 supacloud-cli database query --ref abc123 --file ./queries/vector-search.sql
 supacloud-cli database migration_inventory --ref abc123
 supacloud-cli database lint_migrations --dir supabase/migrations
+supacloud-cli database rebase_migrations --dir supabase/migrations --baseline_file backups/schema.sql --baseline_version 20261008000000 --output_dir supabase/migrations-rebased
 supacloud-cli database push_migrations --ref abc123 --dir supabase/migrations --dry_run
 supacloud-cli supabase migration_new --name add_accounts
 supacloud-cli supabase db_diff --schema public --name add_accounts
@@ -638,6 +639,17 @@ even when strict destructive-risk mode is not enabled.
 `CREATE/DROP INDEX CONCURRENTLY`, `VACUUM`, and other non-transactional work must
 run through an approved maintenance path outside `push_migrations`.
 
+`database rebase_migrations` is local-only and never contacts the Management
+API. Without `--write` it only prints the plan; with `--write` it writes a
+reconstructed baseline, the retained forward migrations, and a
+`migration-rebase.manifest.json` (with SHA-256 records for the complete source
+history) into a separate `--output_dir`, never the source directory. Capture and
+review a schema-only snapshot first with `--baseline_file` and
+`--baseline_version`, then use `--retain_after_version` to keep newer
+migrations. Review the baseline for omitted data backfills, reference data,
+extensions, grants, RLS, functions and triggers, replay it in a clean database,
+and archive the original directory until clean replay and remote read-back pass.
+
 Migration applications and DDL executions send PostgREST schema reload
 notifications (`NOTIFY pgrst_<ref>, 'reload schema'`) so schema changes become
 visible without a manual PostgREST restart. Responses distinguish `notified`

package/dist/index.js

@@ -213546,21 +213546,18 @@ export default app;
         scripts: { build: "vite build" },
         devDependencies: {
           "@supacloud/function-adapter": "^0.1.0",
-          "@sveltejs/kit": "^2.70.3",
+          "@sveltejs/kit": "^3.0.1",
           "@sveltejs/vite-plugin-svelte": "^7.3.0",
           svelte: "^5.57.0",
           vite: "^8.2.2"
         }
       }, null, 2) + `
-`,
-      "svelte.config.js": `import adapter from "@supacloud/function-adapter/sveltekit-adapter";
-
-export default { kit: { adapter: adapter() } };
 `,
       "vite.config.ts": `import { sveltekit } from "@sveltejs/kit/vite";
+import adapter from "@supacloud/function-adapter/sveltekit-adapter";
 import { defineConfig } from "vite";
 
-export default defineConfig({ plugins: [sveltekit()] });
+export default defineConfig({ plugins: [sveltekit({ adapter: adapter() })] });
 `,
       "src/routes/+server.ts": `export function GET() {
   return Response.json({ function: "${slug}", framework: "sveltekit-function" });
@@ -256655,7 +256652,7 @@ function registerRemoteDevTools(server2, options = {}) {
 // package.json
 var package_default = {
   name: "@supacloud/cli",
-  version: "0.71.1",
+  version: "0.72.0",
   description: "Project-scoped CLI for SupaCloud users",
   type: "module",
   main: "./dist/index.js",
@@ -256700,7 +256697,7 @@ var package_default = {
     "@graphql-tools/utils": "^12.0.3"
   },
   devDependencies: {
-    "@supacloud/elysia": "^0.23.1",
+    "@supacloud/elysia": "^0.24.1",
     "@types/bun": "^1.4.2",
     elysia: "2.0.0-beta.21",
     typescript: "^7.0.2"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supacloud/cli",
-  "version": "0.71.1",
+  "version": "0.72.0",
   "description": "Project-scoped CLI for SupaCloud users",
   "type": "module",
   "main": "./dist/index.js",
@@ -45,7 +45,7 @@
     "@graphql-tools/utils": "^12.0.3"
   },
   "devDependencies": {
-    "@supacloud/elysia": "^0.23.1",
+    "@supacloud/elysia": "^0.24.1",
     "@types/bun": "^1.4.2",
     "elysia": "2.0.0-beta.21",
     "typescript": "^7.0.2"