Cross-tab broadcast no longer discards cached tokens
@clerk/clerk-js@6.22.0
1 feature1 fixThis release1 featureNew capabilities1 fixBug fixesAI-tallied from the release notes
Minor Changes
- Handle expired organization domains on self-serve SSO flow, allowing to trigger a new verification (#9000) by @LauraBeatris
Patch Changes
-
Prevent a cross-tab broadcast failure from evicting a freshly cached session token. Previously, if broadcasting a token update to other tabs threw (for example when the
BroadcastChannelwas racing a close), the token that was just cached got dropped and the nextgetToken()made an unnecessary network request. The broadcast is now isolated so a failure no longer discards a valid cached token. (#8969) by @jacekradko -
Updated dependencies [
19ce04a]:- @clerk/shared@4.22.0
Fetched June 25, 2026
