{"ecosystem":"hex","package":"amqp10_client","from_version":null,"to_version":null,"changes":[{"from_version":"v4.0.8","to_version":"v4.1.0-rc.2","change_type":"breaking","description":"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)","migration_hint":null},{"from_version":"v4.0.8","to_version":"v4.1.0-rc.2","change_type":"breaking","description":"`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)","migration_hint":null},{"from_version":"v4.0.8","to_version":"v4.1.0-rc.2","change_type":"breaking","description":"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","migration_hint":null},{"from_version":"v4.0.8","to_version":"v4.1.0-rc.2","change_type":"breaking","description":"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)","migration_hint":null},{"from_version":"v4.1.0-beta.5","to_version":"v4.1.0-rc.1","change_type":"breaking","description":"`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)","migration_hint":null},{"from_version":"v4.1.0-beta.5","to_version":"v4.1.0-rc.1","change_type":"breaking","description":"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)","migration_hint":null},{"from_version":"v4.1.0-beta.5","to_version":"v4.1.0-rc.1","change_type":"breaking","description":"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)","migration_hint":null},{"from_version":"v4.1.0-beta.5","to_version":"v4.1.0-rc.1","change_type":"breaking","description":"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","migration_hint":null},{"from_version":"v4.0.7","to_version":"v4.1.0-beta.5","change_type":"breaking","description":"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)","migration_hint":null},{"from_version":"v4.0.7","to_version":"v4.1.0-beta.5","change_type":"breaking","description":"`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)","migration_hint":null},{"from_version":"v4.0.7","to_version":"v4.1.0-beta.5","change_type":"breaking","description":"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","migration_hint":null},{"from_version":"v4.0.7","to_version":"v4.1.0-beta.5","change_type":"breaking","description":"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)","migration_hint":null},{"from_version":"v4.0.9","to_version":"v4.1.0","change_type":"breaking","description":"`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)","migration_hint":null},{"from_version":"v4.0.9","to_version":"v4.1.0","change_type":"breaking","description":"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)","migration_hint":null},{"from_version":"v4.0.9","to_version":"v4.1.0","change_type":"breaking","description":"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)","migration_hint":null},{"from_version":"v4.0.9","to_version":"v4.1.0","change_type":"breaking","description":"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","migration_hint":null}],"total":16,"note":"Curated major-version breaking changes. Always verify against the package's official changelog before migrating.","_cache":"hit"}