v2.12.0

v2.12.0 (Sep 23, 2025)

Enhancements

• federation enable_tls_peer_verification_for_all_upstreams is a new command that enables TLS peer verification
  for all federation upstreams:

  # Note that the certificate and private key paths below refer
  # to the files deployed to the target RabbitMQ node(s), not to the
  # local files.
  #
  # As such, these arguments are command-specific and should not be confused
  # with the global `--tls-ca-cert-file`, `--tls-cert-file`, and `--tls-key-file`
  # arguments that are used by `rabbitmqadmin` itself to connect to the target node
  # over the HTTP API.
  rabbitmqadmin federation enable_tls_peer_verification_for_all_upstreams \
      --node-local-ca-certificate-bundle-path /path/to/node/local/ca_bundle.pem \
      --node-local-client-certificate-file-path /path/to/node/local/client_certificate.pem \
      --node-local-client-private-key-file-path /path/to/node/local/client_private_key.pem

  See TLS guide and Federation guide to learn more.

• shovel disable_tls_peer_verification_for_all_source_uris is a new command that disables TLS peer verification
  for all shovel source URIs.

  Important: this command should only be used to undo incorrect shovel source URIs, after a bad deployment, for example,
  if peer verification was enabled before certificates and keys were
  deployed.

• shovel disable_tls_peer_verification_for_all_source_uris is a new command that disables TLS peer verification
  for all shovel source URIs.

  Important: this command should only be used to undo incorrect shovel destination URIs (see above).

• All delete_* and clear_* commands now support the --idempotently flag (previously it was just a few):

  • bindings delete
  • close connection
  • close user_connections
  • connections close
  • connections close_of_user
  • exchanges delete
  • exchanges unbind
  • federation delete_upstream
  • global_parameters clear
  • operator_policies delete
  • parameters clear
  • policies delete
  • queues delete
  • shovels delete
  • streams delete
  • users delete
  • vhosts delete

v2.11.0

v2.11.0 (Sep 22, 2025)

Enhancements

• federation disable_tls_peer_verification_for_all_upstreams is a new command that disables TLS peer verification
  for all federation upstreams.

  Important: this command should only be used in case of an emergency, for example,
  if peer verification was enabled prematurely during
  a deployment and all federation links fail to connect.

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.57.0

v2.10.0

v2.10.0 (Sep 18, 2025)

Enhancements

• definitions export_from_vhost now supports --transformations:

  # previously only 'definitions export' supported --transformations
  rabbitmqadmin --vhost "my-vhost" definitions export_from_vhost \
                --transformations prepare_for_quorum_queue_migration,drop_empty_policies \
                --file "my-vhost.definitions.json"

Bug Fixes

• The prepare_for_quorum_queue_migration transformation did not remove CMQ-related keys
  such as x-ha-mode from optional queue arguments

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.52.0

v2.9.0

v2.9.0 (Aug 25, 2025)

Enhancements

• RabbitMQ 4.2 forward compatibility: shovels list_all and shovels list now can render
  local shovel rows

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.44.0

v2.8.2

v2.8.2 (Aug 19, 2025)

Enhancements

• definitions export is now compatible with RabbitMQ 3.10.0, a series that has reached end of life (EOL) in late 2023

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.43.0

v2.8.1

v2.8.1 (Aug 14, 2025)

Bug Fixes

• shovels list and shovels list_all panicked when target cluster had at least one
  static shovel

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.42.0

v2.8.0

v2.8.0 (Aug 11, 2025)

Bug Fixes

• shovels list_all panicked when one of the shovels was in the terminated state

Enhancements

• shovels list is a new command that lists shovels in a particular virtual host

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.41.0

v2.7.2

v2.7.2 (Aug 6, 2025)

Bug Fixes

• shovels declare_amqp091 panicked when the --source-exchange argument was not provided,
  even if --source-queue was

v2.7.1

v2.7.1 (in development)

Bug Fixes

• Improved handling of missing or impossible to load/parse --tls-ca-cert-file on the command line.

  The tool now properly handles cases where a CA certificate file path is not provided, making
  CA certificate loading optional rather than required, which prevents crashes when TLS is used
  without a custom CA certificate bundle

• show overview could panic when run against a freshly booted RabbitMQ node that did not have certain
  metrics/rates initialized and available. Now those metrics will use the default values for their types,
  such as 0 and 0.0 for the counters, gauges, rates

Upgrades

• RabbitMQ HTTP API client was upgraded to 0.40.0

v2.7.0

v2.7.0 (Jul 15, 2025)

Enhancements

• rabbitmqadmin.conf now supports more TLS-related settings: ca_certificate_bundle_path (corresponds to --tls-ca-cert-file on the command line),
  client_certificate_file_path (corresponds to --tls-cert-file), and client_private_key_file_path (corresponds to --tls-key-file).

  As the names suggest, they are used to configure the CA certificate bundle file path, the client certificate file path,
  and the client private key file path, respectively:

   [production]
   hostname = "(redacted)"
   port = 15671
   username = "user-efe1f4d763f6"
   password = "(redacted)"
   tls = true
   ca_certificate_bundle_path = "/path/to/ca_certificate.pem"
   client_certificate_file_path = "/path/to/client_certificate.pem"
   client_private_key_file_path = "/path/to/client_key.pem"

  To learn more, see RabbitMQ's TLS guide.

Bug Fixes

• Tool version was unintentionally missing from -h output (but present in its long counterpart, --help)
• The tls setting in rabbitmqadmin.conf, a --use-tls equivalent, was not respected when connecting to a node
  in certain cases