@everystack/cli 0.4.71 → 0.4.72

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to `@everystack/cli` are documented here.
 
 Format based on [Keep a Changelog](https://keepachangelog.com/).
 
+## [0.4.72] - 2026-09-04
+
+### Fixed
+
+- db:reconcile defers function-body validation (check_function_bodies=off)
+
 ## [0.4.71] - 2026-09-04
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everystack/cli",
-  "version": "0.4.71",
+  "version": "0.4.72",
   "description": "CLI and OTA updates for Expo apps on everystack",
   "license": "AGPL-3.0-only",
   "author": "Scalable Technology, Inc. <licensing@scalable.technology>",
@@ -178,7 +178,7 @@
     "jest": "29.7.0",
     "react": "19.2.0",
     "ts-jest": "29.4.9",
-    "@everystack/server": "0.4.29"
+    "@everystack/server": "0.4.30"
   },
   "scripts": {
     "test": "jest",

package/src/cli/commands/db-reconcile.ts

@@ -188,6 +188,16 @@ export async function executeReconcile(
   // as it was. See derivedSearchPath.
   const setSearchPath = renderSetSearchPath(derivedSearchPath(parsed.objects), atomic);
 
+  // Defer SQL/PLpgSQL function-body validation for the apply window — the pg_dump/pg_restore idiom
+  // db:build already uses (db-build.ts). A SQL-language function's body is validated at CREATE, so a
+  // function that reads a derived object being dropped-and-recreated in the SAME batch aborts with
+  // "relation does not exist" when it is (re)created before that object. The bodies are already
+  // validated upstream (db:build against a fresh DB, db:check in CI); the reconcile only needs the
+  // objects to EXIST by commit, which they do. Without this, reconcile fails where db:build succeeds
+  // on the very same schema — the only difference between them was this SET. LOCAL in the atomic
+  // batch (reverts at COMMIT); session-scoped on the unwrapped path (its connection is ephemeral).
+  const setCheckBodies = atomic ? 'SET LOCAL check_function_bodies = off' : 'SET check_function_bodies = off';
+
   // A schema populated only by derived objects has no model in it, so the state layer never
   // CREATE SCHEMAs it — the derived apply ensures its own object schemas (+ their USAGE
   // grants) before anything is created in them. Empty for all-public apps. See
@@ -221,9 +231,10 @@ export async function executeReconcile(
 
     if (rendered.statements.length > 0) {
       if (atomic) {
-        // The SET rides the same simple-query batch (and the same transaction) as the DDL,
-        // so bare body refs resolve to their real schema; SET LOCAL resets it at COMMIT.
-        await runner([...ensureSchemas, setSearchPath, ...rendered.statements].filter(Boolean).join(';\n'));
+        // The SETs ride the same simple-query batch (and the same transaction) as the DDL, so bare
+        // body refs resolve to their real schema and function bodies defer validation; SET LOCAL
+        // resets both at COMMIT.
+        await runner([...ensureSchemas, setSearchPath, setCheckBodies, ...rendered.statements].filter(Boolean).join(';\n'));
       } else {
         // Self-committing statements (CONCURRENTLY, VACUUM) refuse ANY transaction block —
         // including the implicit one a joined multi-statement simple query runs in, so the
@@ -233,7 +244,17 @@ export async function executeReconcile(
         // create resolves its bare refs.
         for (const statement of ensureSchemas) await runner(statement);
         if (setSearchPath) await runner(setSearchPath);
-        for (const statement of rendered.statements) await runner(statement);
+        // No transaction to scope the deferral to (this path exists for statements a transaction
+        // forbids), so the session GUC is set bare and RESET in a finally. A leak of THIS GUC is
+        // benign, unlike search_path: it only defers a body validation that already ran upstream
+        // (db:build against a fresh DB, db:check in CI) — it never changes what a query resolves to
+        // or what a fingerprint reads, so it cannot mint a wrong result the way a leaked path could.
+        await runner(setCheckBodies);
+        try {
+          for (const statement of rendered.statements) await runner(statement);
+        } finally {
+          await runner('RESET check_function_bodies');
+        }
       }
     }