Log message:
rabbitmq: updated to 3.11.13

RabbitMQ 3.11.13

Core Server

Bug Fixes

3.11.12 introduced a regression that caused client connections to fail with an \ 
exception
when TCP or TLS listeners were bould to a particular interface.

RabbitMQ 3.11.12

Core Server

Bug Fixes

Boot time import of definitions from a conf.d-style directory failed unless
definitions.skip_if_unchanged was set to true, for example, like in this
rabbitmq.conf:

definitions.skip_if_unchanged = false
definitions.import_backend = local_filesystem
definitions.local.path = /path/to/RabbitMQ/definitions/conf.d/

Improved resiliency of dead-lettering.

Enhancements

When the maximum allowed number of connections to the node was limited using the \ 
connection_max key
and the limit was reached, newly connecting client previously would run into a \ 
TCP connection timeout.

Now a more specific error will be returned to the client before connection closure.

Contributed by @SimonUnge (AWS).

CLI Tools

Bug Fixes

rabbitmqctl add_vhosts failed with an exception when --default-queue-type option \ 
was provided.

Management Plugin

Bug Fixes

HTTP API endpoint PUT /api/vhosts/{name} incorrectly used defaultqueuetype for \ 
default queue type
key name. It is now default_queue_type, the same key as returned by GET \ 
/api/vhosts/{name}.

HTTP API will now respond with a 405 Method Not Allowed instead of a 500 when
an unsupported method is used by the client.

Contributed by @gomoripeti (CloudAMQP).

AMQP 1.0 Plugin

Bug Fixes

Fixed AMQP 1.0 authentication issue that affected OAuth 2 token users.

Log message:
rabbitmq: updated to 3.11.10

RabbitMQ 3.11.10

Core Server

Bug Fixes

Tag changes could result in a loop of internal events in certain plugins.

Enhancements

Key classic mirrored queue (a deprecated feature) settings now can be overriden with
operator policies.

Contributed by @SimonUnge (AWS).

Management Plugin

Bug Fixes

Individual virtual host page failed to render.

Individual exchange page failed to render.

AMQP 1.0 Plugin

Enhancements

The plugin now supports authentication with JWT tokens (the OAuth 2 \ 
authentication backend).

OAuth 2 Plugin

Bug Fixes

The auth_oauth2.preferred_username_claims key in rabbitmq.conf now accepts a \ 
list of values.

Dependency Upgrades

ra was upgraded from 2.4.6 to 2.4.9

Log message:
rabbitmq: updated to 3.11.9

RabbitMQ 3.11.9

Core Server

Bug Fixes

Stream delivery using RabbitMQ Stream protocol v2 could fail to start in some cases.

Nodes could run into an exception with certain publishers that used QPid for \ 
client library.

When discovering feature flags across the cluster, default stability level is \ 
now experimental and not stable.

Reset and manually added nodes could start receiving stream replica data before \ 
its database was initialized,
confusing all code paths that expected a blank node state.

Fixed a minor issue with feature flag log message formatting.

Enhancements

Improved support for the AMQP 1.0 message format (used internally by streams), \ 
in particular, when original message
was published using AMQP 1.0.

CLI Tools

Features

rabbitmqctl set_permissions_globally is a new command that sets up user \ 
permissions in all existing virtual hosts.

rabbitmq-diagnostics cluster_status now lists how many CPU cores are available \ 
to individual nodes, plus a total.

Management Plugin

Bug Fixes

Limits tab failed to load when there were no limits configured.

Enhancements

It is now possible to disable operator policy modifications. This can be necessary in
RabbitMQ-as-a-Service environments.

Contributed by @illotum (AWS).

AMQP 1.0 Plugin

Enhancements

Support for OAuth 2 authentication and authorization backends.

MQTT Plugin

Bug Fixes

MQTT nodes did not correctly remove client IDs for clients connected to a node \ 
that was in the process of
being removed from the cluster.

OAuth 2 Plugin

Bug Fixes

auth_oauth2.additional_scopes_key had no effect.

LDAP Plugin

Bug Fixes

Due to a $ sign escaping differences between Make and Bazel (the newly adopted \ 
build tool),
default value of of user_dn_pattern setting was incorrect (had an extra $).

Log message:
revbump after lang/relang fix.

Log message:
Update to 3.11.5. From the changelog:

3.11.5:

## Changes Worth Mentioning

### Core Server

#### Enhancements

 * Backported a number of free disk space monitor resiliency improvements.
   GitHub issue: #5831

 * `raft.adaptive_failure_detector.poll_interval` exposes [`aten`]()'s
   `poll_interval` setting to RabbitMQ users. Increasing it can reduce
   the probability of false positives in clusters where inter-node
   communication links are used at close to maximum capacity. The
   default is `5000` (5 seconds). GitHub issue: #6632

 * When both `disk_free_limit.relative` and `disk_free_limit.absolute`,
   or both `vm_memory_high_watermark.relative` and
   `vm_memory_high_watermark.absolute` are set, the absolute settings
   will now take precedence. GitHub issue: #4980

 * Closing channels will now log a warning if they had any messages
   pending a confirmation from the server. GitHub issue: #1399

 * New quorum queue option for in-memory table (MemTable) compression.
   GitHub issue: #6590

 * Default queue type (a virtual host setting) is now applied when
   importing definitions into a single virtual host. GitHub issue: #6599

#### Bug Fixes

 * Feature flags provided by plugins were mistakingly disabled after
   node restart. GitHub issue: #6500

 * Classic queues with Single Active Consumer enabled could run into an
   exception. GitHub issue: #6502

 * When a global parameter was cleared, nodes emitted an internal event
   of the wrong type. GitHub issue: #6538

### CLI Tools

#### Bug Fixes

 * `rabbitmq-queues grow` and `rabbitmq-queues shrink` misformatted the
   errors they could encounter. GitHub issue: #6601

#### Enhancements

 * Implicit `help` command (when CLI tools were invoked without a
   command name) now respects all global flags (such as `--node`). For
   example, previously the `--node` flag in

       rabbitmqctl --node rabbit@ns1.rabbitmq.cluster.local

   was ignored but now CLI tools would discover what plugins are enabled
   on node `rabbit@ns1.rabbitmq.cluster.local` and include them into
   `help` output. GitHub issue: #6598

 * New key supported by `rabbitmqctl list_queues`:
   `effective_policy_definition` that returns merged definitions of
   regular and operator policies effective for the queue. GitHub
   issue: #6556

### Management Plugin

#### Enhancements

 * It is now possible to omit explicitly specifying queue type when
   declaring a queue (or stream) in the management UI, and rely on the
   default queue type configured for the selected virtual host. GitHub
   issue: #6600

 * New HTTP API endpoint, `GET /api/config/effective`, returns effective
   node configuration. This is an HTTP API counterpart of
   `rabbitmq-diagnostics environment`. GitHub issue: #6016

### Shovel Plugin

#### Enhancements

 * Flow control state for Shovels is now reported with higher fidelity
   (of 1 second vs. several seconds previously). This means it should be
   easier to spot Shovels that run into flow control using management
   UI. GitHub issue: #6615

### Sharding Plugin

#### Bug Fixes

 * Plugin could fail to boot and halt node boot due to incorrect boot
   step metadata. GitHub issue: #6583

## Dependency Upgrades

 * `ra` was upgraded from `2.4.1` to `2.4.5`.

3.11.4:

## Changes Worth Mentioning

### Core Server

#### Enhancements

 * Import of definition files with many streams is now more efficient.
   GitHub issue: #6436

 * Lower CPU throughput in clusters with many mostly idle streams.
   GitHub issue: #6436

 * Streams with `max_age` retention now attempt to reclaim disk space
   every hour. This is relevant in environments with a lot of mostly
   inactive streams that set `max_age`. GitHub issue: #6436

 * Quorum queues are now more resilient to WAL log growth with workloads
   that involve clients that register a consumer and then close the
   channel or connection without ever consuming any deliveries or
   cancelling the consumer. GitHub issue: #6447

#### Bug Fixes

 * When a node encouters an invalid `definitions.local.file` on boot,
   it will refuse to start instead of ignoring the file. GitHub
   issue: #2610

 * Fixed a type analyzer definition. GitHub issue: #6401

### CLI Tools

#### Enhancements

 * `rabbitmq-diagnostics check_if_node_is_quorum_critical` and
   `rabbitmq-upgrade await_online_quorum_plus_one` now consider stream
   (not just quorum queues) replica placement when determining if target
   node is quorum-critical. GitHub issue: #6448

 * Queue info keys now support more inclusive property names related to
   (deprecated) classic mirrored queues. For example, `mirror_pids` can
   now be used instead of `slave_pids`. GitHub issue: #2635

 * `rabbitmq-diagnostics memory_breakdown` now executes significantly
   faster in environments with a large number (say, tens or hundreds of
   thousands) of quorum queues. Two orders of magnitude faster, in fact.
   GitHub issue: #6388

#### Bug Fixes

 * Definition export in JSON failed on nodes that used
   `definitions.skip_if_unchanged`. GitHub issue: #6424

 * Using quorum queue-specific commands on streams now results in
   clearer error messages. GitHub issue: #6488

### LDAP Plugin

#### Bug Fixes

 * LDAP server password could end up in the logs in certain types of
   exceptions. GitHub issue: #4842

### STOMP Plugin

#### Enhancements

  * `x-max-age` stream setting now can be set by STOMP clients via a
    header. GitHub issue: #5003

## Dependency Upgrades

 * `osiris` was upgraded from `1.3.3` to `1.4.0`

Log message:
Indent.

Log message:
rabbitmq: updated to 3.11.3

RabbitMQ 3.11.3

Bug Fixes

Stream unsubscription leaked metric counters.
Stream could become unavailable in certain node or network failure scenarios.

Enhancements

It is now possible to pre-configure virtual host limits for groups of virtual hosts.
This is done using a set of new keys supported by rabbitmq.conf

Quorum queue replicas no longer try to contact their unreachable peers for metrics.
Previously this could result in a 30-40s delay for certain HTTP API requests \ 
that list queue metrics
if one or more cluster members were down or stopped.

CLI Tools

Bug Fixes

rabbitmq-diagnostics status now handles server responses where free disk space
is not yet computed. This is the case with nodes early in the boot process.

When a plugin was enabled as a dependency (e.g. rabbitmq_shovel as a dependency \ 
of rabbitmq_shovel_management),
CLI tools previously did not discover commands in such plugins. Only explicitly \ 
enabled or pre-configured
plugins were scanned for commands.

This behavior was confusing. Now all enabled (explicitly or as a dependency) \ 
plugins are scanned.

rabbitmq-diagnostics memory_breakdown now returns results much faster in \ 
environments with a large number
of quorum queues (say, tens or hundreds of thousands).

Stream Plugin

Bug Fixes

Addition of a stream member could fail if the node being added was very early in \ 
its boot process
(and doesn't have a certain stream-related components started).

AMQP 1.0 Plugin

Enhancements

Support for "modified" disposition outcome used by some client \ 
libraries (such as QPid).

Prometheus Plugin

Bug Fixes

Abruptly closed client connections resulted in incorrect updates of certain global
metric counters.

Management Plugin

Bug Fixes

Management UI links now include "noopener" and "noreferrer" \ 
attributes to protect
them against reverse tabnabbing.
Note that since management UI only includes a small number of external links to \ 
trusted resources,
reverse tabnabbing is unlikely to affect most users. However, it can show up in \ 
security scanner results
and become an issue in environments where a modified version of RabbitMQ is \ 
offered as a service.

Shovel Plugin

Bug Fixes

Plugin could stop in environments where no static Shovels were defined and a specific
sequence of events happens at the same time.

Enhancements

Shovel now handles connection.blocked and connection.unblocked notifications
from remote destination nodes. This means fewer messages are kept in Shovel \ 
buffers when
a resource alarm goes into affect on the destination node.

Log message:
A SUBST_SED was catching too much and breaking rabbitmq-server.  Change the
SUBST_SED to be more restrictive.

Log message:
rabbitmq: Update to 3.11.1

upstream changes:
-----------------
3.11.1
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.11.1.md
3.11.0
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.11.0.md
3.10.9
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.9.md
3.10.8
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.8.md
3.10.7
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.7.md
3.10.6
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.6.md
3.10.5
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.5.md
3.10.4
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.4.md
3.10.3
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.3.md
3.10.2
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.2.md
3.10.1
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.1.md
3.10.0
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.10.0.md
3.9.23
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.9.23.md
3.9.22
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.9.22.md
3.9.21
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.9.21.md
3.9.20
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.9.20.md
3.9.19
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.9.19.md
3.9.18
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.9.18.md
3.9.17
  o https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.9.17.md

Log message:
*: Revbump packages that use Python at runtime without a PKGNAME prefix