Releases/v8.4.0

[MeenaAlfons]

What does this PR do?

Deploying a release candidate for:

• Expose a way to switch from one cluster/app to the other #773

Checklist

• All new functionality has tests.
• All tests are passing.
• New or changed API methods have been documented.
• npm run format has been run

CHANGELOG

• [Added] Introduce a new .switchCluster method to switch the Pusher client to a different cluster and re-establish all existing subscriptions and channel bindings.
• [FIXED] Persist Initial Pusher Options
• [FIXED] Authorization Custom Handler typing [types] Invalid type definition for channelAuthorization with customHandler #715

[kamalbennani]

Once released, this would of course unblock us, thank you again 🙇

[MeenaAlfons]

@kamalbennani In addition to subscribing to channels and sending messages, the following features may get affected by switchCluster if it is not respecting the protocol. It would be a good idea to test them before using this version in production.

• Private Channels
• Presence Channels
• User Authentication
• Server-to-user messages
• Watchlist Online Status

Happy to help 😊

[kamalbennani]

Do you know if it's failing due to my changes, or those are just flaky tests?

[MeenaAlfons]

I've run the tests locally and found the issue. Now all tests are passing but the make command returns 1 in CI.

Given that all tests are passing, I'm gonna go ahead and release the "release candidate" :)

[MeenaAlfons]

@kamalbennani It's released 🚀

[kamalbennani]

Hi @MeenaAlfons
Thanks for the release! I spotted a small issue where the original Pusher options were ignored once the switchCluster is invoked.
I'm pushing a small PR with tests to cover this use-case.
Sorry!

[kamalbennani]

PR: #783

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you'd like this issue to stay open please leave a comment indicating how this issue is affecting you. Thank you.