|
1 | | -RabbitMQ `3.10.15` is a maintenance release in the `3.10.x` [release series](https://www.rabbitmq.com/versions.html). |
| 1 | +Due to a release pipeline failure that was not practically |
| 2 | +possible to "retry", RabbitMQ `3.10.15` never shipped. |
2 | 3 |
|
3 | | -This series [**reaches end of general support** on July 31st, 2023](https://rabbitmq.com/versions.html). |
4 | | - |
5 | | -Please refer to the upgrade section from [v3.10.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.10.0) |
6 | | -if upgrading from a version prior to 3.10.0. |
7 | | - |
8 | | -This release **requires Erlang 24.3** and supports Erlang 25. |
9 | | -[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/which-erlang.html) has more details on |
10 | | -Erlang version requirements for RabbitMQ. |
11 | | - |
12 | | - |
13 | | -### Minimum Supported Erlang Version |
14 | | - |
15 | | -Erlang 23 and 24 versions older than 24.3 have reached [end of support](https://www.rabbitmq.com/which-erlang.html). |
16 | | - |
17 | | -This release of RabbitMQ requires Erlang 24.3 or later versions. Nodes **will fail to start** on older Erlang releases. |
18 | | - |
19 | | -Erlang 25 is recommended: it offers much improved performance on ARM64 architectures, [profiling with flame graphs](https://blog.rabbitmq.com/posts/2022/05/flame-graphs/) |
20 | | -across all architectures, and the most recent TLS 1.3 implementation. |
21 | | - |
22 | | - |
23 | | -## Changes Worth Mentioning |
24 | | - |
25 | | -Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://github.com/rabbitmq/rabbitmq-server/tree/v3.10.x/release-notes). |
26 | | - |
27 | | - |
28 | | -### CLI Tools |
29 | | - |
30 | | -#### Features |
31 | | - |
32 | | - * `rabbitmqctl hash_password` is a new command that produces a [hashed value](https://www.rabbitmq.com/passwords.html#computing-password-hash) of the provided password. |
33 | | - |
34 | | - Contributed by @SimonUnge (AWS). |
35 | | - |
36 | | - GitHub issue: [#5957](https://github.com/rabbitmq/rabbitmq-server/issues/5957) |
37 | | - |
38 | | - * `rabbitmq-diagnostics check_port_connectivity` now supports a new optional flag, `--address`, |
39 | | - that makes the check connect to a specific IP address instead of resolving node's hostname. |
40 | | - This is useful when target node is configured to only listen for connections on one interface |
41 | | - but not others: |
42 | | - |
43 | | - ``` shell |
44 | | - rabbitmq-diagnostics check_port_connectivity --address 127.0.0.1 |
45 | | - rabbitmq-diagnostics check_port_connectivity --address "::1" |
46 | | - ``` |
47 | | - |
48 | | - GitHub issue: [#6853](https://github.com/rabbitmq/rabbitmq-server/issues/6853) |
49 | | - |
50 | | - |
51 | | -### Management Plugin |
52 | | - |
53 | | -#### Bug Fixes |
54 | | - |
55 | | - * User filtering combined with pagination in the management UI did not work as expected. |
56 | | - |
57 | | - GitHub issue: [#4908](https://github.com/rabbitmq/rabbitmq-server/issues/4908) |
58 | | - |
59 | | - * Correctly format JSON field value in channel detail API response. |
60 | | - |
61 | | - Contributed @Syuparn. |
62 | | - |
63 | | - GitHub issue: [#2684](https://github.com/rabbitmq/rabbitmq-server/issues/2684) |
64 | | - |
65 | | - |
66 | | -### AMQP 1.0 Plugin |
67 | | - |
68 | | -#### Bug Fixes |
69 | | - |
70 | | - * AMQP 1.0 connection churn resulted in a memory leak. |
71 | | - |
72 | | - GitHub issue: [#6969](https://github.com/rabbitmq/rabbitmq-server/issues/6969) |
73 | | - |
74 | | - |
75 | | -## Dependency Upgrades |
76 | | - |
77 | | -None in this release. |
78 | | - |
79 | | - |
80 | | -## Source Code Archives |
81 | | - |
82 | | -To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.10.15.tar.xz` |
83 | | -instead of the source tarball produced by GitHub. |
| 4 | +Instead, `3.10.16` was released on the same day after the issue had been addressed. |
0 commit comments