Log message:
Mass-change BUILD_DEPENDS to TOOL_DEPENDS outside mk/.

Almost all uses, if not all of them, are wrong, according to the
semantics of BUILD_DEPENDS (packages built for target available for
use _by_ tools at build-time) and TOOL_DEPEPNDS (packages built for
host available for use _as_ tools at build-time).

No change to BUILD_DEPENDS as used correctly inside buildlink3.

As proposed on tech-pkg:
https://mail-index.netbsd.org/tech-pkg/2023/06/03/msg027632.html

Log message:
rabbitmq: updated to 3.11.17

RabbitMQ 3.11.17

Core Server

Bug Fixes

Fixed two quorum queue federation issues.

Nodes that had a large number of quorum queues could observe accumulation of \ 
Erlang processes
under significant load.

Nodes could hang when recovering classic queue indices during boot.

As of 6418, nodes refuse
to start if the definitions file cannot be parsed as valid JSON.

Now this also applies to nodes that were configure to skip definition import if \ 
the input file(s) has changed
using the definitions.skip_if_unchanged setting.

Enhancements

Reduce CPU footprint of quorum queue metric emission in clusters with a lot of \ 
quorum queues.

Management Plugin

Bug Fixes

The plugin reported the interface its listener(s) were bound to incorrectly.

Enhancements

It is now possible to change default queue type for a virtual host using the
PUT /api/vhosts/{name} endpoint.

Web STOMP Plugin

Bug Fixes

The plugin reported the interface its listener(s) were bound to incorrectly.

Web MQTT Plugin

Bug Fixes

The plugin reported the interface its listener(s) were bound to incorrectly.

Debian Package

Bug Fixes

Make-based source package builds were failing in an offline environment.

RPM Package

Bug Fixes

Make-based source package builds were failing in an offline environment.

Dependency Upgrades

CSV parser used by CLI tools was upgraded to 3.0.5

Log message:
rabbitmq: update for elixir update

Bump PKGREVISION.

Log message:
rabbitmq: updated to 3.11.16

RabbitMQ 3.11.16

Core Server

Bug Fixes

Automatic node removal now will
remove quorum queue replicas from the node before removing it from the cluster.

Enhancements

A new boolean setting, \ 
quorum_queue.property_equivalence.relaxed_checks_on_redeclaration,
makes it possible to relax queue property equivalence checks
for quorum queues. Specifically, when a quorum queue is redeclared and the \ 
client-provided
type is set to "classic", this setting will help avoid a channel \ 
exception, making it
easier to migrate to quorum queues step by step, without upgrading all \ 
applications in a short
period of time.

CLI Tools

Enhancements

rabbitmq-queues grow and rabbitmq-queues add_member now verify cluster \ 
membership of the node
new quorum queue replicas should be placed on.

Federation Plugin

Bug Fixes

URI parser incorrectly used the password query parameter to override the password
value in authority (user info) part.

The password query parameter can be used to specify private key password for
upstream connections that use TLS.

Shovel Plugin

Bug Fixes

URI parser incorrectly used the password query parameter to override the password
value in authority (user info) part.

The password query parameter can be used to specify private key password for Shovels
that use TLS.

Log message:
rabbitmq: updated to 3.11.15

RabbitMQ 3.11.15

Core Server

Enhancements

Operator policies now can define "ha-sync-mode", a classic mirrored \ 
queue setting. Note that classic mirrored queues are
deprecated and will be removed in RabbitMQ 4.0.

All users of CMQs should migrate to quorum queues or streams,
or a combination of both.

Log message:
rabbitmq: fix PLIST per mef's bulk build

(not tested locally)

Log message:
rabbitmq: fix PLIST after update

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 $).