v3.0.0-beta.2

Second beta release of Centrifugo v3.

Documentation site for Centrifugo v3: https://centrifugal.dev

Migration guide draft

v2.8.6

No backwards incompatible changes here.

Improvements:

• RPM and DEB packages now additionally added to release assets

Fixes:

• Fixes accidentally pushed Docker latest tag from Centrifugo v3 PRO beta.

Centrifugo v2.8.6 based on latest Go 1.16.6

Docker images

• docker pull centrifugo/centrifugo:v2.8.6
• docker pull centrifugo/centrifugo:v2
• docker pull centrifugo/centrifugo:v2.8

v3.0.0-beta.1

First beta release of Centrifugo v3. First release details will be shared during a community meeting (join https://t.me/joinchat/ABFVWBE0AhkyyhREoaboXQ)

v2.8.5

No backwards incompatible changes here.

Improvements:

• Possibility to modify data in publish proxy – see #439 and updated docs for publish proxy

Fixes:

• Use default timeouts for subscribe and publish proxy (1 second). Previously these proxy had no default timeout at all.

Centrifugo v2.8.5 based on Go 1.16.4

Docker images

• docker pull centrifugo/centrifugo:v2.8.5
• docker pull centrifugo/centrifugo:v2
• docker pull centrifugo/centrifugo:v2.8
• docker pull centrifugo/centrifugo:latest

v2.8.4

No backwards incompatible changes here.

Improvements:

• New subcommand serve to quickly run a static file server

Fixes:

• Fix panic when using connect proxy with a personal channel feature on. See #436

Centrifugo v2.8.4 based on Go 1.16.3

Docker images

• docker pull centrifugo/centrifugo:v2.8.4
• docker pull centrifugo/centrifugo:v2
• docker pull centrifugo/centrifugo:v2.8
• docker pull centrifugo/centrifugo:latest

v2.8.3

Security warning: take a closer look at new option allowed_origins if you are using connect proxy feature.

No backwards incompatible changes here.

Improvements:

• Possibility to set allowed_origins option (#431). This option allows setting an array of allowed origin patterns (array of strings) for WebSocket and SockJS endpoints to prevent Cross site request forgery attack. This can be especially important when using connect proxy feature. If you are using JWT authentication then you should be safe. Note, that since you get an origin header as part of proxy request from Centrifugo it's possible to check allowed origins without upgrading to Centrifugo v2.8.3. See docs for more details about this new option
• Multi-arch Docker build support - at the moment for linux/amd64 and linux/arm64. See #433

Centrifugo v2.8.3 based on latest Go 1.16.2, Centrifugo does not vendor its dependencies anymore.

Docker images

• docker pull centrifugo/centrifugo:v2.8.3
• docker pull centrifugo/centrifugo:v2
• docker pull centrifugo/centrifugo:v2.8
• docker pull centrifugo/centrifugo:latest

v2.8.2

No backwards incompatible changes here.

Improvements:

• JSON Web Key support - see pull request #410 and description in docs
• Support ECDSA algorithm for verifying JWT - see pull request #420 and updated authentication docs chapter
• Various documentation clarifications - did you know that you can use subscribe proxy instead of private channels for example?

Fixes:

• Use more strict file permissions for a log file created (when using log_file option): 0666 -> 0644
• Fix issue with opening admin web UI menu on small screens

Other:

• Centrifugo repo migrated from Travis CI to GH actions, golangci-lint now works in CI
• Check out a new community package for Laravel that works with the latest version of framework
• Look at the introductory post about Centrifuge library for Go language in our blog (which is Centrifugo server built on top of)

Docker images

• docker pull centrifugo/centrifugo:v2.8.2
• docker pull centrifugo/centrifugo:v2
• docker pull centrifugo/centrifugo:v2.8
• docker pull centrifugo/centrifugo:latest

v2.8.1

No backwards incompatible changes here.

Fixes:

• fix concurrent map access which could result in runtime crash when using presence feature.

Docker images

• docker pull centrifugo/centrifugo:v2.8.1
• docker pull centrifugo/centrifugo:v2
• docker pull centrifugo/centrifugo:v2.8
• docker pull centrifugo/centrifugo:latest

v2.8.0

Minor backwards incompatible changes here when using client_user_connection_limit option – see below.

Centrifugo v2.8.0 has many internal changes that could affect overall performance and latency. In general, we expect better latency between a client and a server, but servers under heavy load can notice a small regression in CPU usage.

Improvements:

• Centrifugo can now maintain a single connection from a user when personal server-side channel used. See #396 and docs
• New option client_concurrency. This option allows processing client commands concurrently. Depending on your use case this option has potential to radically reduce latency between a client and Centrifugo. See detailed description in docs
• When using client_user_connection_limit and user reaches max amount of connections Centrifugo will now disconnect client with connection limit reason instead of returning limit exceeded error. Centrifugo will give a client advice to not reconnect.

Centrifugo v2.8.0 based on latest Go 1.15.5

Docker images

• docker pull centrifugo/centrifugo:v2.8.0
• docker pull centrifugo/centrifugo:v2
• docker pull centrifugo/centrifugo:v2.8
• docker pull centrifugo/centrifugo:latest

v2.7.2

No backwards incompatible changes here.

Fixes:

• Fix client reconnects due to InsufficientState errors. There were two scenarios when this could happen. The first one is using Redis engine with seq/gen legacy fields (i.e. not using v3_use_offset option). The second when publishing a lot of messages in parallel with Memory engine. Both scenarios should be fixed now.
• Fix non-working SockJS transport close with custom disconnect code: this is a regression introduced by v2.6.2

Docker images

• docker pull centrifugo/centrifugo:v2.7.2
• docker pull centrifugo/centrifugo:v2
• docker pull centrifugo/centrifugo:v2.7
• docker pull centrifugo/centrifugo:latest