@jelou/cli 1.90.0 → 1.92.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.90.0",
+  "version": "1.92.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.90.0",
-    "@jelou/cli-darwin-x64": "1.90.0",
-    "@jelou/cli-linux-x64": "1.90.0",
-    "@jelou/cli-linux-arm64": "1.90.0",
-    "@jelou/cli-win32-x64": "1.90.0"
+    "@jelou/cli-darwin-arm64": "1.92.0",
+    "@jelou/cli-darwin-x64": "1.92.0",
+    "@jelou/cli-linux-x64": "1.92.0",
+    "@jelou/cli-linux-arm64": "1.92.0",
+    "@jelou/cli-win32-x64": "1.92.0"
   },
   "keywords": [
     "jelou",
@@ -58,25 +58,41 @@
   "jelou": {
     "minVersion": "1.89.0",
     "release_notes": {
-      "version": "1.90.0",
-      "date": "2026-08-10",
-      "headline": "Facebook and Instagram: page ids, the comments inbox, and why a connected page stays silent.",
+      "version": "1.92.0",
+      "date": "2026-08-11",
+      "headline": "Three fixes for agents that got stuck mid-task — a lockfile the CLI wrote and then refused to read, an update notice that abandoned your work, and a data-table node that validated clean and saved nothing — plus agents now ask what you mean by \"WhatsApp Flows\" instead of guessing.",
       "highlights": [
         {
-          "type": "new",
-          "text": "`jelou channels list --type Facebook_Feed` (and `Instagram_Feed`) reaches the page comments inbox, which was previously invisible to the CLI. The filter is exact: `--type Facebook` stays Messenger DMs only."
+          "type": "fixed",
+          "text": "`jelou pull` could write a `jelou.lock` the CLI itself refused to read. A workflow described as `-`, or a value that looks like a number or a date, was written unquoted, so the next command failed on the lockfile instead of doing what you asked. Repairing it by hand then failed an integrity check. Values are now quoted whenever they'd otherwise change meaning, and the \"invalid lockfile\" error tells you to re-pull rather than leaving you to edit it."
         },
         {
-          "type": "new",
-          "text": "`jelou channels show` prints the Meta page id and a link to the page for Facebook and Instagram channels, mirroring the WhatsApp phone block. It is also on the JSON envelope as `pageId`."
+          "type": "fixed",
+          "text": "An out-of-date CLI no longer abandons your request. Declining the upgrade — or running somewhere nobody can answer the prompt — used to stop the task and tell you an administrator had to upgrade first, even though the CLI runs fine either way. It now finishes what you asked and notes that write commands may be affected until you upgrade."
+        },
+        {
+          "type": "fixed",
+          "text": "Data-table steps that were configured wrong now fail validation instead of silently saving nothing. A step carrying its payload under the wrong field, or a create/update/delete with no values or nothing identifying the row, passed validation and then did nothing at runtime — which reached real conversations."
+        },
+        {
+          "type": "fixed",
+          "text": "The WhatsApp channel check behind `jelou template` and `jelou campaign` stops answering \"unknown\" every time. It asked the Channels API for 100 channels, which that endpoint rejects over 50, so the request never returned and the check fell into its catch. It now clamps the page size and reports what it found."
         },
         {
           "type": "improved",
-          "text": "Your agent now knows that connecting a Facebook page is only half the job: each skill needs its own Facebook channel entry, added in Studio, or the engine finds no workflow for that traffic and nothing replies. The skills also stop suggesting `jelou channels create --type whatsapp`, which the CLI has never accepted. Run `jelou agent install` after upgrading; skill content does not refresh on its own."
+          "text": "\"WhatsApp Flows\" means two different things — the Flow assets on your provider, or a step in a workflow that opens one. Agents now ask which you want before building anything, instead of picking one and either leaving a half-configured node on the canvas or listing when you wanted a node."
         },
         {
           "type": "improved",
-          "text": "The workflow-building skill no longer claims to be WhatsApp-only. It now says what is actually true — one workflow per channel, and the button and list caps it quotes are WhatsApp's, not every channel's."
+          "text": "`jelou channels list` takes a search term, passed through to the Channels API — find a channel by name instead of paging toward it."
+        },
+        {
+          "type": "heads_up",
+          "text": "Validation now rejects data-table steps whose configuration could never run. If you pull an existing project that already contains one, `jelou workflow validate` will report it. Those steps are already failing in production; the validator simply stopped hiding them."
+        },
+        {
+          "type": "heads_up",
+          "text": "`jelou channels list --limit` above 50 is clamped instead of failing. The default is 50, so this only surfaces when a larger page was requested explicitly, and the response reports the page size actually used."
         }
       ]
     }