|
| 1 | +## RabbitMQ 3.13.5 |
| 2 | + |
| 3 | +RabbitMQ `3.13.5` is a maintenance release in the `3.13.x` [release series](https://www.rabbitmq.com/release-information). |
| 4 | +This upgrade is **highly recommended** to all users currently on earlier `3.13.x` series and |
| 5 | +in particular `3.13.4`. |
| 6 | + |
| 7 | +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 |
| 8 | +who hold a valid [commercial support license](https://tanzu.vmware.com/rabbitmq/oss). |
| 9 | + |
| 10 | +Please refer to the upgrade section from the [3.13.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.13.0) |
| 11 | +if upgrading from a version prior to 3.13.0. |
| 12 | + |
| 13 | +This release requires Erlang 26 and supports Erlang versions up to `26.2.x`. |
| 14 | +[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/docs/which-erlang) has more details on |
| 15 | +Erlang version requirements for RabbitMQ. |
| 16 | + |
| 17 | + |
| 18 | +### Minimum Supported Erlang Version |
| 19 | + |
| 20 | +As of 3.13.0, RabbitMQ requires Erlang 26. Nodes **will fail to start** on older Erlang releases. |
| 21 | + |
| 22 | +Users upgrading from 3.12.x (or older releases) on Erlang 25 to 3.13.x on Erlang 26 |
| 23 | +(both RabbitMQ *and* Erlang are upgraded at the same time) **must** consult |
| 24 | +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. |
| 25 | + |
| 26 | + |
| 27 | +## Changes Worth Mentioning |
| 28 | + |
| 29 | +Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://github.com/rabbitmq/rabbitmq-server/tree/v3.13.x/release-notes). |
| 30 | + |
| 31 | + |
| 32 | +### Core Broker |
| 33 | + |
| 34 | +#### Bug Fixes |
| 35 | + |
| 36 | + * Quorum queue replicas could fail to recover in certain scenarios. |
| 37 | + |
| 38 | + GitHub issue: [#11769](https://github.com/rabbitmq/rabbitmq-server/pull/11769) |
| 39 | + |
| 40 | + * Safer AMQP 0-9-1 to AMQP 1.0 (the internal message format) conversion for longer string values. |
| 41 | + |
| 42 | + GitHub issue: [#11737](https://github.com/rabbitmq/rabbitmq-server/pull/11737) |
| 43 | + |
| 44 | + * When a message that contained an `x-deaths` [dead-lettering](https://www.rabbitmq.com/docs/dlx) header was republished "as is" by a client, |
| 45 | + the `time` field in the dead lettering events was not correctly converted for AMQP 0-9-1 clients. |
| 46 | + |
| 47 | + GitHub issue: [#11608](https://github.com/rabbitmq/rabbitmq-server/pull/11608) |
| 48 | + |
| 49 | + * [Direct Reply-to](https://www.rabbitmq.com/docs/direct-reply-to) failed with an exception when firehose tracing was enabled. |
| 50 | + |
| 51 | + GitHub issue: [#11666](https://github.com/rabbitmq/rabbitmq-server/pull/11666) |
| 52 | + |
| 53 | + |
| 54 | +### CLI Tools |
| 55 | + |
| 56 | +#### Bug Fixes |
| 57 | + |
| 58 | + * `rabbitmqctl export_definitions` failed if cluster contained custom federation upstream set definitions. |
| 59 | + |
| 60 | + GitHub issue: [#11612](https://github.com/rabbitmq/rabbitmq-server/issues/11612) |
| 61 | + |
| 62 | + |
| 63 | +### MQTT Plugin |
| 64 | + |
| 65 | +#### Bug Fixes |
| 66 | + |
| 67 | + * An abrupt client TCP connection closure could result in a spike in that connection's memory footprint. |
| 68 | + |
| 69 | + GitHub issue: [#11683](https://github.com/rabbitmq/rabbitmq-server/pull/11683) |
| 70 | + |
| 71 | + |
| 72 | +### Shovel Plugin |
| 73 | + |
| 74 | +#### Enhancements |
| 75 | + |
| 76 | + * Improved AMQP 1.0 to AMQP 0-0-1 conversion for shovels. |
| 77 | + |
| 78 | + Contributed by @luos. |
| 79 | + |
| 80 | + GitHub issue: [#10037](https://github.com/rabbitmq/rabbitmq-server/pull/10037) |
| 81 | + |
| 82 | + |
| 83 | +### etcd Peer Discovery Plugin |
| 84 | + |
| 85 | +#### Bug Fixes |
| 86 | + |
| 87 | + * Nodes now register themselves before running peer discovery, reducing the probability of |
| 88 | + first (usually) two nodes to boot potentially forming two initial clusters. |
| 89 | + |
| 90 | + GitHub issues: [#11647](https://github.com/rabbitmq/rabbitmq-server/pull/11647), [#11646](https://github.com/rabbitmq/rabbitmq-server/pull/11646) |
| 91 | + |
| 92 | + |
| 93 | +### Consul Peer Discovery Plugin |
| 94 | + |
| 95 | +#### Bug Fixes |
| 96 | + |
| 97 | + * Nodes now register themselves before running peer discovery, reducing the probability of |
| 98 | + first (usually) two nodes to boot potentially forming two initial clusters. |
| 99 | + |
| 100 | + GitHub issues: [#11647](https://github.com/rabbitmq/rabbitmq-server/pull/11647), [#11646](https://github.com/rabbitmq/rabbitmq-server/pull/11646) |
| 101 | + |
| 102 | + |
| 103 | +### AWS Peer Discovery Plugin |
| 104 | + |
| 105 | +#### Enhancements |
| 106 | + |
| 107 | + * Forward compatibility: handle AWS API responses that use empty HTTP response bodies. |
| 108 | + |
| 109 | + Contributed by @SimonUnge. |
| 110 | + |
| 111 | + GitHub issue: [#11722](https://github.com/rabbitmq/rabbitmq-server/pull/11722) |
| 112 | + |
| 113 | + |
| 114 | + |
| 115 | +### Dependency Changes |
| 116 | + |
| 117 | + * Ra was [upgraded to `2.13.3`](https://github.com/rabbitmq/ra/releases) |
| 118 | + |
| 119 | +## Source Code Archives |
| 120 | + |
| 121 | +To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.13.5.tar.xz` |
| 122 | +instead of the source tarball produced by GitHub. |
0 commit comments