Cent

Latest version: v5.0.0

Safety actively analyzes 630052 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 19

3.2.3

======

No backwards incompatible changes here.

Improvements

* Support Debian bullseye DEB package release, drop Debian jessie, [520](https://github.com/centrifugal/centrifugo/issues/520)

Fixes

* Fix emitting Join message in dynamic server subscribe case (when calling subscribe server API), [centrifugal/centrifuge231](https://github.com/centrifugal/centrifuge/issues/231).

3.2.2

======

No backwards incompatible changes here.

Fixes

* Fix top-level granular subscribe and publish proxies [517](https://github.com/centrifugal/centrifugo/issues/517).

Misc

* This release is built with Go 1.17.11.

3.2.1

======

No backwards incompatible changes here.

Improvements

* Centrifugo now periodically sends anonymous usage information (once in 24 hours). That information is impersonal and does not include sensitive data, passwords, IP addresses, hostnames, etc. Only counters to estimate version and installation size distribution, and feature usage. See implementation in [516](https://github.com/centrifugal/centrifugo/pull/516). Please do not disable usage stats sending without reason. If you depend on Centrifugo – sure you are interested in further project improvements. Usage stats help us understand Centrifugo use cases better, concentrate on widely-used features, and be confident we are moving in the right direction. Developing in the dark is hard, and decisions may be non-optimal. See [docs](https://centrifugal.dev/docs/next/server/configuration#anonymous-usage-stats) for more details.

Misc

* We continue working on Centrifugo v4, look at our [v4 roadmap](https://github.com/centrifugal/centrifugo/issues/500) where the latest updates are shared. BTW Centrifugo v3 already has code to work over new protocol which we aim to make default in v4. It's already possible to try out our own bidirectional emulation layer with HTTP-streaming and Eventsource transports. Don't hesitate reaching out if you depend on Centrifugo and want to understand more what's coming in next major release. We are actively collecting feedback at the moment.
* This release is built with Go 1.17.10.

3.2.0

======

This release **contains backwards incompatible changes in experimental Tarantool engine** (see details below).

Improvements

* Support checking `aud` and `iss` JWT claims [496](https://github.com/centrifugal/centrifugo/pull/496). See more details in docs: [aud](https://centrifugal.dev/docs/server/authentication#aud), [iss](https://centrifugal.dev/docs/server/authentication#iss).
* Channel Publication now has `tags` field (`map[string]string`) – this is a map with arbitrary keys and values which travels with publications. It may help to put some useful info into publication without modifying payload. It can also help to avoid processing payload in some scenarios. Publish and broadcast server APIs got support for setting `tags`. Though supporting this field throughout our ecosystem (for example expose it in all our client SDKs) may take some time. Server API docs for [publish](https://centrifugal.dev/docs/server/server_api#publish) and [broadcast](https://centrifugal.dev/docs/server/server_api#broadcast) commands have been updated.
* Support setting user for Redis ACL-based auth, for Redis itself and for Sentinel. See [in docs](https://centrifugal.dev/docs/server/engines#redis_user).
* Unidirectional transports now return a per-connection generated `session` unique string. This unique string attached to a connection on start, in addition to client ID. It allows controlling unidirectional connections using server API. Previously we suggested using client ID for this – but turns out it's not really a working approach since client ID can be exposed to other users in Publications, presence, join/leave messages. So backend can not distinguish whether user passed its own client ID or not. With `session` which is not shared at all things work in a more secure manner. Server API docs for [subscribe](https://centrifugal.dev/docs/server/server_api#subscribe), [unsubscribe](https://centrifugal.dev/docs/server/server_api#unsubscribe), [disconnect](https://centrifugal.dev/docs/server/server_api#disconnect) and [refresh](https://centrifugal.dev/docs/server/server_api#refresh) commands have been updated.
* Report line and column for JSON config file syntax error – see [497](https://github.com/centrifugal/centrifugo/issues/497)
* Improve performance (less memory allocations) in message broadcast, during WebSocket initial connect and during disconnect.

Breaking changes

* **Breaking change in experimental Tarantool integration**. In Centrifugo v3.2.0 we updated code to work with a new version of [tarantool-centrifuge](https://github.com/centrifugal/tarantool-centrifuge). `tarantool-centrifuge` v0.2.0 has an [updated space schema](https://github.com/centrifugal/tarantool-centrifuge/releases/tag/v0.2.0). This means that Centrifugo v3.2.0 will only work with `tarantool-centrifuge` >= v0.2.0 or [rotor](https://github.com/centrifugal/rotor) >= v0.2.0. We do not provide any migration plan for this update – spaces in Tarantool must be created from scratch. We continue considering Tarantool integration experimental.

Misc

* This release is built with Go 1.17.9.
* We continue working on client protocol v2. Centrifugo v3.2.0 includes more parts of it and includes experimental bidirectional emulation support. More details in [515](https://github.com/centrifugal/centrifugo/pull/515).
* Check out our progress regarding Centrifugo v4 in [500](https://github.com/centrifugal/centrifugo/issues/500).
* New community-driven Centrifugo server API library [Centrifugo.AspNetCore](https://github.com/ismkdc/Centrifugo.AspNetCore) for ASP.NET Core released.

3.1.1

======

No backwards incompatible changes here.

Improvements:

* Massive JSON client protocol performance improvements in decoding multiple commands in a single frame. See [215](https://github.com/centrifugal/centrifuge/pull/215) for details.
* General JSON client protocol performance improvements for unmarshalling messages (~8-10% according to [215](https://github.com/centrifugal/centrifuge/pull/215))
* Subscribe proxy can now proxy custom `data` from a client passed in a subscribe command.

This release is built with Go 1.17.4.

3.1.0

======

No backwards incompatible changes here.

Improvements:

* Introducing a [granular proxy mode](https://centrifugal.dev/docs/server/proxy#granular-proxy-mode) for a fine-grained proxy configuration. Some background can be found in [477](https://github.com/centrifugal/centrifugo/issues/477).

Also check out new tutorials in our blog (both examples can be run with single `docker compose up` command):

* [Centrifugo integration with NodeJS tutorial](https://centrifugal.dev/blog/2021/10/18/integrating-with-nodejs)
* [Centrifugo integration with Django – building a basic chat application](https://centrifugal.dev/blog/2021/11/04/integrating-with-django-building-chat-application)

Centrifugo [dashboard for Grafana](https://grafana.com/grafana/dashboards/13039) was updated and now uses [$__rate_interval](https://grafana.com/blog/2020/09/28/new-in-grafana-7.2-__rate_interval-for-prometheus-rate-queries-that-just-work/) function of Grafana.

This release is built with Go 1.17.3.

Page 4 of 19

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.