Build Details

Built against RabbitMQ server 4.1.0 on Erlang/OTP 26.2.5.11.

Breaking Changes and Compatibility Notes

This plugin is 4.1.x compatible with the following limitations:

1. If the cluster uses Mnesia for schema store, it works exactly as it did against RabbitMQ 3.13.x
2. If the cluster uses Khepri and the plugin is enabled after Khepri, it will start Mnesia, set up a node-local Mnesia replica and schema, and works as in scenario 1
3. Important: if the cluster uses Mnesia, then the plugin is enabled, and then Khepri is enabled, the plugin must be disabled and re-enabled, or the node must be restarted. Then it will start Mnesia and works as in scenario 2

Changes

• RabbitMQ 4.1.0 compatibility.

Build Details

Built against RabbitMQ server 4.0.7 on Erlang/OTP 26.2.5.9.

Breaking Changes and Compatibility Notes

This plugin is 4.0 compatible with the following limitations:

1. If the cluster uses Mnesia for schema store, it works exactly as it did against RabbitMQ 3.13.x
2. If the cluster uses Khepri and the plugin is enabled after Khepri, it will start Mnesia, set up a node-local Mnesia replica and schema, and works as in scenario 1
3. Important: if the cluster uses Mnesia, then the plugin is enabled, and then Khepri is enabled, the plugin must be disabled and re-enabled, or the node must be restarted. Then it will start Mnesia and works as in scenario 2

Changes

• RabbitMQ 4.0.7 compatibility.

  GitHub issues: #298, rabbitmq/rabbitmq-server#13381

Build Details

Built against RabbitMQ server 4.0.2 on Erlang/OTP 26.2.5.3.

Breaking Changes and Compatibility Notes

This plugin is 4.0 compatible with the following limitations:

1. If the cluster uses Mnesia for schema store, it works exactly as it did against RabbitMQ 3.13.x
2. If the cluster uses Khepri and the plugin is enabled after Khepri, it will start Mnesia, set up a node-local Mnesia replica and schema, and works as in scenario 1
3. Important: if the cluster uses Mnesia, then the plugin is enabled, and then Khepri is enabled, the plugin must be disabled and re-enabled, or the node must be restarted. Then it will start Mnesia and works as in scenario 2

Changes

• RabbitMQ 4.0.x compatibility, including Khepri.

  Contributed by @gomoripeti.

  GitHub issues: #290, #291, #292

rabbitmq_delayed_message_exchange v3.13.0

Built against:
rabbitmq-server [https://github.com/rabbitmq/rabbitmq-server/archive/refs/heads/v3.13.x.zip]
OTP 26.2.2

rabbitmq_delayed_message_exchange v3.12.0

Built against rabbitmq-server [https://github.com/rabbitmq/rabbitmq-server/archive/refs/heads/v3.12.x.zip]

This release targets RabbitMQ 3.11.x and as such, requires Erlang 25.

Enhancements

• This plugin now emits relevant publishing metrics.

  Contributed by @gomoripeti (CloudAMQP)

  GitHub issue: #197

• More accommodating type conversion for delay header values.

  Contributed by @unknovvn.

  GitHub issue: #198

This release has no functional changes but lists RabbitMQ 3.10.x as supported in plugin metadata.

This release has no changes except for its metadata that lists RabbitMQ 3.9.0 (and future 3.9.x releases) as supported.

3.8.17

This release targets RabbitMQ 3.8.16 and later versions.

This release requires Erlang 23.2 or a later version, and supports Erlang 24.

Enhancements

• When nodes are restarted, schema database tables used by this plugin are now reconciled
  with cluster peers the same way RabbitMQ core does it.

  Contributed by @mwfriedm.

  GitHub issue: rabbitmq/rabbitmq-delayed-message-exchange#163