Skip to content

Releases: insurello/Insurello.RabbitMqClient

v7.0.0

13 Feb 14:55
98c9ee1

Choose a tag to compare

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

13 Feb 14:22
0cc5682

Choose a tag to compare

Breaking changes

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

v5.0.2

16 Sep 09:02
3a4a4d7

Choose a tag to compare

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

30 May 11:16
1bde093

Choose a tag to compare

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

29 May 13:07
9664164

Choose a tag to compare

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.

v4.3.0

21 Jul 08:26
33b4463

Choose a tag to compare

What's new

  • When calling MqClient.close channel callbacks calls are ignored to prevent terminating parent process prematurely
  • Added SourceLink

v4.2.0

20 Jul 09:14
5b407e1

Choose a tag to compare

v4.2.0 Pre-release
Pre-release
  • Ignore callbacks while closing
  • Fantomas formatting
  • Microsoft.SourceLink.GitHub

v4.1.0

22 Oct 09:54
5fb327c

Choose a tag to compare

What's new

  • Model now contains connection.
  • The library now has a close function which closes the channelConsumer, rpcConsumer, and then the connection.

v4.0.0

03 Jul 09:38
f3bb98e

Choose a tag to compare

Version v4.0.0

What's new

  • failWithWrapper - removed
  • terminateOnFailureWrapper - Force application termination on failures

New strategy for failWithWrapper

The function failWithWrapper has been replaced with terminateOnFailureWrapper that will force an application exit if there's an exception raised in received message callback or a message is received on ConsumerCancelled or Shutdown

v3.0.0

01 Jul 08:44
a31652a

Choose a tag to compare

Api improvements (#16)

* Add Async API
* Use Map<String, String> everywhere for headers instead of List<(string * string)>


Co-authored-by: Philip Pålsson <philip.palsson@insurello.se>
Co-authored-by: Emil Klasson <emil.klasson@insurello.se>