@uipath/maestro-builder-sdk 6.15.3 → 6.15.4

package/dist/check.js

@@ -3940,19 +3940,46 @@ function checkHttp(step, inputs, diags) {
     // Moving to the managed node is not a rename. A plain step keeps a non-2xx on
     // the SUCCESS path (`out(step,'statusCode')`); the managed one fails on it, so
     // a status branch becomes an error handler reading the envelope's `status`.
-    // That rewrite is the author's call, so the warning states the trade rather
-    // than pretending it is mechanical.
+    //
+    // It is not a free upgrade either, and for a connection-less URL it is usually
+    // the wrong move (flow-builder-sdk#898). With no `connection` the managed node
+    // still goes through Integration Service: serialize emits the `uipath-uipath-http`
+    // connector on `ImplicitConnection`, so the request leaves from IS's SHARED
+    // egress. Measured on slack-weather-pipeline (3/3 runs): agents took the old
+    // `managed: true` hint, and Open-Meteo answered that egress 429 "Daily API
+    // request limit exceeded" while direct calls from the same box got 200. The
+    // plain node goes direct. So the hint only steers toward `managed: true` when
+    // the step was given connection settings; the two other real reasons to move
+    // (a binding, an `.onError()`) already fire as errors with that suggestion
+    // (HTTP_BINDING_REQUIRES_MANAGED, HTTP_ONERROR_V1).
     if (inputs && !inputs.managed) {
-        diags.push({
-            level: 'warning',
-            code: 'HTTP_V1_RETIRED',
-            message: `Step "${step}" emits core.action.http, which the tenant registry no longer serves (only `
-                + `core.action.http.v2). It still runs today. Moving to managed: true changes behaviour rather than just `
-                + `the node type: a non-2xx stops arriving on the success path with statusCode and fails the step instead, `
-                + `so a status branch becomes an .onError() handler reading err('${step}', 'status').`,
-            step,
-            suggestion: `http({ url: …, managed: true })`,
-        });
+        const asked = inputs;
+        const wantsConnection = asked.connection !== undefined || asked.folder !== undefined
+            || asked.targetConnector !== undefined;
+        diags.push(wantsConnection
+            ? {
+                level: 'warning',
+                code: 'HTTP_V1_RETIRED',
+                message: `Step "${step}" emits core.action.http, which the tenant registry no longer serves (only `
+                    + `core.action.http.v2). It sets Integration Service connection settings, which only the managed node `
+                    + `can use. Moving to managed: true changes behaviour rather than just the node type: a non-2xx stops `
+                    + `arriving on the success path with statusCode and fails the step instead, so a status branch becomes `
+                    + `an .onError() handler reading err('${step}', 'status').`,
+                step,
+                suggestion: `http({ url: …, managed: true, connection, folder })`,
+            }
+            : {
+                level: 'warning',
+                code: 'HTTP_V1_RETIRED',
+                message: `Step "${step}" emits core.action.http, which the tenant registry no longer serves (only `
+                    + `core.action.http.v2). It still compiles, validates and runs, and it calls the URL directly. For a URL `
+                    + `that needs no Integration Service connection, keep managed: false. managed: true is not a drop-in `
+                    + `replacement: even without a connection it sends the request through Integration Service's shared `
+                    + `egress (rate limits there are shared, and public APIs can answer 429 where a direct call succeeds), `
+                    + `and a non-2xx fails the step instead of arriving with statusCode. Switch only if the call needs an `
+                    + `Integration Service connection or an .onError() handler.`,
+                step,
+            });
     }
     const connection = inputs?.connection;
     const folder = inputs?.folder;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uipath/maestro-builder-sdk",
-  "version": "6.15.3",
+  "version": "6.15.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": "a85d11af254f270d645ec46d57994ccb800ebc1f"
+  "gitref": "37cc4f8cdcd0cfae5ec65c17d389c762e74f4a7c"
 }