chore(deps): move e2b to 2.62.1 and drizzle-kit to 0.31.11 (#9825)

Author: waleedlatif1

apps/sim/lib/execution/remote-sandbox/e2b.ts

@@ -1156,6 +1156,9 @@ export const e2bProvider: SandboxProvider = {
         : undefined
     const createOptions = {
       apiKey,
+      // The SDK retries a create that hit a gateway error; the key lets E2B return the sandbox
+      // the first attempt already started instead of starting a second one.
+      idempotencyKey: generateId(),
       ...(effectiveLifetimeMs !== undefined ? { timeoutMs: effectiveLifetimeMs } : {}),
       ...(options?.sessionKey
         ? {

apps/sim/package.json

@@ -105,7 +105,7 @@
     "@calcom/embed-react": "1.5.3",
     "@cerebras/cerebras_cloud_sdk": "^1.91.0",
     "@daytona/sdk": "0.207.0",
-    "@e2b/code-interpreter": "2.7.1",
+    "@e2b/code-interpreter": "2.9.1",
     "@earendil-works/pi-ai": "1.0.0",
     "@earendil-works/pi-coding-agent": "1.0.0",
     "@floating-ui/dom": "1.7.6",

bun.lock

@@ -145,7 +145,7 @@
     "marked": "18.0.11",
     "mermaid": "11.16.1",
     "zod": "4.3.6",
-    "e2b": "2.50.0",
+    "e2b": "2.62.1",
     "@ai-sdk/provider-utils": "3.0.28",
     "@azure/identity": "4.14.1",
     "@grpc/grpc-js": "1.14.6",
@@ -224,7 +224,7 @@
   ],
   "patchedDependencies": {
     "@better-auth/oauth-provider@1.6.27": "patches/@better-auth%2Foauth-provider@1.6.27.patch",
-    "drizzle-kit@0.31.10": "patches/drizzle-kit@0.31.10.patch",
+    "drizzle-kit@0.31.11": "patches/drizzle-kit@0.31.11.patch",
     "postgres@3.4.9": "patches/postgres@3.4.9.patch",
     "oracledb@7.0.1": "patches/oracledb@7.0.1.patch",
     "echarts@6.1.0": "patches/echarts@6.1.0.patch",

package.json

@@ -73,7 +73,7 @@
     "@sim/tsconfig": "workspace:*",
     "@types/bun": "1.4.4",
     "@types/node": "24.19.2",
-    "drizzle-kit": "0.31.10",
+    "drizzle-kit": "0.31.11",
     "typescript": "^7.0.2",
     "vitest": "^5.0.4"
   }

packages/db/package.json

@@ -48,7 +48,7 @@ closure handling. Keep the reconnect regression tests when upgrading.
 
 # Drizzle development push policy
 
-`drizzle-kit@0.31.10` prompts when it sees both additions and removals, even with
+`drizzle-kit@0.31.11` prompts when it sees both additions and removals, even with
 `--force`. Its PostgreSQL push path also catches errors and exits successfully,
 which lets post-push work run against a schema that was not applied.
 
@@ -57,8 +57,11 @@ resolvers and makes PostgreSQL push failures and cancellations return nonzero.
 `packages/db/scripts/push.ts` enables the policy only in its Drizzle subprocess
 using `SIM_DB_PUSH_RENAME_MODE=create`. `--interactive-renames` selects the native
 chooser and requires a terminal. Normal migration generation keeps its rename
-prompts. Data-loss confirmations, table filters, introspection, and generated SQL
-remain owned by Drizzle; `--force` still controls data-loss approval.
+prompts. Data-loss confirmations, table filters, and generated SQL remain owned
+by Drizzle; `--force` still controls data-loss approval. Introspection changes in
+one place: PostgreSQL unique constraints read their columns from
+`key_column_usage` in ordinal order, so a composite unique constraint is compared
+by its own columns in declared order.
 
 The same policy answers Drizzle's prompt to truncate a populated table before
 adding a unique constraint with its non-destructive choice: the constraint is

patches/README.md

@@ -63,7 +63,7 @@ diff --git a/bin.cjs b/bin.cjs
 -        console.error(e4);
 +        throw e4;
        }
-@@ -92281,2 +92282,3 @@
+@@ -92291,2 +92292,3 @@
        console.error(e4);
 +      process.exit(1);
      }