chore(deps): bump django-anymail[amazon_ses] from 8.1 to 9.0

[dependabot]

Bumps django-anymail[amazon_ses] from 8.1 to 9.0.

Release notes

Sourced from django-anymail[amazon_ses]'s releases.

v9.0

Changelog

v8.6

Changelog

v8.5

Changelog

v8.4

Changelog

v8.3

Changelog

v8.2

Changelog

Changelog

Sourced from django-anymail[amazon_ses]'s changelog.

v9.0

2022-12-18

Breaking changes

* Require **Django 3.0 or later** and Python 3.6 or later. (For compatibility
  with Django 2.x or Python 3.5, stay on the Anymail `v8.6 LTS`_ extended support
  branch by setting your requirements to `django-anymail~=8.6`.)
Features

* **Sendinblue:** Support delayed sending using Anymail's `send_at` option.
  (Thanks to `@dimitrisor`_ for noting Sendinblue's public beta release
  of this capability.)
* Support customizing the requests.Session for requests-based backends,
  and document how this can be used to mount an adapter that simplifies
  automatic retry logic. (Thanks to `@dgilmanAIDENTIFIED`_.)
* Confirm support for Django 4.1 and resolve deprecation warning regarding
  ``django.utils.timezone.utc``. (Thanks to `@tim-schilling`_.)
Fixes

* **Postmark:** Handle Postmark's SubscriptionChange events as Anymail
  unsubscribe, subscribe, or bounce tracking events, rather than "unknown".
  (Thanks to `@puru02`_ for the fix.)
* **Sendinblue:** Work around recent (unannounced) Sendinblue API change
  that caused "Invalid headers" API error with non-string custom header
  values. Anymail now converts int and float header values to strings.


Other


Test on Python 3.11 with Django development (Django 4.2) branch.

v8.6 LTS
2022-05-15
This is an extended support release. Anymail v8.6 will receive security updates

and fixes for any breaking ESP API changes through at least May, 2023.
Fixes

</tr></table>

</code></pre>

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Commits</summary>
<ul>

<li><a href="https://github.com/anymail/django-anymail/commit/52c7c113125e3e0500db5264779519a3454e8872&quot;&gt;&lt;code&gt;52c7c11&lt;/code&gt;&lt;/a> Release 9.0</li>

<li><a href="https://github.com/anymail/django-anymail/commit/416d7d433c44b8025980a2391c7be8981f4b87e3&quot;&gt;&lt;code&gt;416d7d4&lt;/code&gt;&lt;/a> CI: remove workaround for broken PyPY sqlite release</li>

<li><a href="https://github.com/anymail/django-anymail/commit/07f5d5f224e2a425de415034484a3ae3ac282d97&quot;&gt;&lt;code&gt;07f5d5f&lt;/code&gt;&lt;/a> CI: update action dependencies</li>

<li><a href="https://github.com/anymail/django-anymail/commit/b86613cf15bb33765577493fad2fe8e9247d5895&quot;&gt;&lt;code&gt;b86613c&lt;/code&gt;&lt;/a> Docs: add source repo link to main ToC</li>

<li><a href="https://github.com/anymail/django-anymail/commit/287c2175f44c931c782766ed0afef190785a9818&quot;&gt;&lt;code&gt;287c217&lt;/code&gt;&lt;/a> Sendinblue: Support send_at</li>

<li><a href="https://github.com/anymail/django-anymail/commit/a8cfb2e5eba7454246ac84c26ffe94938c555457&quot;&gt;&lt;code&gt;a8cfb2e&lt;/code&gt;&lt;/a> Fix link to mailjet apikeys</li>

<li><a href="https://github.com/anymail/django-anymail/commit/d37f4ef109bfb3b4a0d3886737474ddfca5e1cde&quot;&gt;&lt;code&gt;d37f4ef&lt;/code&gt;&lt;/a> Fix test workflows (again)</li>

<li><a href="https://github.com/anymail/django-anymail/commit/e9f3444daac63ed89a9267cd73011ade6e1d1ec6&quot;&gt;&lt;code&gt;e9f3444&lt;/code&gt;&lt;/a> Fix test workflows</li>

<li><a href="https://github.com/anymail/django-anymail/commit/681a4afe6b58e23f75922bbd4161083f5cfb8eb9&quot;&gt;&lt;code&gt;681a4af&lt;/code&gt;&lt;/a> Sendinblue: fix &quot;invalid headers&quot; error</li>

<li><a href="https://github.com/anymail/django-anymail/commit/448e8d9d9509044f7d3a91318c3b45769b5a593a&quot;&gt;&lt;code&gt;448e8d9&lt;/code&gt;&lt;/a> Tests: move integration tests to Django 4.1</li>

<li>Additional commits viewable in <a href="https://github.com/anymail/django-anymail/compare/v8.1...v9.0&quot;&gt;compare view</a></li>

</ul>

</details>
<br />



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)