@uipath/maestro-builder-sdk 6.11.3 → 6.11.4

package/README.md

@@ -115,7 +115,7 @@ network calls. That is what `prepare` is for: it is the one verb that does talk
 to the tenant. Run what `check` named, both fields at once:
 
 ```bash
-npx flow-sdk registry pull    # once per machine: the connector library
+uip maestro registry pull     # once per machine: the connector library
 
 npx flow-sdk registry prepare uipath-salesforce-slack --action send-message-to-user \
   --resolve channel:profile.email=ada@example.com \
@@ -289,7 +289,7 @@ Keeping the names symbolic is what lets one flow move between connections: the
 code says `slack`, and only `bindings.json` knows which Slack.
 
 Discover ops and input shapes from the connector library that
-`npx flow-sdk registry pull` downloads and caches. A field the library does not
+`uip maestro registry pull` downloads and caches. A field the library does not
 carry is connection-specific — that is the `prepare` case from the quick start.
 
 The package also exposes the low-level materializer used by the UiPath CLI to
@@ -302,7 +302,7 @@ flow-registry-materialize \
   --connectors ./connectors
 ```
 
-Most callers want `npx flow-sdk registry pull`, which downloads the published
+Most callers want `uip maestro registry pull`, which downloads the published
 archive, verifies its checksum and then runs this transform. The low-level
 command is for SDK development, build pipelines, and troubleshooting: it only
 transforms local files that are already on disk.
@@ -322,7 +322,7 @@ The step-by-step authoring guides — `SKILL.md` for Flow, `SKILL-case.md`,
 UiPath authoring skills catalog rather than here, so a coding agent and a human
 read the same copy. The worked examples named by those guides travel with them.
 
-The connector library is not bundled: `npx flow-sdk registry pull` downloads it
+The connector library is not bundled: `uip maestro registry pull` downloads it
 and caches it per machine. The package does carry the curated overlay that pull
 applies on top — corrections and the definitions the raw registry dump omits.
 

package/dist/check.js

@@ -1142,7 +1142,8 @@ function checkFlow(built, ancestors, opts = {}) {
                     code: 'MOCK_HAS_NO_OUTPUT',
                     message: `Placeholder "${name}" publishes nothing, but "$vars.${name}${field ? '.' + field : ''}" reads it in "${step}". `
                         + 'A mock() is a marker for a node that does not exist yet — its output is null at run time, always. '
-                        + 'Replace it with the real step before reading it.',
+                        + 'Keep the placeholder while the real node does not exist, and have the reader use a value you supply instead (a flow input, as example/ClaimScaffold.flow.ts does). '
+                        + 'Replace the placeholder only with the real node, once `registry search` finds it; a script returning fixed values is not the real node.',
                     step,
                 });
                 continue;

package/dist/registry/cache.d.ts

@@ -21,6 +21,15 @@
 export declare const LIBRARY_JSON_DIR = "library-json";
 export declare const LIBRARY_MARKDOWN_DIR = "library-md";
 export declare const CURRENT_LINK = "current";
+/**
+ * The command a message tells a person or agent to run when the cache is
+ * empty. It is `uip`, not `npx flow-sdk registry pull`: `uip maestro registry
+ * pull` runs this package's pull and fills the same cache, and it is the one
+ * command the authoring skill teaches. Each message used to spell the command
+ * out by hand, so they kept naming the SDK's own entry point after the skill
+ * moved to `uip`. Name it here once.
+ */
+export declare const PULL_COMMAND = "uip maestro registry pull";
 /**
  * Root of the library cache. `UIP_FLOW_SDK_LIBRARY_CACHE` overrides it.
  *

package/dist/registry/cache.js

@@ -24,6 +24,15 @@ import { join } from "node:path";
 export const LIBRARY_JSON_DIR = "library-json";
 export const LIBRARY_MARKDOWN_DIR = "library-md";
 export const CURRENT_LINK = "current";
+/**
+ * The command a message tells a person or agent to run when the cache is
+ * empty. It is `uip`, not `npx flow-sdk registry pull`: `uip maestro registry
+ * pull` runs this package's pull and fills the same cache, and it is the one
+ * command the authoring skill teaches. Each message used to spell the command
+ * out by hand, so they kept naming the SDK's own entry point after the skill
+ * moved to `uip`. Name it here once.
+ */
+export const PULL_COMMAND = "uip maestro registry pull";
 /**
  * Root of the library cache. `UIP_FLOW_SDK_LIBRARY_CACHE` overrides it.
  *

package/dist/registry/path-cli.js

@@ -1,6 +1,6 @@
 import { reportResult } from '../cli-result.js';
 import { join } from "node:path";
-import { CURRENT_LINK, currentEntrySha, libraryCacheRoot, resolveCachedLibrary, resolveCachedMarkdown, } from "./cache.js";
+import { CURRENT_LINK, PULL_COMMAND, currentEntrySha, libraryCacheRoot, resolveCachedLibrary, resolveCachedMarkdown, } from "./cache.js";
 /**
  * Say where the connector library is.
  *
@@ -34,7 +34,7 @@ export async function run(argv) {
     const single = (field, value) => {
         reportResult({ [field]: value ?? null });
         if (!value) {
-            console.error("No connector library in the cache yet. Run `flow-sdk registry pull`.");
+            console.error(`No connector library in the cache yet. Run \`${PULL_COMMAND}\`.`);
             return 1;
         }
         console.log(value);

package/dist/registry/search-cli.js

@@ -1,6 +1,6 @@
 import { reportResult } from '../cli-result.js';
 import { readFile, stat } from "node:fs/promises";
-import { resolveLibraryDir } from "./cache.js";
+import { PULL_COMMAND, resolveLibraryDir } from "./cache.js";
 import { dirname, join } from "node:path";
 export const DEFAULT_SEARCH_LIMIT = 20;
 const USAGE = "Usage: flow-sdk registry search [query] [--library <dir>] [--library-md <dir>] [--connector <key>] [--limit <n>]";
@@ -52,7 +52,7 @@ export async function searchRegistryOperations(options) {
         content = await readFile(indexPath, "utf-8");
     }
     catch {
-        throw new Error(`Could not read ${indexPath}. Run \`flow-sdk registry pull\`, or point` +
+        throw new Error(`Could not read ${indexPath}. Run \`${PULL_COMMAND}\`, or point` +
             " --library at an extracted connector library.");
     }
     let parsed;
@@ -120,6 +120,10 @@ export async function run(argv) {
     // verbs defaulted it was the inconsistency an author hit first.
     const libraryPath = resolveLibraryDir(value(argv, "--library"));
     if (!libraryPath) {
+        // Say why. A bare usage line here read as "no match" to an agent deciding
+        // between a connector and http(): it took the failed search for a miss.
+        console.error(`No connector library is cached. Run \`${PULL_COMMAND}\`, or pass` +
+            " --library <dir>.");
         console.error(USAGE);
         return 2;
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uipath/maestro-builder-sdk",
-  "version": "6.11.3",
+  "version": "6.11.4",
   "description": "Build UiPath Flow, Case, and BPMN artifacts by writing TypeScript.",
   "license": "MIT",
   "homepage": "https://docs.uipath.com/maestro",
@@ -92,5 +92,5 @@
     "@types/node": "^22.7.0",
     "esbuild": "^0.28.1"
   },
-  "gitref": "e1b0e818f78b7911c691e12ea078d03c851daf76"
+  "gitref": "8c18e5efb6f8dd4b2599f9591cabdff42feaf275"
 }