@supabase/lite 0.9.1-next.1 → 0.9.1-next.2

package/dist/cli/lib.d.ts

@@ -174,24 +174,13 @@ interface ApplyResult {
     applied: MigrationFile[];
     skipped: MigrationFile[];
 }
-interface ApplyOptions {
-    /**
-     * Persist the migration-derived deparse snapshot even when the project has
-     * declarative `supabase/schemas/*.sql`. Set ONLY by `lite db reset`, which is
-     * destructive: it drops whatever a declarative apply built, so migration
-     * metadata then describes the fresh database exactly. Non-destructive callers
-     * must not opt in — their snapshot would validate on the next `lite start`
-     * while missing every declarative policy (LITE-310).
-     */
-    persistWithDeclarative?: boolean;
-}
 /**
  * Apply pending migrations to the connected database, one implicit transaction
  * per file. The history INSERT is appended to the file's batch so a failure in
  * any statement rolls back the record too — same semantics as Supabase CLI
  * (`~/supabase/cli/pkg/migration/file.go:72-103` `ExecBatch`).
  */
-declare function applyPendingMigrations(app: App, options?: ApplyOptions): Promise<ApplyResult>;
+declare function applyPendingMigrations(app: App): Promise<ApplyResult>;
 
 /**
  * Resolve the project's configured `auth.publishable_key`, fully substituted