v10.0.1

What's Changed

• Make copy of respons message body by @emilklasson in #32

Full Changelog: v10.0.0...v10.0.1

v10.0.0

What's Changed

• Update connection config by @emilklasson in #31

Full Changelog: v9.0.0...v10.0.0

v9.0.0

What's Changed

• Log connected node endpoint in #30

Full Changelog: v8.0.0...v9.0.0

v8.0.1

What's Changed

• Fix nuget release user.

v8.0.0

What's Changed

• Uses version 7.2.1 of RabbitMQ.Client.
• New modules for Connect, Consume, RPC and Publish.
• We can reuse the connection for multiple channels.
• Every connected queue have their own channel.

Full Changelog: v7.0.0...v8.0.0

v7.0.0

Breaking change

• In v6.0.0 we added a convention that if a queue is bound to exchange it becomes quorum, otherwise classic. We then realized that sometimes we want a quorum queue even if not bound to an exchange. This release lets you specify which type you want on each queue. PR: #26

v6.0.0

Breaking changes

• New convention introduced: Use quorum queues if bound to exchange, otherwise classic. PR #25

v5.0.2

What's new

• Correctly handle multiple confirms. Previously the client could incorrectly state publish timeouts even though the publish was confirmed by the broker.

v5.0.1

What's new

• Target .NET 6
• Function getHeaderAsString that given a ReceivedMessage and a key tries to find the Header value and convert it to a string.
• Pin FSharp.Core to 6.0.0.

v5.0.0

What's new

• Target .NET 6
• Function getHeaderAsString that given a ReceivedMessage and a key tries to find the Header value and convert it to a string.