You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* fix(shared-worker): fix rapid subscribe aggregate
Fix the issue because of which rapid subscription (from other PubNub clients in response to
received subscribe response) throttling causes delayed channel list change.
refactor(shared-worker): add output of requests processed by the `SharedWorker`
Modify the `log` payload for `SharedWorker` to make it possible to log sent / received requests
information to the main browser window (not to the SharedWorker console).
* feat(shared-worker): emit heartbeat processing status
Depending on client configuration, it will emit `status` for heartbeat, which has been started by the `SharedWorker` backup heartbeat timer mechanism.
feat(shared-worker): stop `backup` heartbeats on 403
Stop heartbeats until the auth key / access token is changed. On change, `SharedWorker` will send an immediate heartbeat request.
refactor(shared-worker): restart `backup` heartbeat on explicit heartbeat
Restart the timer of the backup heartbeat if an explicit heartbeat request has been received from the main PubNub client.
* fix(subscription-set): fix issue with global subscription set
Fix the issue with the global subscription set (used for legacy interface support) because of which
`unsubscribe` with the legacy interface wasn't able to complete the unsubscribe process.
* refactor(shared-worker): move some logs before request sending
To avoid confusion in the logs reading where the message about sending the request appears earlier
than it should, move the log output before sending the request.
* refactor(shared-worker): announce request sending logs to interested clients
Make sure that more clients will receive log messages about request sending (we're limited to a
single client for heartbeat requests).
refactor(shared-worker): change log message when heartbeat impossible for presence-only channels
Change the misleading console message for heartbeat requests, which are scheduled for
presence-only (`-pnpres`).
* test: subscription/presence behavior with shared-worker (#463)
* added karma configuration for sharedworker tests with headless browser,
added tests with edge cases for subscribe/unsubscribe with sharedworker
* fix: shared worker tests to adapt quick subscription aggregation handling compatible behaviour
* test: shared worker subscription aggregation and isolation in message distribution in scenario where messages arrive in one of the aggregated channel entities
* test(shared-worker): added test for token management, to test token change behaviour in share worker active subscription
* test(shared-worker): added message verification to confirm subscription change, added new test to verify resubscribing to same channel with message reecive check
* test(shared-worker): test cleanup, removed debug logs
* test(shared-worker) confirm auth token changes through middleware generated request url
* test: added test to inspect presence behaviour mimicking tab close activities
---------
Co-authored-by: Mohit Tejani <[email protected]>
* refactor(shared-worker): incorporate server threshold into heartbeat filter
Incorporate a 3-second threshold from the server to the logic that is used to skip heartbeat
requests if it has been sent too soon (because the previous one was not so long ago).
* fix(shared-worker): fix issue which prevented catchup
Fix the condition that, in some cases (burst subscribe from registered clients) incorrectly
identified when the initial subscribe REST API response should be patched with catch timetoken.
* refactor(shared-worker): re-adjust "backup" timer on early heartbeat
Re-adjust "backup" heartbeat timer when one of the clients request sent too early after previous
request.
* PubNub SDK v9.8.0 release.
---------
Co-authored-by: Mohit Tejani <[email protected]>
Co-authored-by: Mohit Tejani <[email protected]>
Co-authored-by: PubNub Release Bot <[email protected]>
Copy file name to clipboardExpand all lines: .pubnub.yml
+18-3Lines changed: 18 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,20 @@
1
1
---
2
2
changelog:
3
+
- date: 2025-07-11
4
+
version: v9.8.0
5
+
changes:
6
+
- type: feature
7
+
text: "Depending on client configuration, it will emit `status` for heartbeat, which has been started by the `SharedWorker` backup heartbeat timer mechanism."
8
+
- type: feature
9
+
text: "Stop heartbeats until the auth key / access token is changed. On change, `SharedWorker` will send an immediate heartbeat request."
10
+
- type: bug
11
+
text: "Fix the issue with the global subscription set (used for legacy interface support) because of which `unsubscribe` with the legacy interface wasn't able to complete the unsubscribe process."
12
+
- type: bug
13
+
text: "Fix the issue because of which rapid subscription (from other PubNub clients in response to received subscribe response) throttling causes delayed channel list change."
14
+
- type: improvement
15
+
text: "Restart the timer of the backup heartbeat if an explicit heartbeat request has been received from the main PubNub client."
16
+
- type: improvement
17
+
text: "Modify the `log` payload for `SharedWorker` to make it possible to log sent / received requests information to the main browser window (not to the `SharedWorker` console)."
Copy file name to clipboardExpand all lines: CHANGELOG.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,18 @@
1
+
## v9.8.0
2
+
July 11 2025
3
+
4
+
#### Added
5
+
- Depending on client configuration, it will emit `status` for heartbeat, which has been started by the `SharedWorker` backup heartbeat timer mechanism.
6
+
- Stop heartbeats until the auth key / access token is changed. On change, `SharedWorker` will send an immediate heartbeat request.
7
+
8
+
#### Fixed
9
+
- Fix the issue with the global subscription set (used for legacy interface support) because of which `unsubscribe` with the legacy interface wasn't able to complete the unsubscribe process.
10
+
- Fix the issue because of which rapid subscription (from other PubNub clients in response to received subscribe response) throttling causes delayed channel list change.
11
+
12
+
#### Modified
13
+
- Restart the timer of the backup heartbeat if an explicit heartbeat request has been received from the main PubNub client.
14
+
- Modify the `log` payload for `SharedWorker` to make it possible to log sent / received requests information to the main browser window (not to the `SharedWorker` console).
0 commit comments