|
| 1 | +RabbitMQ `3.11.27` is a maintenance release in the `3.11.x` [release series](https://www.rabbitmq.com/versions.html). |
| 2 | +This release series [goes out of community support on Dec 31, 2023](https://rabbitmq.com/versions.html). |
| 3 | + |
| 4 | +Please refer to the upgrade section from [v3.11.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.11.0) |
| 5 | +if upgrading from a version prior to 3.11.0. |
| 6 | + |
| 7 | +This release requires Erlang 25 and supports Erlang versions up to `25.3.x`. |
| 8 | +[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/which-erlang.html) has more details on |
| 9 | +Erlang version requirements for RabbitMQ. |
| 10 | + |
| 11 | + |
| 12 | +### Minimum Supported Erlang Version |
| 13 | + |
| 14 | +As of 3.11.0, RabbitMQ requires Erlang 25. Nodes **will fail to start** on older Erlang releases. |
| 15 | + |
| 16 | +Erlang 25 as our new baseline means much improved performance on ARM64 architectures, [profiling with flame graphs](https://blog.rabbitmq.com/posts/2022/05/flame-graphs/) |
| 17 | +across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. |
| 18 | + |
| 19 | + |
| 20 | +## Changes Worth Mentioning |
| 21 | + |
| 22 | +Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://github.com/rabbitmq/rabbitmq-server/tree/v3.11.x/release-notes). |
| 23 | + |
| 24 | + |
| 25 | +### Core Broker |
| 26 | + |
| 27 | +#### Bug Fixes |
| 28 | + |
| 29 | + * Avoids a rare exception that could stop TCP socket writes on a client connection. |
| 30 | + |
| 31 | + GitHub issues: [#9991](https://github.com/rabbitmq/rabbitmq-server/issues/9991), [#9803](https://github.com/rabbitmq/rabbitmq-server/discussions/9803) |
| 32 | + |
| 33 | +#### Enhancements |
| 34 | + |
| 35 | + * Definition files that are virtual host-specific cannot be imported on boot. Such files will now be |
| 36 | + detected early and the import process will terminate after logging a more informative message. |
| 37 | + |
| 38 | + Previous the import process would run into an obscure exception. |
| 39 | + |
| 40 | + GitHub issues: [#10068](https://github.com/rabbitmq/rabbitmq-server/issues/10068), [#10086](https://github.com/rabbitmq/rabbitmq-server/pull/10086) |
| 41 | + |
| 42 | + |
| 43 | +### Shovel Plugin |
| 44 | + |
| 45 | +#### Bug Fixes |
| 46 | + |
| 47 | + * Avoids two Shovels being started after an upgrade from `3.11.25` or older versions. |
| 48 | + |
| 49 | + Two Shovels running concurrently would still transfer messages but because they act as |
| 50 | + competing consumers (and publishers), this affected message ordering in the target queue. |
| 51 | + |
| 52 | + Contributed by @gomoripeti (CloudAMQP). |
| 53 | + |
| 54 | + GitHub issues: [#9965](https://github.com/rabbitmq/rabbitmq-server/pull/9965), [#10080](https://github.com/rabbitmq/rabbitmq-server/pull/10080) |
| 55 | + |
| 56 | + |
| 57 | +### Management Plugin |
| 58 | + |
| 59 | +#### Bug Fixes |
| 60 | + |
| 61 | + * `DELETE /api/policies/{vhost}/{policy}` returned a 500 response instead of a 404 one |
| 62 | + when target virtual host did not exist. |
| 63 | + |
| 64 | + GitHub issue: [#9983](https://github.com/rabbitmq/rabbitmq-server/issues/9983) |
| 65 | + |
| 66 | + |
| 67 | +## Dependency Upgrades |
| 68 | + |
| 69 | + None in this release. |
| 70 | + |
| 71 | + |
| 72 | +## Source Code Archives |
| 73 | + |
| 74 | +To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.27.tar.xz` |
| 75 | +instead of the source tarball produced by GitHub. |
0 commit comments