@jelou/cli 1.79.0 → 1.80.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.79.0",
+  "version": "1.80.0",
   "description": "Build AI agents on the Jelou platform — from your terminal or your AI editor.",
   "author": "Jelou Inc. (https://jelou.ai)",
   "license": "SEE LICENSE IN LICENSE",
@@ -23,11 +23,11 @@
     "THIRD_PARTY_NOTICES.md"
   ],
   "optionalDependencies": {
-    "@jelou/cli-darwin-arm64": "1.79.0",
-    "@jelou/cli-darwin-x64": "1.79.0",
-    "@jelou/cli-linux-x64": "1.79.0",
-    "@jelou/cli-linux-arm64": "1.79.0",
-    "@jelou/cli-win32-x64": "1.79.0"
+    "@jelou/cli-darwin-arm64": "1.80.0",
+    "@jelou/cli-darwin-x64": "1.80.0",
+    "@jelou/cli-linux-x64": "1.80.0",
+    "@jelou/cli-linux-arm64": "1.80.0",
+    "@jelou/cli-win32-x64": "1.80.0"
   },
   "keywords": [
     "jelou",
@@ -56,27 +56,35 @@
     "access": "public"
   },
   "jelou": {
-    "minVersion": "1.78.0",
+    "minVersion": "1.80.0",
     "release_notes": {
-      "version": "1.78.0",
-      "date": "2026-07-29",
-      "headline": "The agent skill catalog slimmed from 18 to 12 — same capabilities, less context per session, cleaned up automatically.",
+      "version": "1.80.0",
+      "date": "2026-08-01",
+      "headline": "`jelou functions deploy` now refuses to deploy a project into the wrong company, and checks your code against the Deno v2 runtime before uploading anything.",
       "highlights": [
         {
-          "type": "improved",
-          "text": "Secrets guidance now lives in the core `jelou` skill, marketplace guidance in `jelou-project`, and everything workflow-building — creation, validation, CONNECT human-handoff, and the full build engine — in a single `jelou-build-workflows` skill."
+          "type": "heads_up",
+          "text": "A deploy is now **refused** when the project belongs to a different company than your active profile. `jelou.json` records the owning organization, and a mismatch exits 2 without uploading. Previously the CLI would either create a duplicate function in the wrong company or silently overwrite a different function that happened to share the slug — in both cases reporting success. If you hit the refusal, the error names both organizations; run `jelou auth list` then `jelou auth switch <name>`. To deliberately re-point a project, use `jelou functions init --mode link --force`."
         },
         {
-          "type": "improved",
-          "text": "The three largest skills load much less text up front: deep-dive material moved to on-demand reference files, so agents spend fewer tokens per session with the same depth available."
+          "type": "heads_up",
+          "text": "Projects created before this release are stamped on their next successful deploy, so the first deploy after upgrading always goes through."
         },
         {
-          "type": "heads_up",
-          "text": "Six standalone skills were retired: `jelou-secret`, `jelou-marketplace`, `jelou-workflow`, `jelou-connect`, `jelou-build-workflow`, and `jelou-test-whatsapp`. Their content moved into the merged skills above — except `jelou-test-whatsapp`, which was removed (the experimental `jelou test whatsapp` commands still work). Stale copies are deleted from your editors automatically on the next `jelou login` or `jelou agent install`. No CLI commands changed."
+          "type": "new",
+          "text": "`jelou functions check` validates a project against the Deno Deploy v2 runtime without touching the network — run it before a deploy or in CI."
         },
         {
-          "type": "heads_up",
-          "text": "Installed CLIs below 1.78.0 now see the soft \"Update available\" prompt on their next invocation (`below_floor: true` on agent-mode envelopes). Nothing is blocked."
+          "type": "new",
+          "text": "`deploy` runs the same checks and stops on anything that would fail at boot, most importantly `Deno.openKv()` at module scope, which v2 rejects because the KV binding is not attached yet. `--dry-run` reports without blocking."
+        },
+        {
+          "type": "fixed",
+          "text": "`jelou functions dev` overwrote an existing `deno.json` instead of merging into it, discarding tasks, lint and compiler options. It now preserves every key, and leaves the file untouched when it cannot parse it."
+        },
+        {
+          "type": "fixed",
+          "text": "`jelou push` reported `LOCKFILE_DRIFT` on a workflow you had just pulled and barely touched, and `--force` then failed with `POST_PUSH_DIVERGENCE` — the lockfile never refreshed, so every retry repeated it. Workflows that are a project's default entry flow, or that are hidden or carry routing rules, were affected. `push`, `status` and `workflow incoming` now all compare the same shape `pull` writes."
         }
       ]
     }