Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.7.17.md

RabbitMQ `3.7.17` is a maintenance release. It focuses on bug fixes and upgrades a JavaScript dependency in the management UI to patch three CVEs in that library. Per the new Erlang version support policy in effect starting with January 2019, this release . Make sure a is used before upgrading. explains what package repositories and tools can be used to provision latest patch versions of Erlang `21.3.x` and `22.x`. When upgrading to this release and upgrading Erlang to 21.x or later at the same time, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21 or later, RabbitMQ must be upgraded before Erlang. See upgrade and compatibility notes first if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . `amqqueue` module and the feature flag subsystem were backported from 3.8. This makes it possible for plugin developers to target both `3.7.x` and `3.8.x` release series. Note that this only backports the API. There are no feature flags to enable in `3.7.17`. No 3.8-specific features that must be enabled via feature flags were backported and there are no plans to do it in later `3.7.x` releases. GitHub issue: `rabbitmqctl stop` description had a typo. Contributed by Eugene Pirogov. GitHub issue: Commands that take passwords as arguments now accept them via standard input. GitHub issue: `rabbitmq-diagnostics observer` no longer requires RabbitMQ application to be running on the target node. GitHub issue: jQuery has been upgraded to `3.4.x`. This series addresses a number of known CVEs in the library: , , . GitHub issue: Blank effective policy definitions were formatted as a JSON array instead of an empty object in API responses. GitHub issue: Definition import endpoint no longer reports progress via `102 Processing` responses. They proved to be problematic for some HTTP clients, including `rabbitmqadmin`. GitHub issues: , Leading and trailing white space characters are now highlighted in queue and exchange names to make them easier to spot. Tab characters are highlighted as well, even in the middle of the word. The idea is that those characters are typically used by mistake and should be easier to notice. GitHub issue: It wasn't possible to delete a binding declared with `routing_key` set to `null` (only possible via the HTTP API). Now such bindings can be deleted but this practice is highly discouraged. Future HTTP API versions might refuse to accept `null` values as they are impossible to declare via AMQP 0-9-1. GitHub issue: Shovel restart link conflicted with that in the Federation management plugin. When both were enabled, only one was actually functional. GitHub issue: Shovel URI was misformatted for a period of time after UI refresh happened and before the Shovel was fully initialised and running. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.7.17.tar.xz`.