0.4.1

What's Changed

• Add access to publication info field by @oleg-smith in #72

New Contributors

• @oleg-smith made their first contribution in #72

Full Changelog: 0.4.0...0.4.1

0.4.0

What's Changed

• Replace cfuture with minifuture by @vyndor in #70
• Add HTTP response code to ErrorEvent by @vyndor in #69

New Contributors

• @vyndor made their first contribution in #70

Full Changelog: 0.3.1...0.4.0

0.3.1

What's Changed

• Handle closed executor in WebSocket callbacks by @FZambia in #71

Full Changelog: 0.3.0...0.3.1

0.3.0

What's Changed

Breaking change! This release changes the semantics of working with connection tokens described in Centrifugo v5 release post.

Previously, returning an empty token string from ConnectionTokenGetter callback resulted in client disconnection with unauthorized reason.

Now returning an empty string from ConnectionTokenGetter is a valid scenario which won't result into disconnect on the client side. It's still possible to disconnect client by returning instance of a special UnauthorizedException from ConnectionTokenGetter.

And we are putting back SetToken method to the SDK – so it's now possible to reset the token to be empty upon user logout.

Full Changelog: 0.2.8...0.3.0

0.2.8

• Handle disconnect push. This is not used at the moment - but is an enabler for the future development.

0.2.7

What's Changed

• Our errors inherit from Throwable, and now we call super() in their constructors. This allows propagating exception cause, as the result the whole chain of exceptions is visible in error handler. #58
• Disconnect gracefully from WebSocket, instead of calling ws.cancel(). By @PhilipDukhov in #56

Full Changelog: 0.2.6...0.2.7

0.2.6

What's Changed

• Fix unsubscribe API – it used legacy format of the command sent to the server
• Add overloaded newSubscription with SubscriptionOptions support. This allows setting Subscription options upon creation - such as subscription token, SubscriptionTokenGetter, and so on. See #53 by @PhilipDukhov
• Diffirentiate bad protocol disconnects for better understanding where those came from. See #50
• If token expires but ConnectionTokenGetter not set – then we issue unauthorized disconnect instead of bad protocol disconnect, and send ConfigurationException to connection onError handler.

New Contributors

• @PhilipDukhov made their first contribution in #53

Full Changelog: 0.2.5...0.2.6

0.2.5

• Include consumer proguard rules #47 - this should provide ProGuard rules automatically when using centrifuge-java thus users of the library should not add rules manually in the application.
• API compatibility check on CI #46

0.2.4

• Add ability to set custom DNS resolver for connecting to server #40

Also, several internal improvements (thanks to @ntoskrnl):

• Use protobuf gradle plugin to generate Protocol.java #41
• Refactor publishing to Maven Central #43
• GitHub Actions for CI/CD: test and release #45

0.2.3

• Fix reconnect after onFailure #39
• Avoid duplicate connecting event, better Exception msg if tokenGetter not set. Commit.
• Fixes in example