chore: Generate changelog for v5.0.18
This commit is contained in:
Zaiming (Stone) Shi
parent
5150407f7b
commit
34a20d9b51
|
|
@ -0,0 +1,44 @@
|
||||||
|
# v5.0.18
|
||||||
|
|
||||||
|
## Enhancements
|
||||||
|
|
||||||
|
- [#10019](https://github.com/emqx/emqx/pull/10019) Add low level tuning settings for QUIC listeners.
|
||||||
|
|
||||||
|
- [#9213](https://github.com/emqx/emqx/pull/9213) Add pod disruption budget to helm chart
|
||||||
|
|
||||||
|
- [#9949](https://github.com/emqx/emqx/pull/9949) QUIC transport Multistreams support and QUIC TLS cacert support.
|
||||||
|
|
||||||
|
|
||||||
|
- [#9967](https://github.com/emqx/emqx/pull/9967) New common TLS option 'hibernate_after' to reduce memory footprint per idle connecion, default: 5s.
|
||||||
|
|
||||||
|
## Bug Fixes
|
||||||
|
|
||||||
|
- [#10009](https://github.com/emqx/emqx/pull/10009) Validate `bytes` param to `GET /trace/:name/log` to not exceed signed 32bit integer.
|
||||||
|
|
||||||
|
- [#10015](https://github.com/emqx/emqx/pull/10015) To prevent errors caused by an incorrect EMQX node cookie provided from an environment variable,
|
||||||
|
we have implemented a fail-fast mechanism.
|
||||||
|
Previously, when an incorrect cookie was provided, the command would still attempt to ping the node,
|
||||||
|
leading to the error message 'Node xxx not responding to pings'.
|
||||||
|
With the new implementation, if a mismatched cookie is detected,
|
||||||
|
a message will be logged to indicate that the cookie is incorrect,
|
||||||
|
and the command will terminate with an error code of 1 without trying to ping the node.
|
||||||
|
|
||||||
|
- [#10020](https://github.com/emqx/emqx/pull/10020) Fix bridge metrics when running in async mode with batching enabled (`batch_size` > 1).
|
||||||
|
|
||||||
|
- [#10021](https://github.com/emqx/emqx/pull/10021) Fix error message when the target node of `emqx_ctl cluster join` command is not running.
|
||||||
|
|
||||||
|
- [#9939](https://github.com/emqx/emqx/pull/9939) Allow 'emqx ctl cluster' command to be issued before Mnesia starts.
|
||||||
|
Prior to this change, EMQX `replicant` could not use `manual` discovery strategy.
|
||||||
|
Now it's possible to join cluster using 'manual' strategy.
|
||||||
|
|
||||||
|
- [#9958](https://github.com/emqx/emqx/pull/9958) Fix bad http response format when client ID is not found in `clients` APIs
|
||||||
|
|
||||||
|
- [#9961](https://github.com/emqx/emqx/pull/9961) Avoid parsing config files for node name and cookie when executing non-boot commands in bin/emqx.
|
||||||
|
|
||||||
|
- [#9974](https://github.com/emqx/emqx/pull/9974) Report memory usage to statsd and prometheus using the same data source as dashboard.
|
||||||
|
Prior to this fix, the memory usage data source was collected from an outdated source which did not work well in containers.
|
||||||
|
|
||||||
|
- [#9978](https://github.com/emqx/emqx/pull/9978) Fixed configuration issue when choosing to use SSL for a Postgres connection (`authn`, `authz` and bridge).
|
||||||
|
The connection could fail to complete with a previously working configuration after an upgrade from 5.0.13 to newer EMQX versions.
|
||||||
|
|
||||||
|
- [#9997](https://github.com/emqx/emqx/pull/9997) Fix Swagger API schema generation. `deprecated` metadata field is now always boolean, as [Swagger specification](https://swagger.io/specification/) suggests.
|
||||||
|
|
@ -0,0 +1,39 @@
|
||||||
|
# v5.0.18
|
||||||
|
|
||||||
|
## 增强
|
||||||
|
|
||||||
|
- [#10019](https://github.com/emqx/emqx/pull/10019) 为 QUIC 侦听器添加更多底层调优选项。
|
||||||
|
|
||||||
|
- [#9213](https://github.com/emqx/emqx/pull/9213) 在舵手图中添加吊舱干扰预算。
|
||||||
|
|
||||||
|
- [#9949](https://github.com/emqx/emqx/pull/9949) QUIC 传输多流支持和 QUIC TLS cacert 支持。
|
||||||
|
|
||||||
|
- [#9967](https://github.com/emqx/emqx/pull/9967) 新的通用 TLS 选项 'hibernate_after'， 以减少空闲连接的内存占用，默认： 5s 。
|
||||||
|
|
||||||
|
## 修复
|
||||||
|
|
||||||
|
- [#10009](https://github.com/emqx/emqx/pull/10009) 验证 `GET /trace/:name/log` 的 `bytes` 参数，使其不超过有符号的32位整数。
|
||||||
|
|
||||||
|
- [#10015](https://github.com/emqx/emqx/pull/10015) 在 cookie 给错时，快速失败。
|
||||||
|
在此修复前，即使 cookie 配置错误，emqx 命令仍然会尝试去 ping EMQX 节点，
|
||||||
|
并得到一个 "Node xxx not responding to pings" 的错误。
|
||||||
|
修复后，如果发现 cookie 不一致，立即打印不一致的错误信息并退出。
|
||||||
|
|
||||||
|
- [#10020](https://github.com/emqx/emqx/pull/10020) 修复使用异步和批量配置的桥接计数不准确的问题。
|
||||||
|
|
||||||
|
- [#10021](https://github.com/emqx/emqx/pull/10021) 修正当`emqx_ctl cluster join`命令的目标节点未运行时的错误信息。
|
||||||
|
|
||||||
|
- [#9939](https://github.com/emqx/emqx/pull/9939) 允许 'emqx ctl cluster join' 命令在 Mnesia 启动前就可以调用。
|
||||||
|
在此修复前， EMQX 的 `replicant` 类型节点无法使用 `manual` 集群发现策略。
|
||||||
|
|
||||||
|
- [#9958](https://github.com/emqx/emqx/pull/9958) 修复 `clients` API 在 Client ID 不存在时返回的错误的 HTTP 应答格式。
|
||||||
|
|
||||||
|
- [#9961](https://github.com/emqx/emqx/pull/9961) 在 bin/emqx 脚本中，避免在运行非启动命令时解析 emqx.conf 来获取节点名称和 cookie。
|
||||||
|
|
||||||
|
- [#9974](https://github.com/emqx/emqx/pull/9974) Statsd 和 prometheus 使用跟 Dashboard 相同的内存用量数据源。
|
||||||
|
在此修复前，内存的总量和用量统计使用了过时的（在容器环境中不准确）的数据源。
|
||||||
|
|
||||||
|
- [#9978](https://github.com/emqx/emqx/pull/9978) 修正了在Postgres连接中选择使用SSL时的配置问题（`authn`, `authz` 和 bridge）。
|
||||||
|
从5.0.13升级到较新的EMQX版本后，连接可能无法完成之前的配置。
|
||||||
|
|
||||||
|
- [#9997](https://github.com/emqx/emqx/pull/9997) 修复 Swagger API 生成时，`deprecated` 元数据字段未按照[标准](https://swagger.io/specification/)建议的那样始终为布尔值的问题。
|
||||||
Loading…
Reference in New Issue