@myapihq/cli 2.23.1 → 2.23.2

package/dist/commands/email/mailbox.js

@@ -30,8 +30,20 @@ async function create(addressArg, flags) {
         error('Missing required arguments.\nUsage: myapi email mailbox create <user@domain> [--display-name <name>]\n   or: myapi email mailbox create --username <u> --domain <d> [--display-name <name>]\n(Or set default: myapi config set-domain <domain>)');
     }
     const res = await sdkEmail.createMailbox(config.api_key, domain, username, flags['display-name']);
-    // Backend response sometimes omits address; we know it from the inputs.
-    success(`Mailbox created: ${res.address || `${username}@${domain}`}`);
+    // The address comes back as `mailbox`. It is not "sometimes omitted" — the
+    // previous comment here encoded a wrong theory, which turned a permanent
+    // contract mismatch into an imagined intermittent one and kept it patched
+    // instead of reported. Kept the fallback anyway: the address is derivable
+    // from the inputs, and a create that succeeded should still print what it
+    // made if the field ever moves again.
+    success(`Mailbox created: ${res.mailbox || `${username}@${domain}`}`);
+    // A warning on a 2xx means something is configured but incomplete — here, a
+    // missing CAN-SPAM mailing address, which refuses every send LATER rather
+    // than now. Printing it while the customer is set up in front of the
+    // terminal is the whole point of the backend adding it; dropping it silently
+    // meant the fix reached nobody using the CLI.
+    if (res.warning)
+        info(`› ${res.warning}`);
 }
 async function list(flags) {
     const config = requireConfig();

package/dist/commands/fn.js

@@ -316,7 +316,14 @@ export async function runs(id, flags) {
         error: r.error_message || '',
     })), {
         flags,
-        empty: 'No runs recorded yet for this function.',
+        // An empty list here means "we do not measure this", not "it did not
+        // happen": function_runs has one writer, the workflow engine. A direct call
+        // to the invocation URL is served at the edge and never reaches the backend
+        // to be recorded. ImmoPilot read the old sentence as proof the API was
+        // never called and ruled out the branch of a login investigation that was
+        // the actual problem — the function had run hundreds of times that day.
+        empty: 'No workflow-triggered runs. Direct calls to the invocation URL are served at the edge '
+            + 'and are not recorded here, so an empty list does NOT mean the function was not called.',
     });
 }
 // ── Dispatcher ───────────────────────────────────────────────────────────────

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/cli",
   "license": "Apache-2.0",
-  "version": "2.23.1",
+  "version": "2.23.2",
   "description": "MyAPI command-line interface",
   "repository": {
     "type": "git",
@@ -46,7 +46,7 @@
     "lint:skills:strict": "node scripts/copy-skills.js && node scripts/lint-skills.js --strict"
   },
   "dependencies": {
-    "@myapihq/sdk": "^2.23.1"
+    "@myapihq/sdk": "^2.23.2"
   },
   "devDependencies": {
     "@types/node": "^25.6.0",