Releases: centrifugal/centrifuge-dart
v0.14.0
v0.13.0
v0.12.0
v0.11.0
What's Changed
- Update protobuf dependency from
^2.0.0
to^3.0.0
- Update SDK requirement to
'>=2.19.0 <4.0.0'
Full Changelog: v0.10.0...v0.11.0
v0.10.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 getToken
callback resulted in client disconnection with unauthorized reason.
Now returning an empty string from getToken
is a valid scenario which won't result into disconnect on the client side. It's still possible to disconnect client by throwing a special UnauthorizedException
from getToken
function.
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: v0.9.4...v0.10.0
v0.9.4
v0.9.3
What's Changed
- feat: add web support by @robert-virkus in #73
- feat: allow users to run examples by @robert-virkus in #72
New Contributors
- @robert-virkus made their first contribution in #72
Full Changelog: v0.9.2...v0.9.3
v0.9.2
v0.9.1
v0.9.0 - new SDK API
Breaking changes
This release adopts a new iteration of Centrifugal protocol and a new iteration of API. Client now behaves according to the client SDK API specification. The work has been done according to Centrifugo v4 roadmap.
Check out Centrifugo v4 release post that covers the reasoning behind changes.
All the current core features of Centrifugal client protocol are now supported here.
New release only works with Centrifugo >= v4.0.0 and Centrifuge >= 0.25.0. See Centrifugo v4 migration guide for details about the changes in the ecosystem.
Note, that Centrifugo v4 supports clients working over the previous protocol iteration, so you can update Centrifugo to v4 without any changes on the client side (but you need to turn on use_client_protocol_v1_by_default
option in the configuration of Centrifugo, see Centrifugo v4 migration guide for details).