@uipath/maestro-builder-sdk 6.66.11 → 6.66.12

package/dist/core/connector-resolve-error.d.ts

@@ -17,6 +17,8 @@ export type ConnectorResolveCode =
  * missing or not valid JSON: the library on disk is incomplete (#1015).
  */
  | 'CONNECTOR_LIBRARY_ENTRY_UNREADABLE'
+/** The index row and its entry file name different objects for the operation. */
+ | 'CONNECTOR_LIBRARY_ENTRY_INCONSISTENT'
 /**
  * Flow only: the sidecar was synthesized from Integration Service by `registry
  * prepare` (no registry node exists), and a Flow node needs the registry's

package/dist/core/library.js

@@ -147,12 +147,10 @@ export class Library {
             if (row)
                 return this.pageOf(nodeType, layer, row);
         }
-        const parts = nodeType.split('.');
-        const eventNs = parts[2] === 'trigger' || parts[2] === 'event';
         const near = nearest(objectName ?? '', objects);
         throw new ConnectorResolveError('CONNECTOR_NOT_IN_LIBRARY', `connector ${nodeType} has no page for object "${objectName}"`
             + `${near ? ` (nearest: "${near}")` : ''}. ${describeObjects(objects)} If it is a connection-scoped object, run `
-            + `\`${prepareCommand(eventNs ? parts[3] : parts[2], (eventNs ? parts.slice(4) : parts.slice(3)).join('.'), '--object', String(objectName))}\` `
+            + `\`${prepareFor(nodeType, '--object', String(objectName))}\` `
             + 'to prepare it, then describe again.');
     }
     /**
@@ -909,36 +907,24 @@ export class Library {
         // bare ENOENT (#1015).
         const entry = readLibraryFile(nodeType, entryPath, () => readJson(this.read, entryPath));
         const v1def = readLibraryFile(nodeType, v1defPathOf(entryPath), () => readV1def(this.read, entryPath));
-        // A stamped object (case 4) reaches here with the index entry's `objectName`
-        // replaced but the sibling's FILE on disk — so restate the object and derive
-        // the endpoint from the sibling's own template, rather than shipping a node
-        // whose `objectName` and `path` name two different objects.
-        // The index and the definition file can disagree about which object the
-        // operation addresses, and the definition is the stale side: for
-        // `uipath-microsoft-outlook365.send-email` the index says `send-mail-v2`
-        // (what the tenant's typecache reports, connector 1.39.0) while the
-        // definition still says `send-mail` with `/hubs/productivity/send-mail`.
-        // `build` reads the definition, so the compiled node dispatched the retired
-        // path and the runtime SendTask failed — the whole external-outcome half of
-        // one eval task, from a one-token disagreement.
-        //
-        // The index is the fresher side and the one resolution keys on, so restate
-        // the object from it and re-derive the endpoint, exactly as the stamped
-        // branch below does. Warned, not silent: it is upstream archive data, so the
-        // author should see that the two sources disagreed. Unique in the current
-        // archive (1 of 8035 entries).
+        // An index row and its definition that name different objects cannot be
+        // reconciled here: the object, path and parameters must come from one
+        // operation. Taking the index's path with the definition's parameters sent
+        // JSON to Outlook's multipart `send-mail-v2` (MST-17534).
         if (!opts.objectNameUnverified && entry.operation
             && typeof e.objectName === 'string' && e.objectName !== ''
             && typeof entry.operation.objectName === 'string'
             && entry.operation.objectName !== e.objectName) {
-            const stale = entry.operation.objectName;
-            const derived = deriveObjectPath(entry.operation, e.objectName);
-            this.warn(`  warn:  connector ${nodeType}: the library index says objectName "${e.objectName}" but its `
-                + `definition file says "${stale}". Using the index and deriving the endpoint`
-                + (derived.path ? ` (${entry.operation.path} -> ${derived.path})` : '')
-                + `; the definition is the stale side when these disagree.\n`);
-            entry.operation = { ...entry.operation, objectName: e.objectName, ...derived };
+            throw new ConnectorResolveError('CONNECTOR_LIBRARY_ENTRY_INCONSISTENT', `connector library entry for ${nodeType} is inconsistent: index.json says objectName `
+                + `"${e.objectName}" but ${e.path} says "${entry.operation.objectName}" `
+                + `(${entry.operation.path ?? 'no path'}). The compiled node would call one operation with `
+                + `another's inputs. Refresh the library with \`${PULL_COMMAND} --force\`, or describe the `
+                + `operation from the live connection with \`${prepareFor(nodeType, ...(e.activityType === 'Generic' ? ['--object', e.objectName] : []))}\`.`);
         }
+        // A stamped object (case 4) reaches here with the index entry's `objectName`
+        // replaced but the sibling's FILE on disk — so restate the object and derive
+        // the endpoint from the sibling's own template, rather than shipping a node
+        // whose `objectName` and `path` name two different objects.
         if (opts.objectNameUnverified && entry.operation) {
             entry.operation = {
                 ...entry.operation,
@@ -1052,6 +1038,12 @@ function libraryEntries(read, path) {
     cache?.set(path, entries);
     return entries;
 }
+/** The `registry prepare` command for a connector action or event `nodeType`. */
+function prepareFor(nodeType, ...rest) {
+    const parts = nodeType.split('.');
+    const eventNs = parts[2] === 'trigger' || parts[2] === 'event';
+    return prepareCommand(eventNs ? parts[3] : parts[2], (eventNs ? parts.slice(4) : parts.slice(3)).join('.'), ...rest);
+}
 function readLibraryFile(nodeType, path, read) {
     try {
         return read();

package/dist/core/refusals.d.ts

@@ -165,6 +165,7 @@ export declare const REFUSALS: {
     readonly CONNECTOR_INPUT_MISSING: "draft";
     readonly CONNECTOR_INPUT_ROW_NO_TARGET: "lint";
     readonly CONNECTOR_INPUT_ROW_TARGET_UNKNOWN: "lint";
+    readonly CONNECTOR_LIBRARY_ENTRY_INCONSISTENT: "lowering";
     readonly CONNECTOR_LIBRARY_ENTRY_UNREADABLE: "lowering";
     readonly CONNECTOR_NODE_TYPE_INVALID: "lowering";
     readonly CONNECTOR_NOT_IN_LIBRARY: "lowering";

package/dist/core/refusals.js

@@ -216,6 +216,7 @@ export const REFUSALS = {
     CONNECTOR_INPUT_MISSING: 'draft',
     CONNECTOR_INPUT_ROW_NO_TARGET: 'lint',
     CONNECTOR_INPUT_ROW_TARGET_UNKNOWN: 'lint',
+    CONNECTOR_LIBRARY_ENTRY_INCONSISTENT: 'lowering',
     CONNECTOR_LIBRARY_ENTRY_UNREADABLE: 'lowering',
     CONNECTOR_NODE_TYPE_INVALID: 'lowering',
     CONNECTOR_NOT_IN_LIBRARY: 'lowering',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uipath/maestro-builder-sdk",
-  "version": "6.66.11",
+  "version": "6.66.12",
   "description": "Build UiPath Flow, Case, and BPMN artifacts by writing TypeScript.",
   "license": "MIT",
   "homepage": "https://docs.uipath.com/maestro",
@@ -100,5 +100,5 @@
     "@types/node": "^22.7.0",
     "esbuild": "^0.28.1"
   },
-  "gitref": "308e41ca7b62e6bb7dda3a974c00fbee9141b757"
+  "gitref": "09e14700793a9cacefa30495f49e5a5753995226"
 }