Release v2.0.0-beta.1

Overview

Adding demissions. This is a big, evil change.

The original plan was to use rabbitmq/rabbitmq-delayed-message-exchange, though this seems to have a tonne of problems with load and inaccurate timings.

Instead I've gone with creating a separate queue for each demission (bypassing RabbitMQ's per-message TTL caveat), allowing the use of dead-letter exchanges to push messages to the right queue at the right time.

New features

• Set up a before function for demissions: daee6a3
• Set up mad demission bits. We’re making a queue for every message. Is that bad?: a1984cc

Bug fixes / generic changes

• Fiddling with these tests to have them pass even on slow VMs: 8524fca
• Only ever send a single argument as a message; all other parameters are extraneous: a8cd3f0
• If a message has been scheduled, pass that through in the resulting event: 0becae8
• Adding a simple usage example for demissions, mainly proving they work: 22e43e9
• Fix for demissions cancelling when the publisher disconnects: 45aeff0

Release v1.2.0

The core of Remit has been overhauled in this release, though user experience remains entirely unchanged (there are no breaking changes) so we're staying with v1.

The first major thing is the library's been rewritten to use amqplib's promise API rather than its callback API. This seems to allow for better integration with tracing tools and makes the whole thing feel a bit more whole.

The second major change is that we now use RabbitMQ's "direct reply-to" functionality. This is only available in RabbitMQ >=3.4.0 so users below that threshold should stick with v1.1.7. The use of this, however, improves RPC speed dramatically. Bypassing the use of a response queue doubles the messages per second we can manage with simplistic calls.

Release v1.1.7

Just starting to use Github releases for this, so this is the first!