v0.66.0

v0.66.0 (Oct 17, 2025)

Enhancements

• Request errors now include the error and reason fields populated if the API response contains them

v0.65.0

v0.65.0 (Oct 11, 2025)

Enhancements

• Overview#has_jit_enabled is a new method that returns true if the Erlang runtime has the JIT enabled

v0.64.0

v0.64.0 (Oct 9, 2025)

Bug Fixes

• Reintroduced QueueOps#has_queue_ttl_arg, which was unintentionally lost during a refactoring

v0.63.0

v0.63.0 (Oct 9, 2025)

Bug Fixes

• Reintroduced QueueOps#is_server_named, which was unintentionally lost during a refactoring

v0.62.0

v0.62.0 (Oct 9, 2025)

Enhancements

• Client#list_all_cluster_plugins is a new function that returns a combined set of plugins enabled across all cluster nodes
• Client#list_node_plugins is a new function that returns the list of plugins enabled on a specific node

v0.61.0

v0.61.0 (Oct 8, 2025)

Enhancements

• Logging via the log crate. Both clients now emit trace-level logs for HTTP operations, including request/response details and retry attempts.

• HTTP request timeout support. Both ClientBuilder implementations now provide a with_request_timeout method
  for configuring request timeouts:

  use std::time::Duration;
  use rabbitmq_http_client::api::ClientBuilder;
  
  let client = ClientBuilder::new()
      .with_endpoint("http://localhost:15672/api")
      .with_basic_auth_credentials("user", "pass")
      .with_request_timeout(Duration::from_secs(30))
      .build();

  The timeout applies to the entire request/response cycle.
  If a request takes longer than the configured duration, it will be aborted and return a timeout error.

  Note that this new setting is ignored if a custom HTTP client is provided via ClientBuilder#with_client.
  In that case, configure the timeout directly on the custom client instead.

v0.60.0

v0.60.0 (Sep 28, 2025)

Enhancements

• HTTP request retry support. Both ClientBuilder implementations now allow for minimalistic retry behavior configuration:
  the number of retry attempts and the fixed delay between them.

  use rabbitmq_http_client::api::{ClientBuilder, RetrySettings};
  
  let client = ClientBuilder::new()
      .with_endpoint("http://localhost:15672/api")
      .with_basic_auth_credentials("user", "pass")
      .with_retry_settings(RetrySettings {
          // 2 retry attempts (+ 1 initial = 3 total attempts)
          max_attempts: 2,
          // a fixed wait of 500 ms between retries
          delay_ms: 500,
      })
      .build();

v0.59.0

v0.59.0 (Sep 26, 2025)

Enhancements

• NodeMemoryFootprint#breakdown is now an Option<NodeMemoryBreakdown> to handle cases
  where the node memory breakdown stats are not yet available.

Bug Fixes

• NodeMemoryTotals#max now correctly compares all three memory totals (RSS, allocated, and used by runtime) instead of comparing RSS twice.

v0.58.0

v0.58.0 (Sep 23, 2025)

Breaking Changes

• All delete_* and clear_* functions now accept an idempotently boolean argument,
  making it possible to issue idempotent deletion requests that would not fail
  with a 404 Not Found response.

  This affects the following functions:

  • delete_federation_upstream
  • delete_policy
  • delete_operator_policy
  • close_connection
  • close_user_connections
  • delete_binding
  • clear_topic_permissions
  • delete_shovel
  • clear_runtime_parameter

• delete_binding now accepts a requests::BindingDeletionParams struct instead of a long list of arguments.

Enhancements

• All delete_* functions now support idempotent operations.

v0.57.0

v0.57.0 (Sep 22, 2025)

Enhancements

• responses::Shovel now can be converted to requests::RuntimeParameterDefinition, for example, when a shovel
  needs to be updated