@getxflow/cli 0.11.0 → 0.11.2

package/dist/api.js

@@ -1,6 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ApiError = void 0;
+exports.isOlder = isOlder;
 exports.newerVersionSeen = newerVersionSeen;
 exports.apiJson = apiJson;
 exports.apiBinary = apiBinary;

package/dist/bin.js

@@ -227,13 +227,15 @@ function nudge() {
 }
 /**
  * The other staleness, and the one that costs more: the instructions an agent reads are
- * older than the CLI answering it, and nothing about that is visible in the text. Louder
- * than the notice above because it is wrong now rather than out of date soon, and it names
- * the file, because a machine can hold a dozen copies and the wrong one gets edited.
+ * not the ones the CLI answering it ships, and nothing about that is visible in the text.
+ * Louder than the notice above because it is wrong now rather than out of date soon, and
+ * it names the file, because a machine can hold a dozen copies and the wrong one gets edited.
  *
  * The command is skills --refresh, not update: what is out of step here is the copies, not
  * the package, and refreshing needs no network, no npm and no rights on a global folder.
- * The re-read is half the repair, so it is in the same breath as the command.
+ * The re-read is half the repair, so it is in the same breath as the command. Except when
+ * a newer CLI is known: then the package itself is behind, a refresh would rewrite the
+ * copies from it, and the update notice above is the whole advice.
  */
 function nudgeSkill() {
     const stale = (0, skills_1.staleSkillCopy)(process.cwd());
@@ -243,10 +245,17 @@ function nudgeSkill() {
         (0, state_1.clearSkillNudges)();
         return;
     }
+    // A newer CLI is published: the copy that differs may well be ahead of this package,
+    // and a refresh would "repair" it backwards. The update notice is the whole advice —
+    // xflow update brings the package and every copy along. Network-free commands see no
+    // headers, so the version an earlier notice named counts as known too.
+    const nudged = (0, state_1.lastNudgedVersion)();
+    if ((0, api_1.newerVersionSeen)() !== null || (nudged !== null && (0, api_1.isOlder)(version_1.CLI_VERSION, nudged)))
+        return;
     const key = `${stale} ${version_1.CLI_VERSION}`;
     if (!(0, state_1.shouldNudgeSkill)(key))
         return;
-    (0, ui_1.warn)(`${stale} is older than this CLI`);
+    (0, ui_1.warn)(`${stale} does not match this CLI`);
     (0, ui_1.note)((0, ui_1.dim)('  Run xflow skills --refresh, then read that file again: the refresh only writes it to disk'));
     (0, state_1.markSkillNudged)(key);
 }
@@ -304,8 +313,8 @@ async function main() {
         if (!quiet)
             nudge();
         // Not behind the same flag: a copy out of step with the running package stays wrong
-        // whatever the command was, and when the package itself is the problem the copies
-        // match it and this says nothing anyway.
+        // whatever the command was, and when the package itself is the problem this steps
+        // aside on its own.
         nudgeSkill();
     }
 }

package/dist/commands/db.js

@@ -177,14 +177,13 @@ async function dbQuery(args) {
     }
     (0, ui_1.table)([data.columns, ...data.rows.map((row) => data.columns.map((column) => cell(row[column])))]);
     if (data.truncated) {
-        // "raise --limit" used to be the whole advice, and for a long time it was
-        // impossible to follow: the ceiling and the default were the same number, so
-        // the flag could only ask for less. Now it can ask for more, and the line
-        // says so only while there is room left.
+        // No exact total here: the platform stops reading at limit + 1 rows, so all
+        // it knows is that more exist. The "raise --limit" advice shows only while
+        // the flag still has room below the ceiling.
         const room = data.limit !== undefined && data.limit_max !== undefined && data.limit < data.limit_max;
         (0, ui_1.note)((0, ui_1.dim)(room
-            ? `  Shown ${data.rows.length} of ${data.total}: raise --limit (up to ${data.limit_max}), or narrow the query`
-            : `  Shown ${data.rows.length} of ${data.total}: narrow the query, with a where clause or an offset`));
+            ? `  Shown the first ${data.rows.length} rows, more exist: raise --limit (up to ${data.limit_max}), or narrow the query`
+            : `  Shown the first ${data.rows.length} rows, more exist: narrow the query, with a where clause or an offset`));
     }
 }
 async function dbMigrate(args) {

package/dist/state.js

@@ -5,6 +5,7 @@ exports.shouldNudgeSkill = shouldNudgeSkill;
 exports.markSkillNudged = markSkillNudged;
 exports.clearSkillNudges = clearSkillNudges;
 exports.markNudged = markNudged;
+exports.lastNudgedVersion = lastNudgedVersion;
 const node_fs_1 = require("node:fs");
 const node_os_1 = require("node:os");
 const node_path_1 = require("node:path");
@@ -78,6 +79,10 @@ function clearSkillNudges() {
 function markNudged(version) {
     write({ nudgedVersion: version, nudgedAt: new Date().toISOString() });
 }
+/** What the update notice last named, for callers that outlive the process that saw it. */
+function lastNudgedVersion() {
+    return read().nudgedVersion ?? null;
+}
 /** Best effort: a read-only home folder must not break the command that just worked. */
 function write(patch) {
     try {

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.11.0';
+exports.CLI_VERSION = '0.11.2';
 /** 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.11.0",
+  "version": "0.11.2",
   "description": "CLI for the XFlow platform: source sync, deployment and publishing of applications",
   "license": "UNLICENSED",
   "engines": {

package/skills/xflow/SKILL.md

@@ -24,11 +24,11 @@ contains the fix.
 
 ## Keeping these instructions current
 
-These instructions ship with xflow CLI 0.11.0. They travel inside the package, so the copy
+These instructions ship with xflow CLI 0.11.2. They travel inside the package, so the copy
 you are reading can be older than the CLI answering your commands, and nothing about that
 is visible in the text itself.
 
-When the CLI says this file is out of date, run `xflow skills --refresh` and then **read
+When the CLI says this file does not match it, run `xflow skills --refresh` and then **read
 again the file it names**. Refreshing only writes new text to disk; until you re-read it you
 are still working from the old rules, and the command will look like it did nothing. This
 repair is yours to make, no need to ask anyone.
@@ -235,6 +235,13 @@ enforces this, but a project where every function answers its own way costs an a
 on every call. Branch the frontend on `error.code`, never on `error.message`: wording
 gets rewritten on any edit, a code does not.
 
+How a non-2xx answer reaches the page depends on the generation of `src/lib/xflow.ts`
+in the project, so look at that file before writing the catch: a copy that declares
+`XFlowError` throws it carrying `code` and `status`, and a copy that says nothing about
+errors is older and throws a plain `Error` whose message is all there is. In an older
+project, a function that wants its error text seen on the page answers `200` with
+`{ success: false, error }` in the body.
+
 The sources are the whole truth about which functions exist. Delete the directory and the
 next deploy would delete the function from the cloud, schedules included, and that cannot be
 undone: a function created again later gets a different address. So never remove a function