data/configs/cluster-override.conf is cleared to 0KB if hocon_pp:do/2 failed commits/71f64251gen_tcp:connect/2, so
if it's a HTTPs server, we didn't check if TLS handshake was successful.
commits/6b45d2eacreated_at field of rules is missing after emqx restarts. commits/5fc09e6bemqx_schema. #8458sentinel field should be required when AuthN/AuthZ Redis using sentinel mode. #8458chars_limit is not working when formatter is json. #8518cert_subject and cert_common_name placeholder rendering failure. #8531[RuleObj1,RuleObj2], after updating, it will become
{"data": [RuleObj1,RuleObj2], "meta":{"count":2, "limit":100, "page":1},
which will carry the paging meta information./configs/listeners API, use /listeners/ instead. #8485X-Forwarded-For and X-Forwarded-Port #8415cluster_singleton from MQTT bridge config document. This config is no longer applicable in 5.0 #8407emqx/emqx:latest docker image publish to use the Erlang flavor, but not Elixir flavor #8414exp field in JWT auth to be optional rather than required to fix backwards compatability with 4.X releases. #8425Announcement: EMQX team has decided to stop supporting relup for opensource edition. Going forward, it will be an enterprise-only feature.
Main reason: relup requires carefully crafted upgrade instructions from ALL previous versions.
For example, 4.3 is now at 4.3.16, we have 4.3.0->4.3.16, 4.3.1->4.3.16, ... 16 such upgrade paths in total to maintain.
This had been the biggest obstacle for EMQX team to act agile enough in delivering enhancements and fixes.
bin/emqx which affects MacOs release when trying to enable Erlang distribution over TLS #83985.0.1 is built on Erlang/OTP 24.2.1-1. Same as 5.0.0.
5.0.0 (like 4.4.x) had Erlang/OTP version number in the package name. This is because we wanted to release different flavor packages (on different Elixir/Erlang/OTP platforms).
However the long package names also causes confusion, as users may not know which to choose if there were more than one presented at the same time.
Going forward, (starting from 5.0.1), packages will be released in both default (short) and flavored (long) package names.
For example: emqx-5.0.1-otp24.2.1-1-ubuntu20.04-amd64.tar.gz,
but only the default one is presented to the users: emqx-5.0.1-ubuntu20.04-amd64.tar.gz.
In case anyone wants to try a different flavor package, it can be downlowded from the public s3 bucket, for example: https://s3.us-west-2.amazonaws.com/packages.emqx/emqx-ce/v5.0.1/emqx-5.0.1-otp24.2.1-1-ubuntu20.04-arm64.tar.gz
Exceptions:
emqx-5.0.1-elixir1.13.4-otp24.2.1-1-ubuntu20.04-amd64.tar.gzcluster-override.conf from the clustered node which has the greatest tnxid. #8333client.subscribe hookpoint callback result. #8304 #8347packets.connack.auth_error is inaccurate when the client uses a protocol version below MQTT v5.0 to access #8178etc dir.