Bump amqp-client from 5.0.0 to 5.4.0

[dependabot[bot]]

trafficstars

Bumps amqp-client from 5.0.0 to 5.4.0.

Release notes

Sourced from amqp-client's releases.

5.4.0

This is a maintenance release with new features and bug fixes. All users of the 5.x.x series are encouraged to use this version.

Note that as of this release, default DNS resolution on the server hostname is disabled when using TLS (#400). This avoids interfering with hostname verification (#394). DNS resolution can be easily re-enabled by passing in a DnsRecordIpAddressResolver instance to one the ConnectionFactory#newConnection methods.

Thanks to @​vikinghawk for his contribution on this release.

Changes between 5.3.0 and 5.4.0

Make it easier to enable hostname verification when TLS is enabled

GitHub issue: #394

Disable DNS resolution when using TLS

GitHub issue: #400

Add filter to skip some entities on topology recovery

GitHub issue: #383

Add optional retry logic to topology recovery

GitHub issue: #387

Address parser is incapable of handling IPv6 address literals

GitHub issue: #385

Add option for connection recovery triggering

GitHub issue: #379

Continuations (requests) are not discarded on timeouts

GitHub issue: #375

Backport publishing metrics

GitHub issue: #374

Add equals and hashCode to generated classes

GitHub issue: #377

Improve JSON RPC support by using Jackson

GitHub issue: #378

Add dedicated executor to close connections in NIO mode

... (truncated)

Commits

• 7f527b5 [maven-release-plugin] prepare release v5.4.0
• b18bcab Update snapshot version in release file
• b8f0440 Set release version to 5.4.0
• 714c878 Set release version to 5.4.0.RC4
• 6e51a37 [maven-release-plugin] prepare for next development iteration
• de58023 [maven-release-plugin] prepare release v5.4.0.RC3
• b24a9be Merge pull request #403 from vikinghawk/5.x.x-stable
• b88f7f5 was logging the wrong exception
• 9b5adbe tweaks to recovery retry helper
• 8b8c58a Set release version to 5.4.0.RC3
• 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

You can disable automated security fix PRs for this repo from the Security Alerts page.