From b53782011960048c0248d6dbec1dc479caaf2099 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Tue, 13 Oct 2026 02:27:37 +0000 Subject: [PATCH 1/2] Add Web SDK 0.9.0 release notes Co-Authored-By: Brendon Costa --- millicast/changelog/changelog-web-platform.md | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/millicast/changelog/changelog-web-platform.md b/millicast/changelog/changelog-web-platform.md index 06769e00916a..bc56fc32b93b 100644 --- a/millicast/changelog/changelog-web-platform.md +++ b/millicast/changelog/changelog-web-platform.md @@ -6,6 +6,52 @@ Updates to the [JavaScript Web SDK](https://github.com/millicast/millicast-sdk) You can find the full history of previous releases with downloadable assets from the [millicast/millicast-sdk](https://github.com/millicast/millicast-sdk/releases) repository. ::: +## 2026-10-13 | Web SDK [0.9.0](https://github.com/millicast/millicast-sdk/releases/tag/v0.9.0) + +This release includes some minor updates: + +⚡ **Improvements** + +- Added `isConnecting()` to `View` and `Publish` to check whether a `connect()` call is still in progress. +- `stop()` now cancels a `connect()` call that is still in progress. The pending call rejects with an `AbortError`, its connection is closed, and you can call `connect()` again straight away. + +🐛 **Issues** + +- Fixed simulcast publishing on Chrome 154 and later, which sent all three layers at full resolution. +- Fixed a `connect()` call with `metadata: true` that failed leaving its metadata worker running until `stop()`. + +💥 **Breaking Changes** + +- Calling `connect()` on a `View` or `Publish` instance while an earlier `connect()` on the same instance is still in progress now rejects with `Viewer connection already in progress` or `Broadcast connection already in progress`. Previously it opened a second connection. If your application calls `connect()` or `reconnect()` from a `connect()` error handler, make sure it does not treat this rejection as fatal. + +## 2026-09-03 | Web SDK [0.8.1](https://github.com/millicast/millicast-sdk/releases/tag/v0.8.1) + +This release includes some minor updates: + +⚡ **Improvements** + +- Updated stats to v1.3.0. + +🐛 **Issues** + +- Fixed the layout and links of the [API reference](https://millicast.github.io/millicast-sdk/). + +## 2026-09-03 | Web SDK [0.8.0](https://github.com/millicast/millicast-sdk/releases/tag/v0.8.0) + +This release includes some minor updates: + +⚡ **Improvements** + +- Updated dependencies, including `jwt-decode` v4. + +## 2025-10-23 | Web SDK [0.6.1](https://github.com/millicast/millicast-sdk/releases/tag/v0.6.1) + +This release includes some minor updates: + +⚡ **Improvements** + +- `Director.setEndpoint()` now accepts a URL that includes a path. The SDK then uses that URL as is, instead of appending `/api/director/publish` or `/api/director/subscribe`. + ## 2025-09-04 | Web SDK [0.6.0](https://github.com/millicast/millicast-sdk/releases/tag/v0.6.0) This release includes some minor updates: From 918873077f9b365b62b535374295fa5160be9696 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Tue, 13 Oct 2026 02:30:19 +0000 Subject: [PATCH 2/2] Clarify concurrent connect() behavior change Co-Authored-By: Brendon Costa --- millicast/changelog/changelog-web-platform.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/millicast/changelog/changelog-web-platform.md b/millicast/changelog/changelog-web-platform.md index bc56fc32b93b..de3dfa20385e 100644 --- a/millicast/changelog/changelog-web-platform.md +++ b/millicast/changelog/changelog-web-platform.md @@ -22,7 +22,7 @@ This release includes some minor updates: 💥 **Breaking Changes** -- Calling `connect()` on a `View` or `Publish` instance while an earlier `connect()` on the same instance is still in progress now rejects with `Viewer connection already in progress` or `Broadcast connection already in progress`. Previously it opened a second connection. If your application calls `connect()` or `reconnect()` from a `connect()` error handler, make sure it does not treat this rejection as fatal. +- Calling `connect()` on a `View` or `Publish` instance while an earlier `connect()` on the same instance is still in progress now rejects with `Viewer connection already in progress` or `Broadcast connection already in progress`. Previously it opened a second connection, and depending on timing one of the two connections was leaked. This now matches the behavior of an instance that is already connected, which rejects new `connect()` calls until `stop()` is called. If your application calls `connect()` or `reconnect()` from a `connect()` error handler, make sure it does not treat this rejection as fatal. ## 2026-09-03 | Web SDK [0.8.1](https://github.com/millicast/millicast-sdk/releases/tag/v0.8.1)