@zerotal/core 1.14.1 → 1.14.2

package/CHANGELOG.md

@@ -8,6 +8,15 @@ follows the Zerotal monorepo's unified versioning.
 
 ## [Unreleased]
 
+## [1.14.2] — 2026-09-01
+
+### Fixed
+
+- **`zt upgrade` now rewrites `zt.ts serve --dev`.** The `deprecated-aliases` codemod
+  anchored on `zt` followed by whitespace, so it matched `zt serve --dev` and missed
+  `bun zt.ts serve --dev` — the form in every scaffolded `package.json`, and the one an app
+  runs as `bun run dev`. The codemod reported nothing to do on the file that needed it most.
+
 ## [1.14.1] — 2026-09-01
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zerotal/core",
-  "version": "1.14.1",
+  "version": "1.14.2",
   "license": "MIT",
   "maturity": "stable",
   "private": false,

package/src/upgrade/codemods/deprecated-aliases.ts

@@ -41,8 +41,13 @@ const BASE_MODEL_IMPORT = /(\bimport\s*\{[^}]*?)\bBaseModel\b([^}]*?\}\s*from\s*
 const COMMAND_ALIASES: { find: RegExp; replace: string; label: string }[] = [
   { find: /\broutes:types\b/g, replace: "route:types", label: "`routes:types` → `route:types`" },
   {
-    find: /\b(zt|zerotal)\s+serve\s+--dev\b/g,
-    replace: "$1 dev",
+    // `zt.ts` as well as `zt`, because the scaffolded entry point *is* `zt.ts` and
+    // every generated `package.json` reads `bun zt.ts serve --dev`. Anchoring on
+    // `zt` followed by whitespace missed the most common occurrence there is — the
+    // one an app runs as `bun run dev` — so `zt upgrade` reported nothing to do on
+    // the file that needed it most.
+    find: /\b(zt|zerotal)(\.ts)?\s+serve\s+--dev\b/g,
+    replace: "$1$2 dev",
     label: "`serve --dev` → `dev`",
   },
 ];