create-ultimate 23.0.0 → 25.0.0

package/README.md

@@ -1,12 +1,12 @@
 # create-ultimate
 
 ```sh
-bunx create-ultimate myapp && cd myapp && bin/setup && bin/dev
+bunx create-ultimate myapp && cd myapp && bun run setup && bun run dev
 ```
 
-`bin/setup` is the scaffold's own script and it is not optional: `x new` writes files and installs
-nothing, so `x dev` on the tree it just wrote fails with `X_BUILD_FAILED`. The script installs the
-dependencies, writes `.env.development.local`, generates and applies the first migration, seeds,
+`bun run setup` is the scaffold's own script (`bin/setup.ts`, run by Bun — the same command in
+PowerShell, cmd and bash) and it is not optional: `x new` writes files and installs nothing, so
+`x dev` on the tree it just wrote fails with `X_BUILD_FAILED`. The script installs the dependencies, writes `.env.development.local`, generates and applies the first migration, seeds,
 and writes `x.manifest.json` — six commands, idempotent, so it is safe to re-run after every pull.
 
 Thin wrapper over `x new` — same templates, same flags, no second code path.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ultimate",
-  "version": "23.0.0",
+  "version": "25.0.0",
   "description": "bunx create-ultimate myapp — scaffold an Ultimate monorepo",
   "license": "MIT",
   "type": "module",
@@ -28,13 +28,13 @@
     "LICENSE"
   ],
   "engines": {
-    "bun": ">=1.4.0"
+    "bun": ">=1.4.2"
   },
   "scripts": {
     "typecheck": "tsc --noEmit -p tsconfig.json",
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/cli": "23.0.0"
+    "@ultimat3/cli": "25.0.0"
   }
 }