@jelou/cli 1.92.0 → 1.92.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.92.0",
+  "version": "1.92.1",
   "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.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"
+    "@jelou/cli-darwin-arm64": "1.92.1",
+    "@jelou/cli-darwin-x64": "1.92.1",
+    "@jelou/cli-linux-x64": "1.92.1",
+    "@jelou/cli-linux-arm64": "1.92.1",
+    "@jelou/cli-win32-x64": "1.92.1"
   },
   "keywords": [
     "jelou",
@@ -58,41 +58,25 @@
   "jelou": {
     "minVersion": "1.89.0",
     "release_notes": {
-      "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.",
+      "version": "1.92.1",
+      "date": "2026-08-12",
+      "headline": "`jelou channels flows` works — it never could authorize the provider listing before, and it now returns the Meta flow id a Flow step actually needs.",
       "highlights": [
         {
           "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."
+          "text": "`jelou channels flows <botId>` now lists a bot's WhatsApp Flows. It previously always failed with \"the Flows listing could not be authorized\", because it asked the wrong host with the wrong credential. It now reads the provider listing the same way `jelou channels list` reads channels."
         },
         {
           "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."
+          "text": "The listing returns each Flow's provider id — the value a WhatsApp Flow step has to open — instead of an internal row id. A Flow step authored from the old output pointed at an id the provider does not know, and broke when the step ran."
         },
         {
           "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."
+          "text": "A bot with no Flows now reports exactly that, instead of failing as though the provider had answered with something unreadable."
         },
         {
           "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": "\"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": "`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."
+          "text": "A bot is found even when the company has more channels than fit in one page. Companies past 50 WhatsApp channels were told the bot had no channel connected when it did."
         }
       ]
     }