Skip to content

v5.3.0
Compare
Choose a tag to compare
@FZambia FZambia released this 16 Mar 07:58
· 65 commits to master since this release
v5.3.0
57906c1
This commit was signed with the committer’s verified signature.
FZambia Alexander Emelin
GPG key ID: 740BB5E993015FA3
Learn about vigilant mode.

Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.

Centrifugo is language-agnostic and can be used to build chat apps, live comments, multiplayer games, real-time data visualizations, collaborative tools, etc. in combination with any backend. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.

Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.

For details, go to the Centrifugo documentation site.

What's changed

This release adds validation of proper history_ttl and history_meta_ttl configuration. Adding validation means possible errors on Centrifugo start if you have improperly configured history meta TTL expiration. See more details below.

Improvements

  • Better error message for invalid connection token with channel claim, see #776
  • Improvements in Grand Chat Tutorial source code: we now run Django migrations automatically, also long initial connection to PostgreSQL was fixed. So the example is now simpler and smoother to experiment with. If you still have not read our tutorial - just do it 🤓

Fixes

  • ❗Add validation on Centrifugo start for history_meta_ttl option to be greater than or equal to history_ttl option. Without this validation your history streams may eventually return error The ID specified in XADD is equal or smaller than the target stream top item during publish operation. See #768 for the details. This change won't affect you if you don't have history_ttl more than 30 days. Also, documentation about history_meta_ttl option was fixed since it contained different default values in different parts of the doc (the default changed in v5 together with history meta ttl refactoring, but the doc was not properly updated).
  • When using in-memory broker (default) history meta TTL was not properly inherited from channel namespace configuration – the global one was used instead. Fixed in centrifugal/centrifuge#366
  • Web UI: redirect to the login screen in case of unauthorized errors from server, this fixes a regression introduced by Centrifugo v5.2.1
  • Fix setting custom TTL in gensubtoken cli, see #769

Misc

  • Release is built with Go 1.22.1
  • All dependencies were updated to latest versions
  • Built-in integration with Heroku was removed #779
  • ❗If you use SockJS – pay attention to #765 – in Centrifugo v6 SockJS support will be removed
Assets 15
Loading