Releases: centrifugal/centrifuge-go
Releases · centrifugal/centrifuge-go
v0.10.3
What's Changed
- Add HTTP Proxy lookup function support by @ax-esuedmeier in #94
- Add test to reproduce panic during Client close by @C-Pro in #95
- Fix nil pointer dereference during Client close, wait inflight callbacks to finish by @FZambia in #96
- Up protocol dependency to v0.13.4 by @FZambia in #97
- Bump google.golang.org/protobuf from 1.30.0 to 1.33.0 by @dependabot in #89
New Contributors
- @dependabot made their first contribution in #89
- @ax-esuedmeier made their first contribution in #94
Full Changelog: v0.10.2...v0.10.3
Contributors
FZambia, C-Pro, and 2 other contributors
Assets 2
v0.10.2
v0.10.1
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 Config.GetToken callback resulted in client disconnection with unauthorized reason.
Now returning an empty string from Config.GetToken is a valid scenario which won't result into disconnect on the client side. It's still possible to disconnect client by returning a special error ErrUnauthorized from GetToken function.
And we are putting back Client.SetToken method to the SDK – so it's now possible to reset the token to be empty upon user logout.
Full Changelog: v0.9.6...v0.10.0
v0.9.6
v0.9.5
What's Changed
- fixing issues with benchmark Tests by @kiran-bjn in #71
- Up protocol, rm unused fields by @FZambia in #77
New Contributors
- @kiran-bjn made their first contribution in #71
Full Changelog: v0.9.4...v0.9.5
Contributors
FZambia and kiran-bjn
Assets 2
v0.9.4
- Fix wrong unsubscribe code handling – see commit. According to spec unsubscribe codes >= 2500 should result into resubscribe from the SDK side,
centrifuge-godid not follow this, instead it never resubscribed upon receiving such codes from the server. Thus message recovery and automatic resubscribe did not work correctly.