@zerotal/core 1.14.1 → 1.14.3

package/CHANGELOG.md

@@ -8,6 +8,30 @@ follows the Zerotal monorepo's unified versioning.
 
 ## [Unreleased]
 
+## [1.14.3] — 2026-09-01
+
+### Fixed
+
+- **`zt upgrade` never offered the 1.13.0 migrations.** `deprecated-aliases` bundled two
+  retirements that shipped in 1.13.0 — `serve --dev` and `routes:types` — with the
+  `BaseModel` rename that has not shipped and is scheduled for 2.0. A codemod carries one
+  version, so it took the later one, and `zt upgrade --to 1.13.0` selected nothing at all.
+  The migration for the release that broke `serve --dev` was unreachable by every app
+  crossing it.
+
+  Split into `deprecated-aliases` at 1.13.0 and `base-model-rename` at 2.0.0. An app moving
+  to any 1.13+ release now gets the command rewrites, and one crossing to 2.0 no longer has
+  `BaseModel` renamed as a side effect of a command alias.
+
+## [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.3",
   "license": "MIT",
   "maturity": "stable",
   "private": false,

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

@@ -1,24 +1,19 @@
 /**
  * Ledger #4 — retire the deprecated aliases.
  *
- * Three pairs, each a live alias somebody depends on, which is exactly why they
- * could not be dropped in a minor:
+ * Two codemods, not one, because they retire at different times and a codemod
+ * carries a single version:
  *
- * - `BaseModel` → `Model`. The same class object under its original name.
- * - `routes:types` → `route:types`. Registered as an alias in `CommandRunner`.
- * - `serve --dev` → `dev`. The flag still works; `dev` is the command it became.
+ * - {@link deprecatedAliases} at **1.13.0** — `routes:types` → `route:types` and
+ *   `serve --dev` → `dev`. Both shipped; both fail loudly now.
+ * - {@link baseModelRename} at **2.0.0** — `BaseModel` → `Model`. Not shipped;
+ *   sized on 1 Sep 2026 at 617 api-surface references and moved to 2.0.
  *
- * ## What this deliberately does not do
- *
- * **It does not touch `BaseModel` in a type position.** `Model` and `BaseModel`
- * are the same runtime class, so a value-position rename is cosmetic and safe.
- * In a generic bound — `<T extends BaseModel>` — the name may be load-bearing
- * for a reader even though it resolves identically, and in framework source it
- * genuinely is. Those are reported for a person instead.
- *
- * That asymmetry is the whole reason this is a codemod rather than a
- * find-and-replace: the mixin-composition script learned it the hard way in
- * 1.3.0, where a blind rename broke import specifiers it had not considered.
+ * They were one codemod, which forced one version, which took the later of the
+ * two — so `zt upgrade --to 1.13.0` selected nothing and offered no help
+ * migrating the very release that retired `serve --dev`, while an app crossing to
+ * 2.0 would have had its `BaseModel` renamed as a side effect of a command alias.
+ * A codemod nobody's upgrade reaches is a codemod that does not exist.
  */
 import type { Change, Codemod, CodemodResult, Manual, SourceFile } from "../types.ts";
 
@@ -41,16 +36,64 @@ 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`",
   },
 ];
 
+/** The command aliases retired in 1.13.0. Both fail loudly rather than drifting. */
 export const deprecatedAliases: Codemod = {
-  version: "2.0.0",
+  version: "1.13.0",
   name: "deprecated-aliases",
-  description: "Retire BaseModel, routes:types and serve --dev in favour of their real names",
+  description: "Retire routes:types and serve --dev in favour of their real names",
+  ledger: 4,
+
+  run(files: SourceFile[]): CodemodResult {
+    const changes: Change[] = [];
+
+    for (const { file, contents } of files) {
+      let next = contents;
+      const notes: string[] = [];
+
+      for (const { find, replace, label } of COMMAND_ALIASES) {
+        const hits = next.match(find)?.length ?? 0;
+        if (hits === 0) continue;
+        next = next.replace(find, replace);
+        notes.push(`${hits} × ${label}`);
+      }
+
+      if (next !== contents) changes.push({ file, summary: notes.join(", "), contents: next });
+    }
+
+    return { changes, manual: [] };
+  },
+};
+
+/**
+ * `BaseModel` → `Model`, which has **not shipped** and is scheduled for 2.0.
+ *
+ * ## What this deliberately does not do
+ *
+ * **It does not touch `BaseModel` in a type position.** `Model` and `BaseModel`
+ * are the same runtime class, so a value-position rename is cosmetic and safe.
+ * In a generic bound — `<T extends BaseModel>` — the name may be load-bearing
+ * for a reader even though it resolves identically, and in framework source it
+ * genuinely is. Those are reported for a person instead.
+ *
+ * That asymmetry is the whole reason this is a codemod rather than a
+ * find-and-replace: the mixin-composition script learned it the hard way in
+ * 1.3.0, where a blind rename broke import specifiers it had not considered.
+ */
+export const baseModelRename: Codemod = {
+  version: "2.0.0",
+  name: "base-model-rename",
+  description: "Rename BaseModel to Model at every declaration site",
   ledger: 4,
 
   run(files: SourceFile[]): CodemodResult {
@@ -83,13 +126,6 @@ export const deprecatedAliases: Codemod = {
         notes.push("import specifier updated");
       }
 
-      for (const { find, replace, label } of COMMAND_ALIASES) {
-        const hits = next.match(find)?.length ?? 0;
-        if (hits === 0) continue;
-        next = next.replace(find, replace);
-        notes.push(`${hits} × ${label}`);
-      }
-
       // Type positions are a handover, not a rewrite.
       contents.split("\n").forEach((line, i) => {
         if (!BASE_MODEL_TYPE.test(line)) return;

package/src/upgrade/codemods/index.ts

@@ -8,9 +8,9 @@
  * that rule fails is by everyone assuming there is time.
  */
 import type { Codemod } from "../types.ts";
-import { deprecatedAliases } from "./deprecated-aliases.ts";
+import { deprecatedAliases, baseModelRename } from "./deprecated-aliases.ts";
 import { clientTaggedTemplate } from "./client-tagged-template.ts";
 
-export const CODEMODS: Codemod[] = [clientTaggedTemplate, deprecatedAliases];
+export const CODEMODS: Codemod[] = [clientTaggedTemplate, deprecatedAliases, baseModelRename];
 
-export { deprecatedAliases, clientTaggedTemplate };
+export { deprecatedAliases, baseModelRename, clientTaggedTemplate };