@fusebase/fusebase-gate-sdk 2.2.2-sdk.23 → 2.2.2-sdk.25

package/dist/apis/IsolatedStoresApi.d.ts

@@ -11,7 +11,7 @@ export declare class IsolatedStoresApi {
     constructor(client: Client);
     /**
      * Apply SQL migrations
-     * Applies pending postgres migrations from an ordered migration bundle into the selected stage database. For prod, gate creates a checkpoint automatically before applying pending migrations. Applied history must match the bundle prefix exactly; drifted stages are rejected. MCP clients often cap tool_call JSON body size (on the order of a few thousand characters); the request includes full SQL text for every bundle version cumulatively, so large bundles may fail or truncate in chat-only MCP. For schema work under tight limits prefer executeIsolatedStoreSql with one statement per call and keep canonical SQL plus a manifest for apply from SDK or non-MCP callers.
+     * Applies pending postgres migrations from an ordered migration bundle into the selected stage database. For prod, gate creates a checkpoint automatically before applying pending migrations. Applied history must match the bundle prefix exactly; drifted stages are rejected. MCP clients often cap tool_call JSON body size (on the order of a few thousand characters); the request includes full SQL text for every bundle version cumulatively, so large bundles may fail or truncate in chat-only MCP. Keep canonical SQL plus a manifest for apply from SDK, CLI, or any non-MCP caller without a tight body-size limit.
      */
     applyIsolatedStoreSqlMigrations(params: {
         path: {
@@ -155,7 +155,7 @@ export declare class IsolatedStoresApi {
     }): Promise<IsolatedStoreSqlDescribeTableResponseContract>;
     /**
      * Run writable SQL statement
-     * Runs a single SQL statement with execute access against the postgres binding of the selected isolated store stage instance. Unlike applyIsolatedStoreSqlMigrations, this does not record entries in the stage migration journal (fusebase_schema_migrations); after DDL applied only via execute, that table may be absent until a proper migration apply runs.
+     * Runs a single raw DML statement with execute access against the postgres binding of the selected isolated store stage instance. Only INSERT, UPDATE, and DELETE are allowed on this privileged escape hatch. DDL and schema changes are blocked here and must go through applyIsolatedStoreSqlMigrations so the stage migration journal (fusebase_schema_migrations) stays authoritative.
      */
     executeIsolatedStoreSql(params: {
         path: {

package/dist/apis/IsolatedStoresApi.js

@@ -13,7 +13,7 @@ class IsolatedStoresApi {
     }
     /**
      * Apply SQL migrations
-     * Applies pending postgres migrations from an ordered migration bundle into the selected stage database. For prod, gate creates a checkpoint automatically before applying pending migrations. Applied history must match the bundle prefix exactly; drifted stages are rejected. MCP clients often cap tool_call JSON body size (on the order of a few thousand characters); the request includes full SQL text for every bundle version cumulatively, so large bundles may fail or truncate in chat-only MCP. For schema work under tight limits prefer executeIsolatedStoreSql with one statement per call and keep canonical SQL plus a manifest for apply from SDK or non-MCP callers.
+     * Applies pending postgres migrations from an ordered migration bundle into the selected stage database. For prod, gate creates a checkpoint automatically before applying pending migrations. Applied history must match the bundle prefix exactly; drifted stages are rejected. MCP clients often cap tool_call JSON body size (on the order of a few thousand characters); the request includes full SQL text for every bundle version cumulatively, so large bundles may fail or truncate in chat-only MCP. Keep canonical SQL plus a manifest for apply from SDK, CLI, or any non-MCP caller without a tight body-size limit.
      */
     async applyIsolatedStoreSqlMigrations(params) {
         return this.client.request({
@@ -176,7 +176,7 @@ class IsolatedStoresApi {
     }
     /**
      * Run writable SQL statement
-     * Runs a single SQL statement with execute access against the postgres binding of the selected isolated store stage instance. Unlike applyIsolatedStoreSqlMigrations, this does not record entries in the stage migration journal (fusebase_schema_migrations); after DDL applied only via execute, that table may be absent until a proper migration apply runs.
+     * Runs a single raw DML statement with execute access against the postgres binding of the selected isolated store stage instance. Only INSERT, UPDATE, and DELETE are allowed on this privileged escape hatch. DDL and schema changes are blocked here and must go through applyIsolatedStoreSqlMigrations so the stage migration journal (fusebase_schema_migrations) stays authoritative.
      */
     async executeIsolatedStoreSql(params) {
         return this.client.request({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusebase/fusebase-gate-sdk",
-  "version": "2.2.2-sdk.23",
+  "version": "2.2.2-sdk.25",
   "description": "TypeScript SDK for Fusebase Gate APIs - Generated from contract introspection",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

package/release-notes/2.2.2-sdk.25.md

@@ -0,0 +1,9 @@
+# Release Notes 2.2.2-sdk.25
+
+- Current ref: `HEAD`
+- Previous tag: `v2.2.2-sdk.25`
+- Generated at: 2026-04-04T22:07:14.296Z
+
+## Included Drafts
+
+- None

package/release-notes/latest.md

@@ -1,8 +1,8 @@
-# Release Notes 2.2.2-sdk.23
+# Release Notes 2.2.2-sdk.25
 
 - Current ref: `HEAD`
-- Previous tag: `v2.2.2-sdk.23`
-- Generated at: 2026-04-04T20:19:21.907Z
+- Previous tag: `v2.2.2-sdk.25`
+- Generated at: 2026-04-04T22:07:14.296Z
 
 ## Included Drafts
 

package/release-notes/2.2.2-sdk.23.md

@@ -1,9 +0,0 @@
-# Release Notes 2.2.2-sdk.23
-
-- Current ref: `HEAD`
-- Previous tag: `v2.2.2-sdk.23`
-- Generated at: 2026-04-04T20:19:21.907Z
-
-## Included Drafts
-
-- None