@getxflow/cli 0.20.0 → 0.20.1

package/dist/limits.js

@@ -62,6 +62,10 @@ function sizeLabel(mb) {
     return `${Number.isInteger(gb) ? String(gb) : gb.toFixed(1)} GB`;
 }
 function quotaValue(key, use) {
+    // null is a plan feature, not a missing number: the plan does not cap this.
+    if (use.limit === null) {
+        return key.endsWith('_mb') ? `${sizeLabel(use.used)} used, no limit` : `${use.used} used, no limit`;
+    }
     // Same unit on both sides: "0.2 of 15 GB", not "245 of 15360".
     if (key.endsWith('_mb')) {
         const used = use.limit >= 1000 ? (use.used / 1000).toFixed(1) : String(use.used);

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.20.0';
+exports.CLI_VERSION = '0.20.1';
 /** 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.20.0",
+  "version": "0.20.1",
   "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.20.0, so the copy you are reading can be older than
+These instructions ship with xflow CLI 0.20.1, 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
@@ -60,10 +60,11 @@ the error points away from the cause. The sections below carry the details.
 
 ## Plan limits
 
-The organization runs on a plan with finite limits: projects, databases, functions, active
+The organization runs on a plan with limits: projects, databases, functions, active
 connections, seats, database and file storage, function minutes, builds per month and at
-once, schedules and how often they may run. `xflow whoami` prints every one of them next to
-what is used, and the rights of your own key with them: destroying data in a migration,
+once, schedules and how often they may run. Most are finite; a plan may leave one uncapped,
+and then `whoami` prints `no limit` instead of a ceiling. `xflow whoami` prints every one of
+them next to what is used, and the rights of your own key with them: destroying data in a migration,
 deleting files from storage and linking a connected account each need a right that is off by
 default. Reading it before a long task turns a refusal halfway through the work into a
 sentence said before it starts.
@@ -150,6 +151,10 @@ Build setup:
 - Heavy media does not belong in the sources at all: the archive is capped at 10 MB and
   the built application at 15 MB unpacked. Upload it with `xflow storage push` instead
   and refer to the addresses it prints, see **File storage**.
+- Every file in the project is named with latin letters, digits, spaces and `. - _ ~`.
+  A name outside that set does not survive unpacking in the build sandbox, so `Größe.png`
+  and `логотип.png` break the build the same way. This is about the file name, not its
+  contents: interface text stays in whatever language the application speaks.
 
 Platform contract, checked across all of `src/`: