@jelou/cli 1.155.2 → 1.155.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.155.2",
+  "version": "1.155.3",
   "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.155.2",
-    "@jelou/cli-darwin-x64": "1.155.2",
-    "@jelou/cli-linux-x64": "1.155.2",
-    "@jelou/cli-linux-arm64": "1.155.2",
-    "@jelou/cli-win32-x64": "1.155.2"
+    "@jelou/cli-darwin-arm64": "1.155.3",
+    "@jelou/cli-darwin-x64": "1.155.3",
+    "@jelou/cli-linux-x64": "1.155.3",
+    "@jelou/cli-linux-arm64": "1.155.3",
+    "@jelou/cli-win32-x64": "1.155.3"
   },
   "keywords": [
     "jelou",
@@ -58,37 +58,17 @@
   "jelou": {
     "minVersion": "1.155.1",
     "release_notes": {
-      "version": "1.155.2",
+      "version": "1.155.3",
       "date": "2026-09-24",
-      "headline": "`jelou logs` follows the project you are in, and `jelou logs failed` now shows failures the bot handled.",
+      "headline": "`jelou logs chat` reads the whole range you ask for, and `jelou logs failed` no longer times out on busy organizations.",
       "highlights": [
-        {
-          "type": "improved",
-          "text": "Inside a linked project directory, `jelou logs failed`, `jelou logs chat` and `jelou logs conversations list` read that project's channels only; at an organization root they read the whole organization. Every row names its bot and project."
-        },
-        {
-          "type": "improved",
-          "text": "`jelou logs chat --user-id` no longer needs `--bot-id`: it finds the bots that person reached and reads each one. `jelou logs conversations list` without `--bot-id` reads every bot in scope."
-        },
-        {
-          "type": "new",
-          "text": "`jelou logs failed` also lists failed nodes, including ones whose error path was handled so the conversation still ended `COMPLETED`. `--status FAILED` shows only those. A failure inside a tool is labeled with the bot that called the tool."
-        },
         {
           "type": "fixed",
-          "text": "`jelou pull --workflow` accepts a file name such as `name.whatsapp.json`, and fails with an input error when nothing matches instead of reporting success with nothing pulled."
+          "text": "`jelou logs chat --from` now reads each bot back to the start of the range instead of stopping at its latest page. When a bot still has older items, `notice` says how far back it was read and how to continue."
         },
         {
           "type": "fixed",
-          "text": "`jelou skills check` stays quiet with `JELOU_NO_UPDATE_PROMPT=1` or in a managed runtime, and no longer reports going back to an older version as an update."
-        },
-        {
-          "type": "fixed",
-          "text": "The cost report takes its billing window from the company's own day boundaries, so the bill covers the same days as the message counts whatever timezone the machine runs in."
-        },
-        {
-          "type": "heads_up",
-          "text": "`jelou logs failed` now asks for `CRASHED` and `FAILED` by default; pass `--status CRASHED` for the previous output. `jelou logs chat` returns `botId: null` when more than one bot answered — read `bots` for each one."
+          "text": "`jelou logs failed` no longer fails with \"query too broad\" on a wide window: it splits the window on its own, and still returns crashed executions. Any window that still times out is listed in `failedNodesGaps`."
         }
       ]
     }