@getxflow/cli 0.34.1 → 0.34.2

package/dist/bin.js

@@ -343,6 +343,11 @@ async function main() {
             const hint = e instanceof errors_1.CliError ? e.hint : undefined;
             if (hint)
                 (0, ui_1.fatalNote)((0, ui_1.dim)(`  ${hint}`));
+            // The command may exist in a newer release: this path never reaches the platform,
+            // so the update notice below has no version to go on and stays silent.
+            if (e instanceof errors_1.CliError && e.message.startsWith('Unknown command')) {
+                (0, ui_1.fatalNote)((0, ui_1.dim)('  If the command is new, this CLI may be behind: run xflow update'));
+            }
             return 1;
         }
         (0, ui_1.fatal)(e instanceof Error ? e.message : String(e));

package/dist/commands/db.js

@@ -273,7 +273,7 @@ async function dbQuery(args) {
         ? (0, text_file_1.readTextFile)(typed, 'An argument ending in .sql is read as a file: check the path, or end the query with ;')
         : typed;
     if (!sql) {
-        throw new errors_1.CliError(typed ? `${typed} is empty` : 'A query is required', 'For example: xflow db query "select * from orders order by created_at desc limit 20", ' +
+        throw new errors_1.CliError(typed ? `${typed} is empty` : 'A query is required', "For example: xflow db query 'select * from orders order by created_at desc limit 20', " +
             'or a long one from a file outside the project: xflow db query ../report.sql');
     }
     const { projectId, client } = await (0, session_1.projectTarget)(args);

package/dist/help.js

@@ -85,7 +85,7 @@ ${(0, ui_1.bold)('Database')}
   xflow db status                 which migrations are applied and which are waiting
   xflow db list                   databases of the organization, servers, projects
   xflow db schema [table]         tables of the project, or the columns of one
-  xflow db query "select ..."     read data, in a read-only transaction
+  xflow db query 'select ...'     read data, in a read-only transaction
   xflow db migrate [--dry-run] [--allow-destructive]
                                   apply the migrations from migrations/*.sql
   xflow db move --to <server> --confirm <database>
@@ -161,7 +161,7 @@ check ${(0, ui_1.bold)('xflow org')}.`,
 Every command that only talks to the platform takes it, so a service project needs
 no working copy of its own:
 
-  xflow db query --project 3f2a… "select id, title from tasks where done = false"
+  xflow db query --project 3f2a… 'select id, title from tasks where done = false'
   xflow functions invoke kanban --project 3f2a… --data-file card.json
 
 Which commands: ${(0, ui_1.bold)('db status')}, ${(0, ui_1.bold)('db query')}, ${(0, ui_1.bold)('db schema')}, ${(0, ui_1.bold)('db move')}, ${(0, ui_1.bold)('functions list')},
@@ -297,7 +297,7 @@ will work.`,
   xflow db status                  what is applied, what is waiting, the server
   xflow db list                    databases of the organization: servers, projects
   xflow db schema [table]          tables of the project, or the columns of one
-  xflow db query "select ..."      read data (--limit N: 50 by default, 300 at most;
+  xflow db query 'select ...'      read data (--limit N: 50 by default, 300 at most;
                                    --json prints the values whole)
   xflow db query <file>.sql        the same, the query read from a file
   xflow db migrate                 apply migrations/*.sql
@@ -329,9 +329,11 @@ paying for and deleting servers stay with the person, in the web interface.
 ${(0, ui_1.bold)('schema')} answers a different question than the ${(0, ui_1.bold)('migrations/')} directory: one logical
 database is shared by several projects, so the files say what you did, and the schema
 says what is actually in there. ${(0, ui_1.bold)('query')} runs inside a READ ONLY transaction, so
-writes are rejected by the database itself, not by us reading your SQL. A query with
-double quotes goes in a .sql file outside the project: Windows PowerShell strips them from
-arguments, and a file in migrations/ would be taken for a migration. Its table cuts
+writes are rejected by the database itself, not by us reading your SQL. Single quotes around
+the query hold in PowerShell, bash and zsh, while cmd.exe wants double ones; a query that
+needs quotes of its own goes in a .sql file outside the project, because Windows PowerShell
+strips double quotes from arguments and a file in migrations/ would be taken for a
+migration. Its table cuts
 long values to keep the columns readable; ${(0, ui_1.bold)('--json')} prints them whole, together with
 the applied limit and its ceiling. ${(0, ui_1.bold)('status')} named by id (${(0, ui_1.bold)('--project')}) answers with
 the applied history alone: comparing against ${(0, ui_1.bold)('migrations/')} needs the folder.

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

package/skills/xflow/SKILL.md

@@ -22,7 +22,7 @@ contains the fix.
 
 ## Keeping these instructions current
 
-These instructions ship with xflow CLI 0.34.1, so the copy you are reading can be older than
+These instructions ship with xflow CLI 0.34.2, so the copy you are reading can be older than
 the CLI answering your commands.
 
 When the CLI says this file does not match it, run `xflow skills --refresh` and then **read
@@ -482,10 +482,11 @@ One logical database can be shared by several projects, so your migration can br
 do not see: `xflow db status` lists applied migrations with no file in your repository (that is
 somebody else's project), and `xflow db list` names who else is on yours. For the same reason
 `migrations/` is not the schema. It says what you did; `xflow db schema [table]` says what is in
-the database right now, and `xflow db query "select ..."` reads it inside a READ ONLY
-transaction (50 rows by default, `--limit` up to 300; `--json` prints long values whole). A query
-with double quotes goes in a `.sql` file outside the project, `xflow db query ../q.sql`: PowerShell
-strips them from arguments. Look before you write a migration against a shared database.
+the database right now, and `xflow db query 'select ...'` reads it inside a READ ONLY
+transaction (50 rows by default, `--limit` up to 300; `--json` prints long values whole). Single
+quotes hold in PowerShell, bash and zsh, while cmd.exe wants double ones; a query that needs
+quotes of its own goes in a `.sql` file outside the project, `xflow db query ../q.sql`, because
+PowerShell strips double quotes from arguments. Look before you write a migration against a shared database.
 
 An organization can have own database servers, several of them for different jobs. `xflow db
 list` names the server of each database (`platform` is the common one) and lists the own servers