@wix/evalforge-evaluator 0.180.0 → 0.181.0

package/build/types/api-client.d.ts

@@ -61,15 +61,16 @@ export interface ApiClientOptions {
  * The ambassador request factories emit fully-qualified gateway paths that
  * already include the `/_api/evalforge-backend` prefix (e.g.
  * `/_api/evalforge-backend/v1/projects/{id}/eval-runs/{id}`). `serverUrl` also
- * carries that prefix — it is the REST base used by `putJson`/trace-push — so
- * using it directly as the HttpClient `baseURL` duplicates the prefix
+ * carries that prefix — it is the REST base `putJson` uses for the one
+ * remaining legacy write (`updateEvalRun`) — so using it directly as the
+ * HttpClient `baseURL` duplicates the prefix
  * (`.../_api/evalforge-backend/_api/evalforge-backend/v1/...`) and every
  * ambassador call 404s: the run starts but the evaluator can't fetch its data,
  * so the eval fails with no results.
  *
  * Returning the origin only keeps the ambassador-emitted path intact while the
- * REST writes keep using the full `serverUrl`. Origin-only inputs (the local
- * in-cluster `http://host:port`) are returned unchanged.
+ * REST `updateEvalRun` write keeps using the full `serverUrl`. Origin-only
+ * inputs (the local in-cluster `http://host:port`) are returned unchanged.
  *
  * @param serverUrl - Base URL of the server (e.g., "https://bo.wix.com/_api/evalforge-backend")
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/evalforge-evaluator",
-  "version": "0.180.0",
+  "version": "0.181.0",
   "description": "EvalForge Evaluator",
   "bin": "./build/index.js",
   "files": [
@@ -71,5 +71,5 @@
       "artifactId": "evalforge-evaluator"
     }
   },
-  "falconPackageHash": "5ce316680bd58179748e28f277b656cd718bb6b1e7272af06059a26d"
+  "falconPackageHash": "493d50fade4c488a41b6d072b1d1b500cc4c7dea4090888d9e34ac38"
 }