Bump RabbitMQ.Client from 5.1.0 to 6.2.2

[dependabot-preview]

Bumps RabbitMQ.Client from 5.1.0 to 6.2.2.

Release notes

Sourced from RabbitMQ.Client's releases.

6.2.1

Changes Between 6.1.0 and 6.2.1

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

6.1.0

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.

6.0.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

... (truncated)

Changelog

Sourced from RabbitMQ.Client's changelog.

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)

... (truncated)

Commits

• 89237f2 Merge pull request #1053 from GitHubPang/patch-1
• a6872cd Bump APIApproval test dependencies
• ed1bb6a Revert "Update APIApproval expectations"
• cfee834 Update APIApproval expectations
• 74bb090 Merge branch 'pierresetteskog-feature/always-recover-all-consumers' into 6.x
• ca6c39f Wording
• 348141e better log information
• 5a873e4 abort autorecovery if topology cant be recovered because of connection problem
• 84ec099 make HandleTopologyRecoveryException throw exception brcause of all consumers...
• f8fa8c3 Merge pull request #1040 from StevenBonePgh/patch-1
• 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)