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

Log message:
rabbitmq: updated to 3.8.19

RabbitMQ 3.8.19 is a maintenance release.

Log message:
rabbitmq: updated to 3.8.18

3.8.18:
Bug fixes
Security vulnerability patch for CVE-2021-32719

Log message:
rabbitmq: updated to 3.8.17

RabbitMQ 3.8.17

RabbitMQ 3.8.17 is a maintenance release that includes a security patch.

Security Patches

This release addresses an undisclosed vulnerability with CVSS 3.1 score of 2.4 (low).
This section will be updated when the details are made public.

Log message:
rabbitmq: updated to 3.8.16

RabbitMQ 3.8.16 release

The RabbitMQ team is pleased to announce the release of RabbitMQ 3.8.16.

This is a maintenance release that follows-up to 3.8.15 to reintroduce AWS peer \ 
discovery plugin that was unintentionally excluded. Release notes can be found \ 
in the change log.

This release requires Erlang/OTP 23.2 and is the first release to support Erlang 24.

Binary builds and packages of the new release can be found on GitHub, \ 
Cloudsmith, or Package Cloud. See RabbitMQ installation guides to learn more.

We encourage all users of earlier versions of RabbitMQ to upgrade to this latest \ 
release.

As always, we welcome any questions, bug reports, and other feedback on this \ 
release, as well as general suggestions for features and enhancements in future \ 
releases. Contact us via the rabbitmq-users Google group or RabbitMQ community \ 
Slack.

RabbitMQ 3.8.15 release

The RabbitMQ team is pleased to announce the release of RabbitMQ 3.8.15.

This is a maintenance release that includes two security patches. Release notes \ 
can be found in the change log.

This is the last release to support Erlang/OTP 22.

We encourage all users to consult release notes but skip this release and \ 
upgrade to 3.8.11 or later.

As always, we welcome any questions, bug reports, and other feedback on this \ 
release, as well as general suggestions for features and enhancements in future \ 
releases. Contact us via the rabbitmq-users Google group or RabbitMQ community \ 
Slack.

Log message:
rabbitmq: updated to 3.8.14

RabbitMQ 3.8.14 is a maintenance release that restores
Erlang 22.3 compatibility for environments that use direct reply-to.

Log message:
rabbitmq: updated to 3.8.13

RabbitMQ 3.8.13 is a maintenance release.

Log message:
rabbitmq: updated to 3.8.12

RabbitMQ 3.8.12 is a maintenance release that contains bug fixes.