@jelou/cli 1.81.0 → 1.81.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "1.81.0",
+  "version": "1.81.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.81.0",
-    "@jelou/cli-darwin-x64": "1.81.0",
-    "@jelou/cli-linux-x64": "1.81.0",
-    "@jelou/cli-linux-arm64": "1.81.0",
-    "@jelou/cli-win32-x64": "1.81.0"
+    "@jelou/cli-darwin-arm64": "1.81.1",
+    "@jelou/cli-darwin-x64": "1.81.1",
+    "@jelou/cli-linux-x64": "1.81.1",
+    "@jelou/cli-linux-arm64": "1.81.1",
+    "@jelou/cli-win32-x64": "1.81.1"
   },
   "keywords": [
     "jelou",
@@ -58,33 +58,21 @@
   "jelou": {
     "minVersion": "1.80.0",
     "release_notes": {
-      "version": "1.81.0",
+      "version": "1.81.1",
       "date": "2026-08-03",
-      "headline": "Broken WhatsApp nodes are now caught before they ship: a Flow step must point at a Flow that really exists, and contact cards finally get validated.",
+      "headline": "`jelou functions logs` now shows the newest lines and says when the log endpoint fails, instead of reporting that a function has no logs.",
       "highlights": [
-        {
-          "type": "new",
-          "text": "`jelou channels flows <bot-id>` lists the WhatsApp Flows a bot's provider actually holds. It exits `NO_WHATSAPP_FLOWS` when there are none and `WHATSAPP_FLOWS_UNAVAILABLE` when the provider has no Flows API or the listing cannot be authorized — so \"none exist\" and \"could not check\" never look alike."
-        },
         {
           "type": "fixed",
-          "text": "A WhatsApp Flow step authored without a real `flow_id` — or with the one from the docs — now fails validation instead of pushing clean and failing to render when the message is sent."
+          "text": "`functions logs --history` reported \"No logs found\" when the log endpoint had actually failed. The endpoint answers with HTTP 200 and an `error` field, which the CLI ignored — so an upstream failure was indistinguishable from a function that had never logged. The failure is now reported with the upstream message and a non-zero exit."
         },
         {
           "type": "fixed",
-          "text": "Flow nodes missing `text`, `title` or `parameters.flow_cta` are now validated on the pulled-workflow path too, not only on locally authored drafts."
+          "text": "`--order desc` returns the NEWEST entries. The endpoint ignores ordering and always serves the oldest page first, so `--order desc --limit 6` used to hand back the six OLDEST lines; the newest only appeared if you inflated `--limit` until a page happened to reach the end of the log. `desc` now pages to the end and keeps the last N. It costs one request per page, so narrow with `--since` when you only need recent lines."
         },
         {
           "type": "fixed",
-          "text": "Contact cards were invisible to the CLI: `contacts` messages resolved to no known node kind, so nothing validated them and nothing filled the row ids the editor keys its phone/email/address/url lists by. Cards now get those ids, keep any the editor already assigned, and a card with no first name is rejected."
-        },
-        {
-          "type": "fixed",
-          "text": "`jelou models list` and `jelou models show` reported wholesale model prices rather than what your company is actually charged. The cached catalog is now keyed per company, so two companies driven from one machine can no longer read each other's rates."
-        },
-        {
-          "type": "heads_up",
-          "text": "Existing installs keep their old agent skill files. Run `jelou agent install` to pick up the new build guidance — an agent adding a Flow step now checks which Flows exist and asks you which one to use, instead of inventing an id."
+          "text": "`--limit` above 1000 returned nothing at all: the endpoint's ceiling is 1000 and anything higher tripped the error path above. The value is clamped to 1000 per page, and the CLI says so rather than silently changing what you asked for."
         }
       ]
     }