Bump RabbitMQ.Client from 5.1.2 to 6.1.0

[dependabot-preview]

Bumps RabbitMQ.Client from 5.1.2 to 6.1.0.

Release notes

Sourced from RabbitMQ.Client's releases.

4.0 RC1

4.0 RC1 is a release candidate release for version 4.0

Changes

• dotnet core support: GitHub issue: rabbitmq-dotnet-client#148
• IHostnameSelector replaced by IEndpointResolver: GitHub issue: rabbitmq-dotnet-client#195
• Use optionals. GitHub issue: rabbitmq-dotnet-client#125
• Make Hostname a property. GitHub issue: rabbitmq-dotnet-client#217

Changelog

Sourced from RabbitMQ.Client's changelog.

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.

GitHub issue: #714

... (truncated)

Commits

• 9f0cdf8 Merge pull request #854 from bollhals/simplify.missed.heartbeat
• 56bd745 The "_site" submodule must point to the gh-pages branch of this repo
• f4d7b2e Merge branch 'bollhals-minor.improvements'
• 24076c0 Merge pull request #851 from stebet/netstandardBinaryPrimitives
• e0d8269 Merge pull request #849 from bollhals/throwOnLongStringKey
• 344ce71 Merge pull request #850 from stebet/preserveStacktraces
• 595ac87 Merge pull request #844 from stebet/frameOptimizations
• ce9b039 Merge pull request #848 from bollhals/reduce.allocation
• dee726a Merge pull request #847 from Pliner/remove-unreachable-code
• 1f80b1e Merge pull request #845 from bollhals/simplify.write.string
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)