@jelou/cli 1.91.0 → 1.92.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (1) hide show
  1. package/package.json +22 -38
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jelou/cli",
3
- "version": "1.91.0",
3
+ "version": "1.92.0",
4
4
  "description": "Build AI agents on the Jelou platform — from your terminal or your AI editor.",
5
5
  "author": "Jelou Inc. (https://jelou.ai)",
6
6
  "license": "SEE LICENSE IN LICENSE",
@@ -23,11 +23,11 @@
23
23
  "THIRD_PARTY_NOTICES.md"
24
24
  ],
25
25
  "optionalDependencies": {
26
- "@jelou/cli-darwin-arm64": "1.91.0",
27
- "@jelou/cli-darwin-x64": "1.91.0",
28
- "@jelou/cli-linux-x64": "1.91.0",
29
- "@jelou/cli-linux-arm64": "1.91.0",
30
- "@jelou/cli-win32-x64": "1.91.0"
26
+ "@jelou/cli-darwin-arm64": "1.92.0",
27
+ "@jelou/cli-darwin-x64": "1.92.0",
28
+ "@jelou/cli-linux-x64": "1.92.0",
29
+ "@jelou/cli-linux-arm64": "1.92.0",
30
+ "@jelou/cli-win32-x64": "1.92.0"
31
31
  },
32
32
  "keywords": [
33
33
  "jelou",
@@ -58,57 +58,41 @@
58
58
  "jelou": {
59
59
  "minVersion": "1.89.0",
60
60
  "release_notes": {
61
- "version": "1.91.0",
62
- "date": "2026-08-10",
63
- "headline": "Thirteen findings from a QA pass over `jelou tool`. The common thread: the CLI knew what went wrong and reported something else.",
61
+ "version": "1.92.0",
62
+ "date": "2026-08-11",
63
+ "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.",
64
64
  "highlights": [
65
65
  {
66
- "type": "new",
67
- "text": "`jelou tool unpublish <tool-id> <version>` removes one published version. This is the prerequisite for `jelou tool delete`, which the server refuses while any published version survives — and now says so."
68
- },
69
- {
70
- "type": "improved",
71
- "text": "Every 422 from the workflows API reports its real reason. The server buries it behind a fixed \"Unprocessable entity\", which is what you used to see for every failure, on every tool command."
72
- },
73
- {
74
- "type": "improved",
75
- "text": "`jelou tool show` accepts any slug `jelou tool list` prints, with no linked project — and reports a slug for a tool looked up by numeric id instead of null. A slug is derived from the tool name by the CLI; the server has no such field."
76
- },
77
- {
78
- "type": "improved",
79
- "text": "`jelou test tool` refuses a missing required input with exit 2 before the request goes out. The server answers a missing input with 500, which classified as retryable — so an agent would retry a call that could never succeed."
80
- },
81
- {
82
- "type": "improved",
83
- "text": "`jelou test tool` distinguishes its three failures by code: TOOL_FAILED_OUTPUT (the graph fired a FAILED output on purpose), TOOL_NODE_FAILED (a node threw), TOOL_PARKED (no output, no failed node). Exit codes are unchanged."
66
+ "type": "fixed",
67
+ "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."
84
68
  },
85
69
  {
86
- "type": "improved",
87
- "text": "A parked tool run now names the async TOOL node as a cause: with the `brain_async_tool_node` flag on, a nested TOOL node suspends by default and the parent never sees a result. Set \"async\": false to force the synchronous path."
70
+ "type": "fixed",
71
+ "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."
88
72
  },
89
73
  {
90
74
  "type": "fixed",
91
- "text": "`--json` and `--agent` survive an argument error. A missing argument used to produce colored help on stdout and no error envelope at all."
75
+ "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."
92
76
  },
93
77
  {
94
78
  "type": "fixed",
95
- "text": "`jelou tool input|output add|update|delete` keep tools/<slug>.json and the lockfile in sync. They wrote only to the server, so the next `jelou tool push` deleted the fields you had just added."
79
+ "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."
96
80
  },
97
81
  {
98
- "type": "fixed",
99
- "text": "Push conflict diagnosis names the half that actually moved. A rename was reported as a contract change, sending authors hunting for input/output edits that never happened."
82
+ "type": "improved",
83
+ "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."
100
84
  },
101
85
  {
102
- "type": "fixed",
103
- "text": "`jelou workflow node-spec` tells a real node type with no authoring spec card apart from one that does not exist. PMA is a real node type — it is banned inside tools for a reason, and the command implied it was fictional."
86
+ "type": "improved",
87
+ "text": "`jelou channels list` takes a search term, passed through to the Channels API — find a channel by name instead of paging toward it."
104
88
  },
105
89
  {
106
- "type": "fixed",
107
- "text": "`jelou tool pull` names the scopes it searched. Only SHARED and PURCHASED tools are pullable; a BRAIN- or marketplace-scoped tool is absent from that catalog while being perfectly real."
90
+ "type": "heads_up",
91
+ "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."
108
92
  },
109
93
  {
110
94
  "type": "heads_up",
111
- "text": "`jelou tool clone` still cannot clone. The server's clone endpoint scopes its lookup by a parameter its own route never provides, so it returns \"not found\" for every tool id. The CLI now confirms the tool is reachable and tells you the endpoint is broken, with the manual workaround, instead of leaving you hunting for the right id."
95
+ "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."
112
96
  }
113
97
  ]
114
98
  }