@isnap/sdk 1.3.0-next.34 → 1.3.0-next.36

package/CHANGELOG.md

@@ -21,6 +21,7 @@ All notable changes to `@isnap/sdk` will be documented in this file. The format
 
 ### Changed
 - `src/generated/openapi.d.ts` is now generated from the **published** contract. `packages/backend/openapi.json` carries only the partner-facing `/v1/*` surface, so the internal operator routes (`/admin`, `/va`, `/farm-ops`, `/kam`, `/auth`, …) and the bridge-only `/v1/device/*` contract — plus every schema reachable only from them — are no longer emitted into the SDK types. Those routes are the dashboard, the ops back-office and the device bridge; none of them is part of the partner contract this SDK wraps, and no `ISnapClient` method referenced their types, so no documented method changes shape.
+- **`AppDownloadEntry.version` is now `string | null`** (API `1.15.0`, WHA-2538) — source-breaking for a consumer that renders `apps.manifest()`'s `version` without narrowing, which is the point. The field used to be a per-deployment configured string tied to no artifact: staging advertised `0.1.0-staging` for both platforms while the Mac ran `0.0.209` and the update channel published `0.0.x`, so the number could not be installed and the two platforms agreed only because both read one env value. It is now read from the release feed beside the artifact the download URL resolves to, and is `null` when that feed publishes nothing. Render the absence; do not substitute a number, and do not treat `null` as an error. It is also no longer the same string `byod.pair` returns as `bridge_version`.
 
 ### Fixed
 - `User-Agent` misreported the SDK version. `SDK_VERSION` was left at `1.0.0` through `package.json`'s bumps to `1.1.0` and `1.2.0`, and it is the sole input to the header, so every request from the published package mis-identified its own version to server, proxy and CDN logs. `SDK_VERSION` now tracks `package.json` (`1.2.0`), and `src/version.test.ts` reads the published version off disk and fails the build the next time they disagree.

package/dist/generated/openapi.d.ts

@@ -5897,7 +5897,7 @@ export interface paths {
         };
         /**
          * Get the app/bridge download manifest (public)
-         * @description Per-platform installer URL, advertised bridge version, and availability. Requires no pairing and no auth — use it for setup guides, "add a device" flows, reinstalls, and update prompts. The URLs are the same stable 302-redirect endpoints `POST /v1/byod/pair` returns in `download_urls`, and `version` is the same string it returns as `bridge_version`; both surfaces derive from one builder so they cannot drift.
+         * @description Per-platform installer URL, published version, and availability. Requires no pairing and no auth — use it for setup guides, "add a device" flows, reinstalls, and update prompts. The URLs are the same stable 302-redirect endpoints `POST /v1/byod/pair` returns in `download_urls`, built by one shared builder so they cannot drift. `version` is read from the release feed beside the artifact the redirect resolves to, and is `null` when that feed publishes nothing — never a configured placeholder.
          */
         get: {
             parameters: {
@@ -6935,10 +6935,10 @@ export interface components {
              */
             url: string;
             /**
-             * @description Bridge version this deployment advertises — the same string `POST /v1/byod/pair` returns as `bridge_version`. Compare it against an installed version to offer an update.
-             * @example 2.0.1
+             * @description Version currently published for this platform, read from the release feed that sits beside the artifact `url` resolves to — so the number announced and the file served cannot name different releases. `null` when that feed publishes nothing or cannot be read: render "version not published" rather than a number, because a fabricated version makes a failed install and an uninformed console indistinguishable to whoever is checking. Compare it against an installed version to offer an update.
+             * @example 0.0.211
              */
-            version: string;
+            version: string | null;
             /**
              * @description False when this deployment has no artifact configured for the platform. The entry is still returned, so a consumer can hide the affordance instead of surfacing a link that 404s on click.
              * @example true

package/dist/resources/apps.d.ts

@@ -6,15 +6,22 @@ export type AppDownloadEntry = components['schemas']['AppDownloadEntry'];
 export declare class AppsResource extends BaseResource {
     /**
      * `GET /v1/apps` — the app/bridge download manifest: per-platform installer
-     * URL, the advertised bridge version, and whether this deployment has an
-     * artifact configured for the platform. Public (no auth) and, unlike
+     * URL, the version currently published for that platform, and whether this
+     * deployment has an artifact configured for it. Public (no auth) and, unlike
      * `byod.pair`, requires no pairing in flight — use it for setup guides,
      * "add a device" flows, reinstalls, and update prompts (compare `version`
      * against the version the device reports).
      *
      * The URLs are the same stable redirects `byod.pair` returns in
-     * `download_urls`, and `version` is the same string it returns as
-     * `bridge_version` — both surfaces derive from one builder server-side.
+     * `download_urls` — one builder server-side, so they cannot drift.
+     *
+     * `version` is `string | null`. It is read from the release feed beside the
+     * artifact `url` resolves to, so the number and the file cannot name
+     * different releases, and it is `null` when that feed publishes nothing.
+     * Render the absence ("version not published"); never substitute a number,
+     * and do not treat `null` as an error. It is deliberately NOT the
+     * `bridge_version` string `byod.pair` returns — that field is a separate,
+     * device-facing value (WHA-2538).
      *
      * A platform with `available: false` still appears in the response; hide the
      * affordance rather than offering a link that 404s on click.

package/dist/resources/apps.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"apps.d.ts","sourceRoot":"","sources":["../../src/resources/apps.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,yBAAyB,CAAA;AACzD,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,aAAa,CAAA;AACjD,OAAO,EAAE,YAAY,EAAE,MAAM,WAAW,CAAA;AAExC,MAAM,MAAM,WAAW,GAAG,UAAU,CAAC,SAAS,CAAC,CAAC,qBAAqB,CAAC,CAAA;AACtE,MAAM,MAAM,gBAAgB,GAAG,UAAU,CAAC,SAAS,CAAC,CAAC,kBAAkB,CAAC,CAAA;AAExE,qBAAa,YAAa,SAAQ,YAAY;IAC5C;;;;;;;;;;;;;;OAcG;IACH,QAAQ,CAAC,IAAI,CAAC,EAAE,cAAc,GAAG,OAAO,CAAC,WAAW,CAAC;CAGtD"}
+{"version":3,"file":"apps.d.ts","sourceRoot":"","sources":["../../src/resources/apps.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,yBAAyB,CAAA;AACzD,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,aAAa,CAAA;AACjD,OAAO,EAAE,YAAY,EAAE,MAAM,WAAW,CAAA;AAExC,MAAM,MAAM,WAAW,GAAG,UAAU,CAAC,SAAS,CAAC,CAAC,qBAAqB,CAAC,CAAA;AACtE,MAAM,MAAM,gBAAgB,GAAG,UAAU,CAAC,SAAS,CAAC,CAAC,kBAAkB,CAAC,CAAA;AAExE,qBAAa,YAAa,SAAQ,YAAY;IAC5C;;;;;;;;;;;;;;;;;;;;;OAqBG;IACH,QAAQ,CAAC,IAAI,CAAC,EAAE,cAAc,GAAG,OAAO,CAAC,WAAW,CAAC;CAGtD"}

package/dist/resources/apps.js

@@ -2,15 +2,22 @@ import { BaseResource } from './base.js';
 export class AppsResource extends BaseResource {
     /**
      * `GET /v1/apps` — the app/bridge download manifest: per-platform installer
-     * URL, the advertised bridge version, and whether this deployment has an
-     * artifact configured for the platform. Public (no auth) and, unlike
+     * URL, the version currently published for that platform, and whether this
+     * deployment has an artifact configured for it. Public (no auth) and, unlike
      * `byod.pair`, requires no pairing in flight — use it for setup guides,
      * "add a device" flows, reinstalls, and update prompts (compare `version`
      * against the version the device reports).
      *
      * The URLs are the same stable redirects `byod.pair` returns in
-     * `download_urls`, and `version` is the same string it returns as
-     * `bridge_version` — both surfaces derive from one builder server-side.
+     * `download_urls` — one builder server-side, so they cannot drift.
+     *
+     * `version` is `string | null`. It is read from the release feed beside the
+     * artifact `url` resolves to, so the number and the file cannot name
+     * different releases, and it is `null` when that feed publishes nothing.
+     * Render the absence ("version not published"); never substitute a number,
+     * and do not treat `null` as an error. It is deliberately NOT the
+     * `bridge_version` string `byod.pair` returns — that field is a separate,
+     * device-facing value (WHA-2538).
      *
      * A platform with `available: false` still appears in the response; hide the
      * affordance rather than offering a link that 404s on click.

package/dist/resources/apps.js.map

@@ -1 +1 @@
-{"version":3,"file":"apps.js","sourceRoot":"","sources":["../../src/resources/apps.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,YAAY,EAAE,MAAM,WAAW,CAAA;AAKxC,MAAM,OAAO,YAAa,SAAQ,YAAY;IAC5C;;;;;;;;;;;;;;OAcG;IACH,QAAQ,CAAC,IAAqB;QAC5B,OAAO,IAAI,CAAC,MAAM,CAAC,OAAO,CAAc,KAAK,EAAE,UAAU,EAAE,SAAS,EAAE,IAAI,CAAC,CAAA;IAC7E,CAAC;CACF"}
+{"version":3,"file":"apps.js","sourceRoot":"","sources":["../../src/resources/apps.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,YAAY,EAAE,MAAM,WAAW,CAAA;AAKxC,MAAM,OAAO,YAAa,SAAQ,YAAY;IAC5C;;;;;;;;;;;;;;;;;;;;;OAqBG;IACH,QAAQ,CAAC,IAAqB;QAC5B,OAAO,IAAI,CAAC,MAAM,CAAC,OAAO,CAAc,KAAK,EAAE,UAAU,EAAE,SAAS,EAAE,IAAI,CAAC,CAAA;IAC7E,CAAC;CACF"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@isnap/sdk",
-  "version": "1.3.0-next.34",
+  "version": "1.3.0-next.36",
   "description": "Official TypeScript SDK for the iSnap P2P telephony API",
   "license": "MIT",
   "type": "module",