@spatius/avatarkit 1.3.5-beta.1 → 1.3.6

package/CHANGELOG.md

@@ -5,6 +5,20 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.3.6] - 2026-08-15
+
+### Fixed
+- **Fixed the SDK continuing to send audio under an already-finished conversation id in direct mode.** After `send(audio, end=true)`, feeding new audio while that round had not started playing yet reused the same conversation id on the wire, so the driving service received new audio on a request it had already been told was over. A new round now always starts under a fresh id, whether or not the previous one had begun playing. Host mode never produced the symptom (it owns the id and has no uplink) but shared the same flaw internally and is aligned.
+- Internal telemetry only, no change to public API or runtime behaviour: the connection identifier is now attached automatically to the SDK's diagnostic events and traces. It previously had to be passed by hand at each call site and reached only two of the event types, which made it impractical to line up client-side events with the driving service's own records for the same session.
+- Internal telemetry only, no change to public API or runtime behaviour: widened the duration buckets for template and asset downloads. The previous ceilings sat well below what a cold start on a large template actually takes, so the slow tail — the part worth measuring — collapsed into a single overflow bucket and 11 seconds could not be told apart from 90.
+
+## [1.3.5] - 2026-08-12
+
+### Fixed
+- **`initialize` no longer fails with `Cannot destructure property 'AvatarDownloader'` in production builds.** The SDK loaded several of its own modules dynamically, which the bundler compiled into a form that only resolves while those modules stay in separate chunks. Whether they do is decided by the *consuming* application's bundler, which merges them once a project grows past a certain size — so the same SDK build worked in development and in small projects, then broke on `vite build` in larger ones. Affects 1.3.1 through 1.3.5-beta.1; upgrading is the fix, no integration changes are needed.
+- Internal telemetry only, no change to public API or runtime behaviour: the avatar-loading and connection timings the SDK reports are now sent for failed attempts as well, each tagged with what went wrong. They were previously only sent on success, so the data could not tell a healthy integration apart from one where every load was failing. HTTP status codes alone could not fill the gap — a request that returns 200 and then fails to parse, or a WebSocket that is refused after the handshake, has no failing status code to report.
+- Internal telemetry only, no change to public API or runtime behaviour: motion data received in host mode now continues the trace started upstream, so one round of playback reads as a single trace end to end instead of two unrelated ones.
+
 ## [1.3.4] - 2026-08-11
 
 ### Fixed