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.

Log message:
rabbitmq: updated to 3.9.13

RabbitMQ 3.9.13

Core Server

Bug Fixes

Disk space monitor now correctly parses output on (at least some) systems where \ 
non-ASCII characters are used in paths.

Stream leader election is now deterministic when cluster is undergoing a rolling \ 
upgrade.

Enhancements

Queue and binding definition import can be delayed until a moment
when at least N nodes (e.g. three) have joined the cluster. This way imported \ 
quorum queues will have a desired
number of replicas from the start.

Log message:
rabbitmq: updated to 3.9.12

3.9.12

Core Server

Bug Fixes

Work around a slow Windows-specific memory leak in Erlang's file:read_file/1.
log.file.rotation.date pattern parser now supports more values and is closer to \ 
Lager in RabbitMQ 3.7 and earlier releases.
User limits were ignored by definition import.
Stream coordinator could run into an exception in some scenarios.
On node shutdown, stopped applications were unintentionally logged at the error \ 
level.

Enhancements

basic.* AMQP 0-9-1 operations now consume fewer CPU cycles.
More efficient (up to 67% more) user addition and updates, including during \ 
definition import.
Authentiication and authorization backend exceptions could potentially leak \ 
user-provided credentials to node log.
When a non-existent stream offset is requested, the server will return a more \ 
appropriate error code.
Stream operations that fail due to an unavailable leader now use a separate \ 
error code from the case when the stream does not exist.
Deprecated classic health check is now less resource intensive (but still very \ 
intensive compared to modern alternatives).
Operator and regular policy merging now supports keys that use boolean values. \ 
The operator value overrides the regular policy one.
Free disk space monitoring robustness improvements on Windows.
Unnamed parameters and policies in definition files will now be rejected as invalid.

OAuth 2 Plugin

Enhancements

HTTPS client and related improvements for JWKS URLs.

Log message:
rabbitmq: updated to 3.9.11

RabbitMQ 3.9.11

Core Server

Bug Fixes

When a TLS-enabled listener failed to stop, it logged all of its settings
which could contain sensitive values.

Enhancements

Quorum queues now store commands for enqueued messages in a more compact format
on disk (some derivative data has been dropped).

queue.declare-ok response to AMQP 0-9-1 clients operating on a stream could \ 
return a ready-for-delivery
message count value that was out of sync with the stream leader replica.

Classic queues now deliver more efficiently on channels that had global QoS changed
during consumer operation.

Prometheus Plugin

Enhancements

New optional metrics provided by the GET /metrics/detailed endpoint. These \ 
metrics are cluster-wide,
and therefore must not be aggregated.

Bug Fixes

A help tip on the policies page was misplaced.

Management Agent Plugin

Enhancements

Disabling the plugin will stop metric collection performed periodically by
queues, streams, connections, et cetera.

Log message:
rabbitmq: updated to 3.9.10

RabbitMQ 3.9.10

Core Server

Bug Fixes

Make stream coordinator more defensive to rapid declaration and deletion cycles

Enhancements

Several inter-node communication listener settings are now exposed to rabbitmq.conf:

# this port range is used by default
distribution.listener.port_range.min = 25675
distribution.listener.port_range.max = 25675
# instead of listening on all interfaces
distribution.listener.interface = 192.168.0.1

OAuth 2 Plugin

Bug Fixes

Signing keys specified in rabbitmq.conf were not translated correctly,
resulting in exceptions during permission checks.

Log message:
rabbitmq: updated to 3.9.9

3.9.9

Core Server

Bug Fixes

Fixed an issue where node monitor could produce a false network partition when
one of the cluster members was restarted

Message store resiliency improvements

Reduced log noise in certain scenarios where a new queue leader is elected

Queue leader rebalancing now logs less

Enhancements

cluster_formation.target_cluster_size_hint is a new configuration setting that \ 
can be used to specify expected initial cluster size.
This can be used by features, plugins or tools that expect a certain minimum \ 
number of clusters nodes
to join during initial cluster formation

Prometheus Plugin

Enhancements

Metric rendering efficiency improvements (mostly latency)

Bug Fixes

TLS-enabled Prometheus endpoint listener port was not correctly stored internally

Management Plugin

Bug Fixes

Persistent message count is now displayed correctly on individual queue pages

Restore compatibility with IE 11

Consistent Hashing Exchange Plugin

Bug Fixes

Corrected deletion of duplicate bindings between an exchange and a queue

Contributed by @FalconerTC

Dependency Upgrades

Ra was upgraded to 2.0.2

Osiris was upgraded to 1.2.3

Log message:
net: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Not committed (merge conflicts...):

net/radsecproxy/distinfo

The following distfiles could not be fetched (fetched conditionally?):

./net/citrix_ica/distinfo citrix_ica-10.6.115659/en.linuxx86.tar.gz
./net/djbdns/distinfo dnscache-1.05-multiple-ip.patch
./net/djbdns/distinfo djbdns-1.05-test28.diff.xz
./net/djbdns/distinfo djbdns-1.05-ignoreip2.patch
./net/djbdns/distinfo djbdns-1.05-multiip.diff
./net/djbdns/distinfo djbdns-cachestats.patch

Log message:
rabbitmq: updated to 3.9.8

3.9.8:

Core Server

Bug Fixes

* When the mandatory flag was used when publishing to classic queues,
  but publisher confirms were not, channels memory usage would grow indefinitely.

* `rabbitmq-diagnostics memory_breakdown` failed to read memory of connection
  reader, writer and channel processes.

* In some environments, Stream replicas advertised IP addresses that could not \ 
be reached by cluster peers
  (eg. IP addresses behind a NAT in a Docker deployment). RabbitMQ node \ 
hostnames are now advertised as well
  so that other peers can resolve them to get an externally visible IP address.

Log message:
net: Remove SHA1 hashes for distfiles

Log message:
rabbitmq: updated to 3.9.7

3.9.7:
All Components

All bytecode is now compiled using the +deterministic compiler flag. This should \ 
eliminate the capture of some irrelevant build environment attributes in \ 
produced artifacts, improve consistency between builds, and reduce the file \ 
level diff between release artifacts.
Core Server

Enhancements

Classic queue shutdown now uses a much higher timeout (up to 10 minutes instead \ 
of 30 seconds).

In environments with many queues (especially mirrored queues) and many consumers \ 
this means that the chance of queue indices rebuilding after node restart is now \ 
substantially lower.
Prometheus Plugin

Enhancements

More configurability for metrics exposed via the Prometheus endpoint.
Shovel Plugin

Bug Fixes

Shovel URIs could be logged with credentials in some scenarios.

3.9.6:
Core Server

Bug Fixes

TLS information delivered in Proxy protocol header is now attached to connection \ 
metrics as if it was provided by a non-proxying client.
max_message_size had a one-off error in the validator.
mirroring_sync_batch_size was incorrectly validated as if it represented batch \ 
size in bytes. It represents batch size in number of messages, so the new \ 
default hard cap is now 1M (a very high number that's impractical)
Stream Plugin

Bug Fixes

Offset parameters were not stored correctly in some cases.
Partitions list order is now stable.
When stream clients close connections abruptly, publisher and consumer metrics \ 
get cleaned up correctly.
Management Plugin

Enhancements

Stream publishers are now listed on the individual stream page.
Counters have been added to the tiles of several sections on detail pages.

3.9.5:
Core Server

Bug Fixes

Virtual host metadata (description, tags) was not imported from definitions.
Reduced unnecessary debug logging from streams.
AWS Peer Discovery Plugin

Enhancements

AWS API calls are now retried multiple times.

Contributed by AWS.
Management Plugin

Enhancements

PUT /api/vhosts/{name} now can update metadata (tags and descriptions) for \ 
existing virtual hosts.

3.9.4:
Core Server

Enhancements

New Prometheus metrics for alarms
Nodes will now use four more environment variables, if set: \ 
RABBITMQ_DEFAULT_USER (overrides default_user in rabbitmq.conf), \ 
RABBITMQ_DEFAULT_PASS (overrides default_pass), RABBITMQ_DEFAULT_VHOST \ 
(overrides default_vhost) and RABBITMQ_ERLANG_COOKIE (sets shared authentication \ 
secret value). These variables are not recommended to be used in production but \ 
can be the only realistic option in some environment, such as service \ 
containers, ECS, and so on. Most users should continue using rabbitmq.conf and a \ 
securely generated local cookie file.
Definitions now can be imported from different sources, including those provided \ 
by plugins. Original local filesystem source is still supported in a \ 
backwards-compatible way.

3.9.3:
Core Server

Bug Fixes

Queues that had messages with per-message TTL in them could fail to recover \ 
their indices after a restart.
JSON logging could fail with an exception when a logged event included \ 
epoch-based timestamp value.
JSON logging now uses integers (as opposed to floats) to represent epoch-based \ 
timestamps

Enhancements

RabbitMQ application no longer reports the stopping event to systemd. This was \ 
counterproductive when the application was stopped but the runtime (Erlang VM) \ 
was kept running, e.g. via rabbitmqctl stop_app or by the pause minority \ 
partition handling strategy.

Now systemd service monitoring will recognize a node as stopped only when the \ 
runtime is stopped, which is usually the behavior operators expect.

3.9.2:
CLI Tools

Bug Fixes

rabbitmq-upgrade drain and rabbitmq-upgrade revive now log warning and info \ 
level instead of alert.
Shovel Plugin

Bug Fixes

Multiple Shovels could be started in some cases involving node restarts of failures.
Federation Plugin

Bug Fixes

Multiple Federation links could be started in some cases involving node restarts \ 
of failures.

3.9.1:
Core Server

Bug Fixes

Clients that used global QoS prefetch (deprecated as of 3.9.0) ran into an \ 
exception when acknowledging deliveries.
Improved resiliency of stream coordinator in certain conditions.
Nodes failed to start when hostname contained non-ASCII (broader Unicode) characters.

CLI Tools

Bug Fixes

rabbitmq-diagnostics stream_status fails with an exception when the --tracking \ 
option was used.
rabbitmq-diagnostics stream_status used an outdated documentation guide link.
RabbitMQ Erlang Client

Bug Fixes

New releases of the client are again published to Hex.pm.
connection_timeout was adjusted to avoid a confusing warning.
Corrected a typo in direct connection net tick time adjustment.

3.9.0:
Streams
Erlang 24 Support
Kubernetes
Logging in JSON