Bump pusher-java-client from 1.8.2 to 2.2.6

[dependabot-preview]

Bumps pusher-java-client from 1.8.2 to 2.2.6.

Release notes

Sourced from pusher-java-client's releases.

2.2.6

Fixed an issue causing a NullPointerException if event data on a Presence channel was malformed or missing

v2.2.5

Fixed an issue with the Java-WebSocket library with android pre-sdk24 devices causing a NoSuchMethod exception

v.2.2.4

• Removed unnecessary code in the TweetNaClFast implementation
• Updated the Java-WebSocket library to 1.5.1 as the current version 1.4.0 has a known critical vulnerablity.

v2.2.3

Fixed LazySodium causing a crash on Android devices by swapping it out for TweetNaCl

v2.2.2

Fixed an issue where some private encrypted messages were not decrypted accurately by swapping our implementation of SecretBoxOpener for one provided by Lazy Sodium

v2.2.1

Changed PusherOptions setForceTLS and isForceTLS to setUseTLS and isUseTLS to align with the other client SDKs.

v.2.2.0

Changed PusherOptions setEncrypted and isEncrypted to setForceTLS and isForceTLS to reduce confusion between this option and private encrypted channels.

v2.1.1

• Fix a case where multiple websocket connections could be opened at once if reconnection was triggered by an activity timeout.

v2.1.0

Add private encrypted channels.

v2.0.2

• Make a no-op state change non-fatal, allowing transitions to/from the same state

v2.0.1

• Forward channel_data returned by the auth endpoint when subscribing to private channels

v2.0.0

• The onEvent handler now gets called with one parameter, called the PusherEvent. This PusherEvent has all the same information available as was available before with the 3 parameters, but now is accessible by calling getChannelName(), getData() or getEventName() on the PusherEvent object you receive. In addition, for presence channel client events, you can now retrieve an authenticated User ID by calling getUserId() on the PusherEvent object. To read more on Authenticated users, see the README or our docs here.
• Update Java sourceCompatibility and targetCompatibility to 1.8.
• Fix an issue where the reconnect logic would not be reset after connect() is called again.
• Depend on org.java-websocket:Java-WebSocket:1.4.0 instead of com.pusher:java-websocket:1.4.1.

Changelog

Sourced from pusher-java-client's changelog.

Version 2.2.6 - 17th March 2021

• Fixed an issue causing a NullPointerException if event data on a Presence channel was malformed or missing

Version 2.2.5 - 11th August 2020

• Fixed an issue with the Java-WebSocket library with android pre-sdk24 devices causing a NoSuchMethod exception

Version 2.2.4 - 3rd August 2020

• Removed unnecessary code in the TweetNaClFast implementation
• Updated the Java-WebSocket library to 1.5.1 as the current version 1.4.0 has a known critical vulnerability.

Version 2.2.3 - 8th July 2020

• Fixed LazySodium causing a crash on Android devices by swapping it out for TweetNaCl

Version 2.2.2 - 6th July 2020

• Fixed an issue where some private encrypted messages were not decrypted accurately by swapping our implementation of SecretBoxOpener for one provided by Lazy Sodium

Version 2.2.1 - 22nd April 2020

• Changed PusherOptions setForceTLS and isForceTLS to setUseTLS and isUseTLS to align with the other client SDKs.

Version 2.2.0 - 22nd April 2020

• Changed PusherOptions setEncrypted and isEncrypted to setForceTLS and isForceTLS to reduce confusion between this option and private encrypted channels.

Version 2.1.1 - 15th April 2020

• Fix a case where multiple websocket connections could be opened at once if reconnection was triggered by an activity timeout.

Version 2.1.0 - 8th April 2020

• Added support for private encrypted channels

Version 2.0.2

• Make a no-op state change non-fatal, allowing transitions to/from the same state

Version 2.0.1

• Forward channel_data returned by the auth endpoint when subscribing to private channels

Version 2.0.0

• The onEvent handler now gets called with one parameter, called the PusherEvent. This PusherEvent has all the same information available as was available before with the 3 parameters, but now is accessible by calling getChannelName(), getData() or getEventName() on the PusherEvent object you receive. In addition, for presence channel client events, you can now retrieve an authenticated User ID by calling getUserId() on the PusherEvent object. To read more on Authenticated users, see the README or our docs here.
• Update Java sourceCompatibility and targetCompatibility to 1.8.
• Fix an issue where the reconnect logic would not be reset after connect() is called again.
• Depend on org.java-websocket:Java-WebSocket:1.4.0 instead of com.pusher:java-websocket:1.4.1.

... (truncated)

Commits

• e02f458 Merge pull request #296 from pusher/release/2.2.6
• 26a8652 Prepare for v2.2.6 release
• 49ce2d9 Merge pull request #290 from pusher/add-error-when-presence-data-missing
• 4030c80 Merge pull request #285 from pusher/dev-android-readme
• 8816840 Add test case for subscription error with malformed presence event data
• 8bb6d12 Return error via SubscriptionListener when presence events are malformed
• 011b7ce remove link to android wrapper
• 93c25bc Release 2.2.5
• 101241f Merge pull request #284 from pusher/dev-fix-set-ssl-parameters-2
• 2b96533 fix bug in encrypted channel where replace doesn't exist on maps
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)