Bump amqp from 2.4.2 to 5.0.6 in /api

[dependabot-preview]

Bumps amqp from 2.4.2 to 5.0.6.

Release notes

Sourced from amqp's releases.

v5.0.6

5.0.6

:release-date: 2021-04-01 10:45 A.M. UTC+6:00 :release-by: Asif Saif Uddin

• Change the order in which context.check_hostname and context.verify_mode get set in SSLTransport._wrap_socket_sni. Fixes bug introduced in 5.0.3 where setting context.verify_mode = ssl.CERT_NONE would raise "ValueError: Cannot set verify_mode to CERT_NONE when check_hostname is enabled." Setting context.check_hostname prior to setting context.verify_mode resolves the issue.
• Remove TCP_USER_TIMEOUT option for Solaris (#355)
• Pass long_description to setup() (#353)
• Fix for tox-docker 2.0
• Moved to GitHub actions CI (#359)

v5.0.4

5.0.4

:release-date: 2021-01-28 2:30 P.M UTC+6:00 :release-by: Asif Saif Uddin

• Add missing load_default_certs() call to fix a regression in v5.0.3 release. (#350)

v5.0.3

5.0.3

:release-date: 2021-01-19 9:00 P.M UTC+6:00 :release-by: Asif Saif Uddin

• Change the default value of ssl_version to None. When not set, the proper value between ssl.PROTOCOL_TLS_CLIENT and ssl.PROTOCOL_TLS_SERVER will be selected based on the param server_side in order to create a TLS Context object with better defaults that fit the desired connection side.

• Change the default value of cert_reqs to None. The default value of ctx.verify_mode is ssl.CERT_NONE, but when ssl.PROTOCOL_TLS_CLIENT is used, ctx.verify_mode defaults to ssl.CERT_REQUIRED.

• Fix context.check_hostname logic. Checking the hostname depends on having support of the SNI TLS extension and being provided with a server_hostname value. Another important thing to mention is that enabling hostname checking automatically sets verify_mode from ssl.CERT_NONE to ssl.CERT_REQUIRED in the stdlib ssl and it cannot be set back to ssl.CERT_NONE as long as hostname checking is enabled.

• Refactor the SNI tests to test one thing at a time and removing some tests that were being repeated over and over.

... (truncated)

Changelog

Sourced from amqp's changelog.

5.0.6

:release-date: 2021-04-01 10:45 A.M. UTC+6:00 :release-by: Asif Saif Uddin

• Change the order in which context.check_hostname and context.verify_mode get set in SSLTransport._wrap_socket_sni. Fixes bug introduced in 5.0.3 where setting context.verify_mode = ssl.CERT_NONE would raise "ValueError: Cannot set verify_mode to CERT_NONE when check_hostname is enabled." Setting context.check_hostname prior to setting context.verify_mode resolves the issue.
• Remove TCP_USER_TIMEOUT option for Solaris (#355)
• Pass long_description to setup() (#353)
• Fix for tox-docker 2.0
• Moved to GitHub actions CI (#359)

.. _version-5.0.5:

5.0.5

:release-date: 2021-01-28 4:30 P.M UTC+6:00 :release-by: Asif Saif Uddin

• Removed mistakenly introduced code which was causing import errors

.. _version-5.0.4:

5.0.4

:release-date: 2021-01-28 2:30 P.M UTC+6:00 :release-by: Asif Saif Uddin

• Add missing load_default_certs() call to fix a regression in v5.0.3 release. (#350)

.. _version-5.0.3:

5.0.3

:release-date: 2021-01-19 9:00 P.M UTC+6:00 :release-by: Asif Saif Uddin

• Change the default value of ssl_version to None. When not set, the proper value between ssl.PROTOCOL_TLS_CLIENT and ssl.PROTOCOL_TLS_SERVER will be selected based on the param server_side in order to create a TLS Context object with better defaults that fit the desired connection side.

... (truncated)

Commits

• 4dad914 Bump version: 5.0.5 → 5.0.6
• 70e6557 changelog for py-amqp v5.0.6
• 4eb39c6 Added GitHub actions CI (#359)
• cd7ede9 Fix typos.
• 1f599c7 Fix ordering of context.check_hostname and context.verify_mode so as to not r...
• 137245b Pass long_description to setup() (#353)
• 3db08f6 remove TCP_USER_TIMEOUT option for Solaris
• 5bcae4a Fix for tox-docker 2.0
• d11b276 Bump version: 5.0.4 → 5.0.5
• 8bcd75d added changelog for 5.0.5
• 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)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)