Log Message:
rabbitmq: updated to 3.9.14

RabbitMQ 3.9.14

Changes Worth Mentioning

Core Server

Bug Fixes

Restart of a node that hosted one or more stream leaders resulted in
their consumers not "re-attaching" to the newly elected leader.

Large fanouts experienced a performance regression when streams were not
enabled using a feature flag.

Stream management plugin did not support mixed version clusters.

Stream deletion did not result in a basic.cancel being sent to AMQP 0-9-1 consumers.

Stream clients did not receive a correct stream unavailability error in some
cases.

It is again possible to clear user tags and update the password in a single \ 
operation.

Enhancements

Forward compatibility with Erlang 25.

File handle cache efficiency improvements.

Uknown stream properties (e.g. those requested by a node that runs a newer version)
are now handled gracefully.

Temporary hostname resolution issues (attempts that fail with nxdomain)
are now handled more gracefully and with a delay of several seconds.

Build time compatibility with Elixir 1.13.

OAuth 2 AuthN/AuthZ Backend Plugin

Bug Fixes

auth_oauth2.additional_scopes_key in rabbitmq.conf was not converted correctly
during configuration translation and thus had no effect.

LDAP AuthN/AuthZ Backend Plugin

Enhancement

Adapt to a breaking Erlang 24.3 LDAP client change.

Shovel Plugin

Enhacements

Shovels now can be declared with delete-after parameter set to 0.
Such shovels will immediately stop instead of erroring and failing to
start after a node restart.

Consul Peer Discovery Plugin

Enhancements

Support for Consul 1.1 response code changes
when an operation is attempted on a non-existent health check.