@take-out/scripts 0.4.22 → 0.4.24

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@take-out/scripts",
-  "version": "0.4.22",
+  "version": "0.4.24",
   "type": "module",
   "main": "./src/cmd.ts",
   "sideEffects": false,
@@ -29,8 +29,8 @@
   },
   "dependencies": {
     "@clack/prompts": "^0.8.2",
-    "@take-out/helpers": "0.4.22",
-    "@take-out/run": "0.4.22",
+    "@take-out/helpers": "0.4.24",
+    "@take-out/run": "0.4.24",
     "picocolors": "^1.1.1"
   }
 }

package/src/helpers/uncloud.ts

@@ -126,13 +126,21 @@ export async function pushImage(
 
 export async function deployStack(
   composeFile: string,
-  options?: { profile?: string } & UncloudConfig,
+  options?: { profile?: string; service?: string; recreate?: boolean } & UncloudConfig,
 ): Promise<void> {
-  console.info('\n📦 deploying stack...\n')
+  const service = options?.service
+  console.info(`\n📦 deploying ${service ?? 'stack'}...\n`)
 
   const profileFlag = options?.profile ? `--profile ${options.profile}` : ''
-  // --recreate ensures containers are recreated even if config unchanged (pulls fresh images)
-  await run(`${ucCmd(options)} deploy -f ${composeFile} ${profileFlag} --recreate --yes`)
+  // --recreate forces fresh containers even when config is unchanged (picks up the new
+  // :latest image). pass recreate:false to let uncloud restart a service ONLY when its
+  // image/config actually changed — used for zero, whose restarts drop every websocket
+  // connection and cause a client reconnect storm.
+  const recreateFlag = options?.recreate === false ? '' : '--recreate'
+  const serviceArg = service ? ` ${service}` : ''
+  await run(
+    `${ucCmd(options)} deploy -f ${composeFile} ${profileFlag} ${recreateFlag} --yes${serviceArg}`,
+  )
 
   console.info('\n✅ deployment complete!')
 }

package/src/node-version-check.ts

@@ -1,10 +1,24 @@
 #!/usr/bin/env bun
 
+import { execFileSync } from 'node:child_process'
 import fs from 'node:fs'
 
 import { cmd } from './cmd'
 
 function getCurrentNodeVersion() {
+  // under bun, process.version is bun's bundled node-COMPAT string (a fixed
+  // value like v24.3.0), not the project's actual node toolchain — comparing
+  // it against engines.node rejects any pin newer than bun's compat level.
+  // the check exists to guard native-addon ABI for the real `node` binary
+  // child processes will run, so resolve that binary's version from PATH.
+  if (process.versions.bun) {
+    try {
+      return execFileSync('node', ['--version'], { encoding: 'utf-8' }).trim()
+    } catch {
+      // no node on PATH — nothing for the version pin to guard
+      return null
+    }
+  }
   return process.version
 }
 
@@ -35,7 +49,7 @@ export async function checkNodeVersion() {
   const currentNodeVersion = getCurrentNodeVersion()
   const requiredNodeVersion = await getRequiredNodeVersion()
 
-  if (requiredNodeVersion) {
+  if (requiredNodeVersion && currentNodeVersion) {
     if (currentNodeVersion !== requiredNodeVersion) {
       throw new Error(
         `\u001b[33mWarning: Incorrect Node.js version. Expected ${requiredNodeVersion} but got ${currentNodeVersion}\u001b[0m`,