Update dependency RabbitMQ.Client to v5.2.0 #188
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.1.0
->5.2.0
Release Notes
rabbitmq/rabbitmq-dotnet-client
v5.2.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 significantlyreduces 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 usingSystem.ReadOnlyMemory<byte>
over
byte[]
and dont' assume that this memory can be retained and used outside of the scope of the publishingfunction.
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.
GitHub issue: #714
Requires .NET Framework 4.6.1 or .NET Standard 2.0
The client now requires .NET Framework 4.6.1 or .NET Standard 2.0. Earlier versions are no longer
supported.
GitHub issue: #686
Microsoft.Diagnostics.Tracing.EventSource
Dependency DroppedMicrosoft.Diagnostics.Tracing.EventSource
dependency has been removed. It was an annoyingdependency to have for some environments.
Source Linking
The library now supports source linking.
GitHub issue: #697
NuGet Source Packages
Source packages are now also distributed via NuGet.
CRL Checks for Server x.509 (TLS) Certificates
Added a TLS option to enforce CRL checks for server certificates.
GitHub issue: #500
v5.1.2
Please see the milestone for all changes:
GitHub
5.2.0
MilestoneSelected highlights:
Add support for
netstandard2.0
GitHub issues: #428, #435
Re-introduce lock for all socket writes
GitHub PR: rabbitmq-dotnet-client#702
v5.1.1
Bump System.Net.Security to 4.3.2
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.