From 1f5714b3f01b169deaf1cfac56ffdbb6985f53ff Mon Sep 17 00:00:00 2001 From: Thales Macedo Garitezi Date: Mon, 29 May 2023 09:31:30 -0300 Subject: [PATCH] docs: Generate changelog for v5.0.26 --- changes/v5.0.26.en.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/changes/v5.0.26.en.md b/changes/v5.0.26.en.md index c79131bec..54f40eddb 100644 --- a/changes/v5.0.26.en.md +++ b/changes/v5.0.26.en.md @@ -1,4 +1,4 @@ -# +# v5.0.26 ## Enhancements @@ -105,3 +105,14 @@ - [#10817](https://github.com/emqx/emqx/pull/10817) Fix the error of not being able to configure `auto_restart_interval` as infinity - [#10818](https://github.com/emqx/emqx/pull/10818) Fixing `emqx_ctl traces` command. + +- [#10820](https://github.com/emqx/emqx/pull/10820) In case the cluster updated license before the new node join in. The new node will not apply the updated license. + After this change, the new joined node will use the cluster's license key. + + Sometimes the new node must start with a outdated license. + e.g. use emqx-operator deployed and needed to scale up after license expired. + At the time the cluster's license key already updated by API/CLI, but the new node won't use it. + +- [#10833](https://github.com/emqx/emqx/pull/10833) Only include enabled authenticators and authorizers in telemetry report, not all of them. + +- [#10851](https://github.com/emqx/emqx/pull/10851) Obfuscated sensitive data in the bad API logging.