Skip to content

Commit b7400fe

Browse files
michaelklishinmergify[bot]
authored andcommitted
3.13.7 release notes
(cherry picked from commit d5bc5a0) (cherry picked from commit 8abd6a8)
1 parent 52b3843 commit b7400fe

File tree

1 file changed

+160
-0
lines changed

1 file changed

+160
-0
lines changed

release-notes/3.13.7.md

Lines changed: 160 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,160 @@
1+
## RabbitMQ 3.13.7
2+
3+
RabbitMQ `3.13.7` is a maintenance release in the `3.13.x` [release series](https://www.rabbitmq.com/release-information).
4+
5+
This upgrade is **highly recommended** to all users currently on earlier `3.13.x` series and
6+
in particular between `3.13.3` and `3.13.5`, inclusive.
7+
8+
Starting June 1st, 2024, community support for this series will only be provided to [regularly contributing users](https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md) and those
9+
who hold a valid [commercial support license](https://tanzu.vmware.com/rabbitmq/oss).
10+
11+
Please refer to the upgrade section from the [3.13.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.13.0)
12+
if upgrading from a version prior to 3.13.0.
13+
14+
This release requires Erlang 26 and supports Erlang versions up to `26.2.x`.
15+
[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/docs/which-erlang) has more details on
16+
Erlang version requirements for RabbitMQ.
17+
18+
19+
### Minimum Supported Erlang Version
20+
21+
As of 3.13.0, RabbitMQ requires Erlang 26. Nodes **will fail to start** on older Erlang releases.
22+
23+
Users upgrading from 3.12.x (or older releases) on Erlang 25 to 3.13.x on Erlang 26
24+
(both RabbitMQ *and* Erlang are upgraded at the same time) **must** consult
25+
the [v3.12.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.12.0) and [v3.13.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.13.0) first.
26+
27+
28+
## Changes Worth Mentioning
29+
30+
Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://github.com/rabbitmq/rabbitmq-server/tree/v3.13.x/release-notes).
31+
32+
33+
### Core Broker
34+
35+
#### Bug Fixes
36+
37+
* Streams recover better from certain node process failures that may leave behind orphaned segment files
38+
(that is, segment files that do not have a corresponding index file) or index files without a corresponding
39+
segment file.
40+
41+
GitHub issue: [#12073](https://github.com/rabbitmq/rabbitmq-server/pull/12073)
42+
43+
* Classic [peer discovery](https://www.rabbitmq.com/docs/cluster-formation) now logs warnings for certain common user mistakes.
44+
45+
GitHub issues: [#11586](https://github.com/rabbitmq/rabbitmq-server/issues/11586), [#11898](https://github.com/rabbitmq/rabbitmq-server/pull/11898)
46+
47+
* Queue declaration operations now return more useful errors when Khepri is enabled and there's only a minority
48+
of nodes online.
49+
50+
GitHub issues: [#12020](https://github.com/rabbitmq/rabbitmq-server/pull/12020), [#11991](https://github.com/rabbitmq/rabbitmq-server/pull/11991)
51+
52+
* Logging is now more defensive around exception handling. Previously a (very rare) logger exception could
53+
lead to the `amq.rabbitmq.log` handler and exchange to be removed.
54+
55+
Contributed by @gomoripeti.
56+
57+
GitHub issue: [#12107](https://github.com/rabbitmq/rabbitmq-server/pull/12107)
58+
59+
* `rabbitmq-upgrade revive` unintentionally tried to perform operations on replicas that are not local to the node.
60+
This could result in an exceptions some of which were not handled and the command failed.
61+
Re-running the command usually helped.
62+
63+
GitHub issue: [#12038](https://github.com/rabbitmq/rabbitmq-server/pull/12038)
64+
65+
66+
#### Enhancements
67+
68+
* Enabling an experimental feature flag now involves an explicit confirmation.
69+
70+
GitHub issue: [#12059](https://github.com/rabbitmq/rabbitmq-server/pull/12059)
71+
72+
* Khepri projections are registered in a safer manner during node boot.
73+
74+
GitHub issue: [#11837](https://github.com/rabbitmq/rabbitmq-server/pull/11837)
75+
76+
77+
### MQTT
78+
79+
#### Bug Fixes
80+
81+
* Clients that use JWT tokens are now disconnected when their token expires. Previously all newly attempted
82+
operations with an expired token would be rejected but a completely passive connection was not closed.
83+
84+
GitHub issue: [#11869](https://github.com/rabbitmq/rabbitmq-server/pull/11869)
85+
86+
#### Enhancements
87+
88+
* Connection that provide incorrect credentials now closed with a delay, just like for several
89+
other protocols supported by RabbitMQ, as a throttling mechanism.
90+
91+
GitHub issue: [#11906](https://github.com/rabbitmq/rabbitmq-server/pull/11906)
92+
93+
94+
### CLI Tools
95+
96+
#### Bug Fixes
97+
98+
* When the Khepri feature flag is not enabled, `rabbitmq-diagnostics metadata_store_status` will not try to retrieve
99+
and display its status.
100+
101+
GitHub issue: [#12103](https://github.com/rabbitmq/rabbitmq-server/pull/12103)
102+
103+
#### Enhancements
104+
105+
* `rabbitmq-upgrade await_quorum_plus_one` now produces more log messages when the operation times out.
106+
When Khepri is enabled, it now also treats Khepri as a critical Raft-based component that may depend on replica quorum
107+
just like queues and streams do.
108+
109+
GitHub issue: [#12117](https://github.com/rabbitmq/rabbitmq-server/pull/12117)
110+
111+
112+
### Management Plugin
113+
114+
#### Bug Fixes
115+
116+
* When no virtual host limits are set, the limits collection was returned as a JSON array (and not a JSON object)
117+
by `GET /api/vhost-limits`.
118+
119+
GitHub issue: [#12084](https://github.com/rabbitmq/rabbitmq-server/pull/12084)
120+
121+
#### Enhancements
122+
123+
* `GET /api/queues/quorum/{vhost}/{name}/status` is a new endpoint that allows clients to retrieve several key quorum queue
124+
replica and Raft metrics.
125+
126+
Contributed by @SimonUnge.
127+
128+
GitHub issue: [#12072](https://github.com/rabbitmq/rabbitmq-server/pull/12072)
129+
130+
131+
### Shovel Plugin
132+
133+
#### Bug Fixes
134+
135+
* `GET /api/shovels/{vhost}/{name}` now correctly returns a single shovel instead of all shovels in the target
136+
virtual host.
137+
138+
GitHub issue: [#12040](https://github.com/rabbitmq/rabbitmq-server/issues/12040)
139+
140+
141+
### Consistent Hashing Exchange Plugin
142+
143+
#### Bug Fixes
144+
145+
* For an exchange declared with a `hash-header`, publishing failed with an exception when the client (usually unintentionally)
146+
did not set that header.
147+
148+
GitHub issue: [#11808](https://github.com/rabbitmq/rabbitmq-server/pull/11808)
149+
150+
151+
### Dependency Changes
152+
153+
* Osiris was [upgraded to `1.8.3`](https://github.com/rabbitmq/osiris/releases)
154+
* Cuttlefish was [upgraded to `3.4.0`](https://github.com/Kyorai/cuttlefish/releases)
155+
* `observer_cli` was [upgraded to `1.7.5`](https://github.com/zhongwencool/observer_cli/releases)
156+
157+
## Source Code Archives
158+
159+
To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.13.7.tar.xz`
160+
instead of the source tarball produced by GitHub.

0 commit comments

Comments
 (0)