@zerotal/orm 1.5.1 → 1.6.0

package/CHANGELOG.md

@@ -8,6 +8,24 @@ follows the Zerotal monorepo's unified versioning.
 
 ## [Unreleased]
 
+## [1.6.0] — 2026-08-15
+
+### Fixed
+
+- **Auto-`synchronize` was never hard-off in production.** The guard compared
+  `APP_ENV` against `"production"`, but `setAppEnv()` replaces that with the runtime
+  mode before the app boots — so it read `"web"` and never fired. The only thing standing
+  between a production database and boot-time schema sync was the config default in
+  `config/database.ts`. It reads `deployEnv()` now, and covers `staging` too.
+
+- **`forceState()` did not refuse to run in production.** Its throw exists so a
+  state-machine escape hatch cannot be used on live data; the same `APP_ENV` comparison
+  meant it never triggered.
+
+- **The N+1 detector's own environment gate never matched**, so the detector returned early
+  even in development. (The provider-level gate that installs it was fixed in 1.5.0; this is
+  the second gate inside the detector itself.)
+
 ## [1.5.0] — 2026-08-15
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zerotal/orm",
-  "version": "1.5.1",
+  "version": "1.6.0",
   "license": "MIT",
   "maturity": "stable",
   "private": false,
@@ -30,8 +30,8 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@zerotal/core": "1.5.1",
-    "@zerotal/validator": "1.5.1"
+    "@zerotal/core": "1.6.0",
+    "@zerotal/validator": "1.6.0"
   },
   "devDependencies": {
     "typescript": "^5.8.0"

package/src/db/NPlusOneDetector.ts

@@ -1,4 +1,5 @@
 import { ZerotalError, FrameworkEvents } from "@zerotal/core";
+import { isProdLike, deployEnv } from "@zerotal/core";
 import { NPlusOneDetected } from "../events.ts";
 
 // ── N+1 Query Detector ────────────────────────────────────────────────────────
@@ -180,13 +181,12 @@ export function trackQuery(
 
   // Honour explicit opt-in or auto-enable in local/development only
   if (!_forced) {
-    const env = (typeof Bun !== "undefined" ? Bun.env["APP_ENV"] : undefined) ?? "";
+    const env = deployEnv();
     if (env !== "local" && env !== "development" && env !== "dev") return;
   }
 
   // Production always off
-  const env = (typeof Bun !== "undefined" ? Bun.env["APP_ENV"] : undefined) ?? "";
-  if (env === "production" || env === "prod") return;
+  if (isProdLike(deployEnv())) return;
 
   // Only watch SELECTs — the N+1 problem is purely about reads
   if (!fingerprint.trimStart().toLowerCase().startsWith("select")) return;

package/src/model/State.ts

@@ -19,6 +19,7 @@
 //     @column() status!: keyof typeof States;
 //   }
 
+import { isProdLike, deployEnv } from "@zerotal/core";
 import { StateError } from "../errors/index.ts";
 import { currentOrmContext } from "./OrmContext.ts";
 import type { Constructor } from "./mixins.ts";
@@ -278,7 +279,7 @@ export function State<TBase extends Constructor>(Base: TBase) {
      * @throws {Error} when called with `APP_ENV=production`.
      */
     async forceState(state: string): Promise<this> {
-      if (Bun.env["APP_ENV"] === "production") {
+      if (isProdLike(deployEnv())) {
         throw new Error("forceState() cannot be called in production (APP_ENV=production).");
       }
       const field = (this.constructor as unknown as StateModelClass).stateField;

package/src/schema/autoMigrate.ts

@@ -1,4 +1,5 @@
 import type { ConcernDescriptor } from "@zerotal/core";
+import { isProdLike, deployEnv } from "@zerotal/core";
 import type { ConfigManager } from "@zerotal/core/config";
 import { ModelInspector, columnDbName } from "./ModelInspector.ts";
 import { SchemaDiffer, type DiffResult } from "./SchemaDiffer.ts";
@@ -147,9 +148,12 @@ export const autoMigrateConcern: ConcernDescriptor = {
   name: "auto-migrate",
   order: 100,
   async run(ctx) {
-    // Hard-off in production. `ctx.env` is the runtime mode (web/console/…), so the
-    // deployment name is read from APP_ENV directly.
-    if (Bun.env.APP_ENV === "production") return;
+    // Hard-off on any deployed environment. Both `ctx.env` AND `APP_ENV` hold the
+    // runtime mode by now — the comment that used to sit here claimed APP_ENV still
+    // carried the deployment name, which is exactly the mistake. This guard never
+    // fired under `zt serve`, so the only thing between a production database and
+    // boot-time schema sync was the config default.
+    if (isProdLike(deployEnv())) return;
     const config = ctx.resolve<ConfigManager>("config");
     const { enabled, disruptive } = resolveSyncOptions(config?.get("database.synchronize"));
     if (!enabled) return;