@getxflow/cli 0.6.2 → 0.6.3

package/dist/prompt.js

@@ -6,8 +6,8 @@ const node_readline_1 = require("node:readline");
 const errors_1 = require("./errors");
 const ui_1 = require("./ui");
 function render(lines, first) {
-    const up = first ? '' : `[${lines.length}A`;
-    process.stderr.write(up + lines.map((line) => `${line}\n`).join(''));
+    const up = first || lines.length === 1 ? '' : `[${lines.length - 1}A`;
+    process.stderr.write(`${up}\r${lines.map((line) => `${line}`).join('\n')}`);
 }
 function listen(onKey) {
     if (process.stdin.isTTY !== true) {
@@ -17,6 +17,7 @@ function listen(onKey) {
     const wasRaw = process.stdin.isRaw === true;
     process.stdin.setRawMode(true);
     process.stdin.resume();
+    process.stderr.write('[?25l');
     const handler = (_, key) => {
         if (key)
             onKey(key);
@@ -26,6 +27,7 @@ function listen(onKey) {
         process.stdin.off('keypress', handler);
         process.stdin.setRawMode(wasRaw);
         process.stdin.pause();
+        process.stderr.write('[?25h\n');
     };
 }
 const isConfirm = (key) => key.name === 'return' || key.name === 'enter';

package/dist/version.js

@@ -2,6 +2,6 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.DEFAULT_API_URL = exports.CLI_VERSION = void 0;
 /** Keep in sync with cli/package.json. */
-exports.CLI_VERSION = '0.6.2';
+exports.CLI_VERSION = '0.6.3';
 /** Overridden by XFLOW_API_URL or the `api` field in xflow.json. */
 exports.DEFAULT_API_URL = 'https://app.getxflow.com';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getxflow/cli",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "CLI for the XFlow platform: source sync, deployment and publishing of applications",
   "license": "UNLICENSED",
   "engines": {

package/skills/xflow/SKILL.md

@@ -251,6 +251,16 @@ assemble a variable name from an expression and never destructure the environmen
 (`const { API_KEY } = process.env` reads as no mention at all, and the variable arrives
 empty). New values arrive on the next `xflow deploy`, not at the moment they are written.
 
+Some variables come from a connected account instead of from you. When someone connects an
+advertising cabinet or another external service in the platform settings and links it to the
+project, its credentials show up in `xflow env` marked read-only, under a prefix chosen at
+link time: `YANDEX_DIRECT_TOKEN`, `YANDEX_DIRECT_CLIENT_LOGIN`. Read them like any other
+variable. Do not try to `xflow env set` those names: the platform keeps the values in sync
+and refuses. If a call to that service starts failing with an authorisation error, run
+`xflow status`: it says whether the token is merely expiring (any build renews it) or the
+account was disconnected on the provider's side, which only a human can fix by reconnecting
+it in the platform settings.
+
 To run a function on a timer: `xflow schedules set report "0 3 ? * * *"` (daily at 03:00).
 Six fields, UTC, and exactly one of day-of-month / day-of-week must be `?` — that is
 how Yandex wants it. A scheduled run reaches the handler as a POST with no headers.