docs: Generate changelog for v5.0.26
This commit is contained in:
parent
79f6861499
commit
1f5714b3f0
|
@ -1,4 +1,4 @@
|
|||
# <VSN-TAG>
|
||||
# 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.
|
||||
|
|
Loading…
Reference in New Issue