@assetlib/sdk-expo 0.7.0-preview.1 → 0.7.2-preview.1

package/README.md

@@ -128,7 +128,7 @@ For decorative artwork, set `accessibilityMode="decorative"`; the image is hidde
 
 ## Artwork states in one component
 
-Use a state set for artwork that belongs to a single placement, such as a plant progressing from sprout to full growth. The application chooses the state from its own business logic. Every declared state needs a bundled fallback.
+Use a state set for artwork that belongs to a single placement, such as a plant progressing from sprout to full growth. The application chooses the state from its own business logic; the state names mean nothing to Assetlib. Every declared state needs a bundled fallback. The console publishes the family only when every state has an image at the placement's aspect ratio (pixel sizes may differ), and a release never mixes states from different publications.
 
 ```tsx
 import { AssetlibStateImage, type StateSetRef } from '@assetlib/sdk-expo';
@@ -237,7 +237,7 @@ await client.flush();
 client.dispose(); // Remove the AppState listener and stop observation timers.
 ```
 
-The adapter identifies itself as `sdk-expo` version `0.7.0-preview.1`. An explicit `telemetry.sdk` or `telemetry.build` takes precedence. When the runtime can optionally require `expo-application` or `expo-constants`, the adapter reads native app version and build number (falling back to Expo config version/build). Missing packages, unavailable runtime loaders, and throwing native bridges are ignored; no new dependency is required. Supply `build` explicitly for reliable production attribution, especially with bundlers that cannot resolve optional runtime requires or in Expo Go. Without complete runtime metadata or an explicit build, batches use platform `expo` and version/build `unknown`.
+The adapter identifies itself as `sdk-expo` version `0.7.2-preview.1`. An explicit `telemetry.sdk` or `telemetry.build` takes precedence. When the runtime can optionally require `expo-application` or `expo-constants`, the adapter reads native app version and build number (falling back to Expo config version/build). Missing packages, unavailable runtime loaders, and throwing native bridges are ignored; no new dependency is required. Supply `build` explicitly for reliable production attribution, especially with bundlers that cannot resolve optional runtime requires or in Expo Go. Without complete runtime metadata or an explicit build, batches use platform `expo` and version/build `unknown`.
 
 Only the observation contract fields are sent: environment, SDK name/version, build platform/version/number, random install ID, send time, and coalesced events with placement key, kind/count, source, asset ID/release sequence when known, effective arm/appearance when selected, and fallback reason. Bundle outcomes send only `fallback` events without asset ID or sequence. Dynamic catalog references do not emit observations because they have no placement key. Image bytes, descriptions, URLs, device identifiers, account identifiers, and status/error messages are not included.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@assetlib/sdk-expo",
-  "version": "0.7.0-preview.1",
+  "version": "0.7.2-preview.1",
   "license": "MIT",
   "type": "module",
   "main": "./src/index.tsx",
@@ -20,7 +20,7 @@
     "test": "node --test test/*.test.mjs"
   },
   "dependencies": {
-    "@assetlib/sdk-core": "0.7.0-preview.1"
+    "@assetlib/sdk-core": "0.7.2-preview.1"
   },
   "peerDependencies": {
     "expo": ">=57 <58",

package/src/telemetry.ts

@@ -48,7 +48,7 @@ export function expoTelemetry(telemetry: ClientOptions['telemetry']): ClientOpti
   if (!telemetry?.enabled) return telemetry;
   return {
     ...telemetry,
-    sdk: telemetry.sdk ?? { name: 'sdk-expo', version: '0.7.0-preview.1' },
+    sdk: telemetry.sdk ?? { name: 'sdk-expo', version: '0.7.2-preview.1' },
     build: telemetry.build ?? runtimeBuild() ?? { platform: 'expo', appVersion: 'unknown', buildNumber: 'unknown' },
   };
 }