From cb1c1f1ba180665d37fc7ac3cfdcec528c92b844 Mon Sep 17 00:00:00 2001 From: raviteja83 Date: Thu, 20 Aug 2026 13:04:41 +0530 Subject: [PATCH 1/2] docs: note the version from which sessions are migrated Sessions are only moved for clients on hms-video-store 0.12.17 or newer; the unpublish and republish case applies on every version. Co-Authored-By: Claude Opus 5 (1M context) --- .../set-up-video-conferencing/render-video/overview.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/javascript/v2/how-to-guides/set-up-video-conferencing/render-video/overview.mdx b/docs/javascript/v2/how-to-guides/set-up-video-conferencing/render-video/overview.mdx index 38298e209..3a8f8727a 100644 --- a/docs/javascript/v2/how-to-guides/set-up-video-conferencing/render-video/overview.mdx +++ b/docs/javascript/v2/how-to-guides/set-up-video-conferencing/render-video/overview.mdx @@ -47,6 +47,8 @@ If you attach once to `peer.videoTrack` and never subscribe to changes, the tile Server migration needs no action from your app or your users, so it is the case that gets missed. The only other way `peer.videoTrack` changes is a real unpublish and republish of that peer's video — for example a role change to a role that cannot publish video, and then back to one that can. +A session is only moved for clients on `@100mslive/hms-video-store` 0.12.17 or newer; older clients are left on their current server. The unpublish and republish case applies on every version, so subscribe by peer id whichever version you are on. + Use the `selectVideoTrackByPeerID` selector with `hmsActions.attachVideo` and `hmsActions.detachVideo`: ```js From 4a862e6a893eac7ba31351ef55007d9dff29b5b6 Mon Sep 17 00:00:00 2001 From: raviteja83 Date: Thu, 20 Aug 2026 16:27:12 +0530 Subject: [PATCH 2/2] docs: link the version to the release notes page Co-Authored-By: Claude Opus 5 (1M context) --- .../set-up-video-conferencing/render-video/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/javascript/v2/how-to-guides/set-up-video-conferencing/render-video/overview.mdx b/docs/javascript/v2/how-to-guides/set-up-video-conferencing/render-video/overview.mdx index 3a8f8727a..55cac2046 100644 --- a/docs/javascript/v2/how-to-guides/set-up-video-conferencing/render-video/overview.mdx +++ b/docs/javascript/v2/how-to-guides/set-up-video-conferencing/render-video/overview.mdx @@ -47,7 +47,7 @@ If you attach once to `peer.videoTrack` and never subscribe to changes, the tile Server migration needs no action from your app or your users, so it is the case that gets missed. The only other way `peer.videoTrack` changes is a real unpublish and republish of that peer's video — for example a role change to a role that cannot publish video, and then back to one that can. -A session is only moved for clients on `@100mslive/hms-video-store` 0.12.17 or newer; older clients are left on their current server. The unpublish and republish case applies on every version, so subscribe by peer id whichever version you are on. +A session is only moved for clients on `@100mslive/hms-video-store` [0.12.17](/javascript/v2/release-notes/release-notes) or newer; older clients are left on their current server. The unpublish and republish case applies on every version, so subscribe by peer id whichever version you are on. Use the `selectVideoTrackByPeerID` selector with `hmsActions.attachVideo` and `hmsActions.detachVideo`: