@viu/emporix-sdk 3.1.0 → 3.2.0

package/CHANGELOG.md

@@ -1,5 +1,52 @@
 # @viu/emporix-sdk
 
+## 3.2.0
+
+### Minor Changes
+
+- [#311](https://github.com/viuteam/emporix-sdk/pull/311) [`93816b2`](https://github.com/viuteam/emporix-sdk/commit/93816b231b01babfbbf42704279bcd53809462fe) Thanks [@amnael1](https://github.com/amnael1)! - feat(sdk): add the import analytics reads and failed-record retry
+
+  Five operations Emporix added to the Import Service on 2026-08-26 ([changelog](https://developer.emporix.io/changelog#import-service-analytics-and-failed-record-retry)),
+  all on the `importtool.import_trigger` scope the rest of that surface already uses:
+  - `client.imports.stats(query?)` — aggregated analytics: totals, a time series,
+    an error breakdown, per-stream health and stream changes. `sections` decides
+    which the service computes, so name what you render.
+  - `client.imports.listJobGroups()` — the dashboard's job groups, configurations
+    with their runs grouped under them.
+  - `client.imports.getHealthThresholds()` — the error rates above which a stream
+    counts as degraded or failing in `stats`. Read-only; changing them needs
+    `importtool.import_manage`.
+  - `client.imports.getLicense()` — import limits and current consumption.
+  - `client.imports.retryRun(runId)` — re-process only a run's failed records.
+
+  **`retryRun` returns a new run**, not a mutated original: its `id` differs and
+  `retry` is `true`. Poll it with `getRun` or follow it with `streamRun` exactly as
+  you would a triggered run. Like `triggerRun` it is not retried on a 5xx — a POST
+  that timed out may already have queued the retry.
+
+  The types for all five had already arrived with the spec sync, so this is the
+  facade catching up rather than new modelling. That is also why the gap was easy to
+  miss: a sync PR looks like a types-only diff, and five operations sitting there
+  without a wrapper show up in no diff at all.
+
+  Nothing was needed for the seven endpoints the same release _changed_. This
+  package's facade types are aliases of the generated ones, so the added response
+  fields — `aiEnabled`, `version`, `healthThresholds`, `createdBy` on a config, and
+  `retry` / `force` / `dryRun` on a run — were already reachable, as was `force` on
+  `triggerRun`'s body. Only that body's JSDoc was stale and now names all three
+  fields.
+
+  Upstream still marks the whole Import Service as preview; every new method says
+  so, like its neighbours.
+
+## 3.1.1
+
+### Patch Changes
+
+- [#305](https://github.com/viuteam/emporix-sdk/pull/305) [`4dfeefc`](https://github.com/viuteam/emporix-sdk/commit/4dfeefcdab7fe9d6b41e31d9cee6f4763b8862f2) Thanks [@viu-release-bot](https://github.com/apps/viu-release-bot)! - chore(sdk): sync generated types with upstream Emporix API specs
+
+  Updated services: ai-service,import-service
+
 ## 3.1.0
 
 ### Minor Changes

package/dist/index.cjs

@@ -1242,7 +1242,7 @@ var HttpClient = class {
 };
 
 // package.json
-var version = "3.1.0";
+var version = "3.2.0";
 
 // src/version.ts
 var SDK_VERSION = version;
@@ -8267,6 +8267,91 @@ var ImportService = class {
     });
     return toPage(wire, args);
   }
+  // ─── Analytics and retry (upstream release 2026-08-26) ─────────────────────
+  /**
+   * Aggregated import analytics.
+   *
+   * Every section is optional in the response, and `sections` is what decides
+   * which the service computes — asking for all of them on a tenant with a long
+   * history is the expensive call, so name the ones you render.
+   *
+   * `from` / `to` are ISO timestamps. Omitted, the service picks its own window;
+   * do not assume it is «everything».
+   *
+   * **Preview upstream**: the contract may change without a major bump.
+   */
+  async stats(query = {}, auth2 = SERVICE29) {
+    return this.ctx.http.request({
+      method: "GET",
+      path: `${this.base()}/stats`,
+      query: { ...query },
+      auth: auth2
+    });
+  }
+  /**
+   * The dashboard's job groups: configurations with their runs grouped under
+   * them.
+   *
+   * Named after the path rather than the summary («Retrieving job groups»)
+   * because the resource lives under `/dashboard` and is shaped for that view —
+   * a caller wanting plain run history wants {@link listRuns}.
+   *
+   * **Preview upstream**: the contract may change without a major bump.
+   */
+  async listJobGroups(auth2 = SERVICE29) {
+    return this.ctx.http.request({
+      method: "GET",
+      path: `${this.base()}/dashboard/job-groups`,
+      auth: auth2
+    });
+  }
+  /**
+   * The tenant's health thresholds — the error rates above which a stream counts
+   * as degraded or failing in {@link stats}.
+   *
+   * Read-only here: changing them needs `importtool.import_manage`, which this
+   * service does not cover.
+   *
+   * **Preview upstream**: the contract may change without a major bump.
+   */
+  async getHealthThresholds(auth2 = SERVICE29) {
+    return this.ctx.http.request({
+      method: "GET",
+      path: `${this.base()}/settings/health-thresholds`,
+      auth: auth2
+    });
+  }
+  /**
+   * The tenant's import limits and current consumption.
+   *
+   * **Preview upstream**: the contract may change without a major bump.
+   */
+  async getLicense(auth2 = SERVICE29) {
+    return this.ctx.http.request({
+      method: "GET",
+      path: `${this.base()}/license`,
+      auth: auth2
+    });
+  }
+  /**
+   * Retry only the failed records of a finished run.
+   *
+   * Returns a **new** run — the retry is its own run with `retry: true`, not a
+   * mutation of the original. Poll it with {@link getRun} or follow it with
+   * {@link streamRun} exactly as you would a triggered run.
+   *
+   * Not retried on a 5xx, for the same reason {@link triggerRun} is not: a POST
+   * that timed out may already have queued the retry.
+   *
+   * **Preview upstream**: the contract may change without a major bump.
+   */
+  async retryRun(runId, auth2 = SERVICE29) {
+    return this.ctx.http.request({
+      method: "POST",
+      path: `${this.base()}/runs/${encodeURIComponent(runId)}/retry`,
+      auth: auth2
+    });
+  }
 };
 
 // src/services/unit-handling.ts