amqp_client breaking changes

• v4.0.8 \u2192 v4.1.0-rc.2breaking

  The client now only can declare durable entities in preparation for a Khepri-only future version of RabbitMQ. GitHub issue: [#12947](https://github.com/rabbitmq/rabbitmq-server/pull/12947)

• v4.0.8 \u2192 v4.1.0-rc.2breaking

  `rabbitmqctl force_reset` is **deprecated** as it is incompatible with Khepri, which will become the default metadata store in RabbitMQ by 4.2.0. GitHub issue: [#13217](https://github.com/rabbitmq/rabbitmq-server/pull/13217)

• v4.0.8 \u2192 v4.1.0-rc.2breaking

  The original HTTP API One True Health Check™ is now a no-op. A comparable "mega health check" has long been deprecated in CLI tools and was made a no-op in `4.0.0`. This endpoint was using a [deprecated feature](https://www.rabbitmq.com/docs/deprecated-features): a classic non-exclusive transient (non-durable) queue. See [Health Checks](https://www.rabbitmq.com/docs/monitoring#health-checks) for modern focused alternatives. GitHub issue: [#13047](https://github.com/rabbitmq/rabbitmq-server/issue

• v4.0.8 \u2192 v4.1.0-rc.2breaking

  The OAuth 2 plugin now requires several values to be explicitly configured by the user and will not provide any defaults. The affected identity providers are Azure Entra (né Azure AD) and auth0. GitHub issue: [#12235](https://github.com/rabbitmq/rabbitmq-server/issues/12235)

• v4.1.0-beta.5 \u2192 v4.1.0-rc.1breaking

  `rabbitmqctl force_reset` is **deprecated** as it is incompatible with Khepri, which will become the default metadata store in RabbitMQ by 4.2.0. GitHub issue: [#13217](https://github.com/rabbitmq/rabbitmq-server/pull/13217)

• v4.1.0-beta.5 \u2192 v4.1.0-rc.1breaking

  The client now only can declare durable entities in preparation for a Khepri-only future version of RabbitMQ. GitHub issue: [#12947](https://github.com/rabbitmq/rabbitmq-server/pull/12947)

• v4.1.0-beta.5 \u2192 v4.1.0-rc.1breaking

  The OAuth 2 plugin now requires several values to be explicitly configured by the user and will not provide any defaults. The affected identity providers are Azure Entra (né Azure AD) and auth0. GitHub issue: [#12235](https://github.com/rabbitmq/rabbitmq-server/issues/12235)

• v4.1.0-beta.5 \u2192 v4.1.0-rc.1breaking

  The original HTTP API One True Health Check™ is now a no-op. A comparable "mega health check" has long been deprecated in CLI tools and was made a no-op in `4.0.0`. This endpoint was using a [deprecated feature](https://www.rabbitmq.com/docs/deprecated-features): a classic non-exclusive transient (non-durable) queue. See [Health Checks](https://www.rabbitmq.com/docs/monitoring#health-checks) for modern focused alternatives. GitHub issue: [#13047](https://github.com/rabbitmq/rabbitmq-server/issue

• v4.0.7 \u2192 v4.1.0-beta.5breaking

  The client now only can declare durable entities in preparation for a Khepri-only future version of RabbitMQ. GitHub issue: [#12947](https://github.com/rabbitmq/rabbitmq-server/pull/12947)

• v4.0.7 \u2192 v4.1.0-beta.5breaking

  `rabbitmqctl force_reset` is **deprecated** as it is incompatible with Khepri, which will become the default metadata store in RabbitMQ by 4.2.0. GitHub issue: [#13217](https://github.com/rabbitmq/rabbitmq-server/pull/13217)

• v4.0.7 \u2192 v4.1.0-beta.5breaking

  The original HTTP API One True Health Check™ is now a no-op. A comparable "mega health check" has long been deprecated in CLI tools and was made a no-op in `4.0.0`. This endpoint was using a [deprecated feature](https://www.rabbitmq.com/docs/deprecated-features): a classic non-exclusive transient (non-durable) queue. See [Health Checks](https://www.rabbitmq.com/docs/monitoring#health-checks) for modern focused alternatives. GitHub issue: [#13047](https://github.com/rabbitmq/rabbitmq-server/issue

• v4.0.7 \u2192 v4.1.0-beta.5breaking

  The OAuth 2 plugin now requires several values to be explicitly configured by the user and will not provide any defaults. The affected identity providers are Azure Entra (né Azure AD) and auth0. GitHub issue: [#12235](https://github.com/rabbitmq/rabbitmq-server/issues/12235)

• v4.0.9 \u2192 v4.1.0breaking

  `rabbitmqctl force_reset` is **deprecated** as it is incompatible with Khepri, which will become the default metadata store in RabbitMQ by 4.2.0. GitHub issue: [#13217](https://github.com/rabbitmq/rabbitmq-server/pull/13217)

• v4.0.9 \u2192 v4.1.0breaking

  The client now only can declare durable entities in preparation for a Khepri-only future version of RabbitMQ. GitHub issue: [#12947](https://github.com/rabbitmq/rabbitmq-server/pull/12947)

• v4.0.9 \u2192 v4.1.0breaking

  The OAuth 2 plugin now requires several values to be explicitly configured by the user and will not provide any defaults. The affected identity providers are Azure Entra (né Azure AD) and auth0. GitHub issue: [#12235](https://github.com/rabbitmq/rabbitmq-server/issues/12235)

• v4.0.9 \u2192 v4.1.0breaking

  The original HTTP API One True Health Check™ is now a no-op. A comparable "mega health check" has long been deprecated in CLI tools and was made a no-op in `4.0.0`. This endpoint was using a [deprecated feature](https://www.rabbitmq.com/docs/deprecated-features): a classic non-exclusive transient (non-durable) queue. See [Health Checks](https://www.rabbitmq.com/docs/monitoring#health-checks) for modern focused alternatives. GitHub issue: [#13047](https://github.com/rabbitmq/rabbitmq-server/issue

Get this data programmatically \u2014 free, no authentication.