Changelog

oauth2-1.0.0-beta.0 (2023-09-25)

Full Changelog

oauth2-1.0.0 (2023-09-25)

Full Changelog

v6.6.0-beta.0 (2023-09-25)

Full Changelog

v6.6.0 (2023-09-25)

Full Changelog

Implemented enhancements:

Allow update of RoutingKey during Nack #1333
Support credential refresh for OAuth 2/JWT authentication scenarios #956

Fixed bugs:

Configured MaxMessageSize is not honoured #1378
ConnectionFactory Authmechanisms has incorrect sharing between instances #1370
Unknown reply code 312 #1331

Closed issues:

Invalid parameter name in IManagementClient.DeleteExchangeBindingAsync #1375
Closing connection in EventingBasicConsumer.Received event handler freezes execution of event handler and connection is never closed #1292

v6.5.0 (2023-03-25)

Full Changelog

Implemented enhancements:

Investigate the use of TaskCreationOptions.LongRunning #1318
Exception during recovery causes recovery failure #658

Closed issues:

Consumer tags aren't cleaned on channel close causing memory leak. #1302
Impossible to use a ulong as a header value #1298
Recovery does not appear to save consumer arguments #1293
Timeout when opening a new channel after channel exception #1246
Autorecovery for server-named queues loops indefinitely when consumer listen this queue #1238
IModel.WaitForConfirmsOrDie* methods don't document that they close #1234
Port #1223 to main #1225
Better integrate max message size #1223
7.0 Release Checklist #1191
Missing IRecoveryable implementation #998
BasicGetResult body memory safety in 6.x+ #994

v6.4.0-rc.1 (2022-06-14)

Full Changelog

Changes Between 6.3.1 and 6.4.0

This release adds the ability to specify a maximum message size when receiving data. The default values are:

RabbitMQ .NET client 7.0.0 and beyond: 128MiB
RabbitMQ .NET client 6.4.0 up to 7.0.0: no limit by default

Receiving a frame that specifies a content larger than the limit will throw an execption. This is to help prevent situations as described in this discussion.

To set a limit, use the set MaxMessageSize on your ConnectionFactory before opening connections:

// This sets the limit to 512MiB
var cf = new ConnectionFactory();
cf.MaxMessageSize = 536870912;
var conn = cf.CreateConnection()`

GitHub milestone: 6.4.0 Diff: link

Changes Between 6.3.0 and 6.3.1

GitHub milestone: 6.3.1 Diff: link

Changes Between 6.2.4 and 6.3.0

GitHub milestone: 6.3.0 Diff: link

Changes Between 6.2.3 and 6.2.4

GitHub milestone: 6.2.4

This release contains some important bug fixes:

Fix connection leaks on auto recovery
Fix buffer overflow when writing long strings
Fix regression resulting in ObjectDisposedException
Fix regression that could affect consuming after auto recovery

Changes Between 6.2.1 and 6.2.3

GitHub milestone: 6.2.3 GitHub milestone: 6.2.2

Changes Between 6.2.0 and 6.2.1

6.2.0 was published incorrectly, resulting in version 6.2.1

GitHub milestone: 6.2.1.

Changes Between 6.1.0 and 6.2.0

This releases primarily focuses on efficiency improvements and addressing bugs introduced in 6.x releases.

A full list of changes can be found in the GitHub milestone: 6.2.0.

Key highlights include:

Concurrent publishing on a shared channel is now safer. We still recommend avoiding it when possible but safety properties have been improved by changing how outgoing frame sequences are serialised.

Contributed by @bollhals.

GitHub issue: #878
Batch publishing using System.ReadOnlyMemory<byte> payloads instead of byte arrays.

Contributed by @danielmarbach.

GitHub issue: #865, #892

Changes Between 6.0.0 and 6.1.0

This release continues with improvements to memory use and object allocations.

A full list of changes can be found in the GitHub milestone: 6.1.0.

Changes Between 5.2.0 and 6.0.0

This major release of this client introduces substantial improvements in terms of memory footprint and throughput. They come at the cost of minor but important breaking API changes covered below.

The client now requires .NET Framework 4.6.1 or .NET Standard 2.0. Earlier versions are no longer supported by the 6.x series.

Key improvements in this release have been the result of hard work by our stellar community members (in no particular order): @stebet, @bording, @Anarh2404, @danielmarbach, and others.

A full list of changes can be found in the GitHub milestone: 6.0.0.

The Switch to System.Memory (and Significantly Lower Memory Footprint that Comes with It)

The client now uses the System.Memory library for message and command payloads. This significantly reduces object allocation and GC pressure for heavy workloads but also potentially requires application changes: consumer delivery payloads are now of instance System.ReadOnlyMemory<byte> instead of byte[].

While there's an implicit conversion for these types, instances of System.ReadOnlyMemory<byte> must be copied or consumed/deserialised before delivery handler completes. Holding on to delivered payloads and referencing them at a later point is no longer safe.

The same applies to publishers and the IModel.BasicPublish method: prefer using System.ReadOnlyMemory<byte> over byte[] and dont' assume that this memory can be retained and used outside of the scope of the publishing function.

GitHub issue: #732

Timeouts Use `System.TimeSpan`

All timeout arguments now use System.TimeSpan values.

GitHub issue: #688

Reduced Public API Surface

No major changes here but this is potentially breaking. Only public classes that were never meant to be publicly used have been turned internal to the client.