release 0.5.2

Fixes:
 - issue #75: do not crash when collecting unavailable info from the
 cache
 - issue #75, #77: improve cache availability on exchanges in two
 nodes setup
 - If we timeout when reloading the cache, force load it instead of
 crashing

Improvements:
 - Do not replicate the cache on multiple nodes with queue
 deduplication

release 0.5.1

Fixes:
  - issue #76: reinstate use of broker boot steps due to upstream fix

release 0.5.0

Fixes:
  - issue #21: reinstate support for publish confirms

Features:
  - issue #62: support broker restart
  - Support disabling the plugin

Refactoring:
  - Deprecate use of broker boot steps in favour of standard
    Erlang/Elixir application behaviour

release 0.4.5

Fixes:
  - issue #49, #55, #58: improve cache resilience over nodes crash and
    replacements

Deprecation:
  - queue: parameter `x-cache-persistence` has no effect anymore

release 0.4.4

Fixes:
  - issue #52: handle dead-lettered messages in queue deduplication

release 0.4.3

Fixes:
  - Add support for RabbitMQ v3.8

release 0.4.2

Fixes:
  - issues #36: fix a bug preventing a deduplication queue
    from being deleted

release 0.4.1

Fixes:
  - issues #33, #34: accept non-string queue deduplication headers
  - issue #33: handle all integer types in exchange arguments

release 0.4.0

Refactoring:
  - Caching mechanism no longer relies on a single process per cache.
    Instead, a single process per rabbit node takes care of creating,
    cleaning and destroying the caches. Exchanges and queues access
    their own caches directly.

Fixes:
  - issues #28, #30: exchange level deduplication now works across
    multiple rabbit nodes.

release 0.3.7

Fixes:
  - issue #26: fix queue crash due to wrong parameter matching
               in several callback functions