@jelou/cli 3.3.0 → 3.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jelou/cli",
-  "version": "3.3.0",
+  "version": "3.4.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": "3.3.0",
-    "@jelou/cli-darwin-x64": "3.3.0",
-    "@jelou/cli-linux-x64": "3.3.0",
-    "@jelou/cli-linux-arm64": "3.3.0",
-    "@jelou/cli-win32-x64": "3.3.0"
+    "@jelou/cli-darwin-arm64": "3.4.0",
+    "@jelou/cli-darwin-x64": "3.4.0",
+    "@jelou/cli-linux-x64": "3.4.0",
+    "@jelou/cli-linux-arm64": "3.4.0",
+    "@jelou/cli-win32-x64": "3.4.0"
   },
   "keywords": [
     "jelou",
@@ -56,43 +56,35 @@
     "access": "public"
   },
   "jelou": {
-    "minVersion": "3.3.0",
+    "minVersion": "3.4.0",
     "release_notes": {
-      "version": "3.3.0",
+      "version": "3.4.0",
       "date": "2026-09-30",
-      "headline": "Live WhatsApp tests now drive the phone through `jelou` itself — mobile-mcp is no longer needed.",
+      "headline": "The CLI now supports the Email channel end to end — create the channel, build its workflows, and test them with a synthetic email.",
       "highlights": [
         {
           "type": "new",
-          "text": "`jelou test whatsapp tap`, `back` and `swipe` act on the phone and return the screen they land on; `prepare-text` fills the chat with accents and emoji intact."
+          "text": "`jelou channels create --type email --email <address>` creates the channel with its bot, prints the address to forward the mailbox to, and sends the sender confirmation (`--domain` prints DNS records instead)."
         },
         {
           "type": "new",
-          "text": "`jelou test whatsapp inspect-screen` and `screenshot` read Settings, menus, WhatsApp Flows and the in-app browser, where `read-screen` only reports `other`."
+          "text": "`jelou channels email status`, `verify` and `close-workflow` show what still blocks the channel, check the sender or domain, and run a workflow when a ticket closes."
         },
         {
           "type": "new",
-          "text": "`jelou functions secrets set KEY --generate` stores a random secret without ever printing it (`--bytes N`, default 32). On a KEY that already exists it asks first, and needs `--yes` under `--agent`."
+          "text": "`jelou workflow create --channel EMAIL` creates the workflow on the Email channel instead of WhatsApp."
         },
         {
-          "type": "fixed",
-          "text": "`jelou test whatsapp read-screen` no longer hangs when another tool holds the phone — it names the blocker, or says the screen is off — and reads webviews whose text contains quotes instead of returning an empty screen."
-        },
-        {
-          "type": "fixed",
-          "text": "`jelou workflow validate` follows `option:<id>` branches when it checks for unwired interactive options."
-        },
-        {
-          "type": "improved",
-          "text": "`jelou test whatsapp doctor` checks that the phone's screen can be read, instead of looking for a mobile-mcp config."
+          "type": "new",
+          "text": "`jelou test send text --email <file.json>` sends a synthetic inbound email, or the ticket-close event, to an EMAIL workflow."
         },
         {
           "type": "improved",
-          "text": "Workflows laid out from scratch come out the same every time, with retry loops kept left to right."
+          "text": "Building an email workflow now follows its own guide: HTML replies, the email and ticket fields, and ticket handoff over HTTP instead of CONNECT."
         },
         {
           "type": "heads_up",
-          "text": "`jelou workflow validate` and `jelou push` now refuse a CODE node that builds or stores a PDF."
+          "text": "`jelou push` now warns about an image block in an email workflow — the email would carry neither the image nor a body. Use text instead."
         }
       ]
     }