Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency django-anymail to v12 #207

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 4, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
django-anymail (changelog) 10.3 -> 12.0 age adoption passing confidence

Release Notes

anymail/django-anymail (django-anymail)

v12.0

Compare Source

2024-09-09

Breaking changes


* Require **Django 4.0 or later** and Python 3.8 or later.

Features
~~~~~~~~

* **Resend:** Add support for ``send_at``.

Fixes
~~~~~

* **Unisender Go:** Fix several problems in Anymail's Unisender Go status tracking
  webhook. Rework signature checking to fix false validation errors (particularly
  on "clicked" and "opened" events). Properly handle "use single event" webhook
  option. Correctly verify WEBHOOK_SECRET when set. Provide Unisender Go's
  ``delivery_status`` code and unsubscribe form ``comment`` in Anymail's
  ``event.description``. Treat soft bounces as "deferred" rather than "bounced".
  (Thanks to `@MikeVL`_ for fixing the signature validation problem.)

Other
~~~~~

* **Mandrill (docs):** Explain how ``cc`` and ``bcc`` handling depends on
  Mandrill's "preserve recipients" option. (Thanks to `@dgilmanAIDENTIFIED`_
  for reporting the issue.)

* **Postal (docs):** Update links to Postal's new documentation site.
  (Thanks to `@jmduke`_.)

v11.1

Compare Source

2024-08-07

Features


* **Brevo:** Support Brevo's new "Complaint," "Error" and "Loaded by proxy"
  tracking events. (Thanks to `@originell`_ for the update.)

Deprecations
  • This will be the last Anymail release to support Django 3.0, 3.1 and 3.2
    (which reached end of extended support on 2021-04-06, 2021-12-07 and
    2024-04-01, respectively).

  • This will be the last Anymail release to support Python 3.7 (which reached
    end-of-life on 2023-06-27, and is not supported by Django 4.0 or later).

v11.0.1

Compare Source

2024-07-11

(This release updates only documentation and package metadata; the code is
identical to v11.0.)

Fixes


* **Amazon SES (docs):** Correct IAM policies required for using
  the Amazon SES v2 API. See
  `Migrating to the SES v2 API <https://anymail.dev/en/stable/esps/amazon_ses/#amazon-ses-v2>`__.
  (Thanks to `@scur-iolus`_ for identifying the problem.)

v11.0

Compare Source

2024-07-11

(This release updates only documentation and package metadata; the code is
identical to v11.0.)

Fixes


* **Amazon SES (docs):** Correct IAM policies required for using
  the Amazon SES v2 API. See
  `Migrating to the SES v2 API <https://anymail.dev/en/stable/esps/amazon_ses/#amazon-ses-v2>`__.
  (Thanks to `@scur-iolus`_ for identifying the problem.)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Jan 30, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
[14:42:13.468] INFO (1132): Installing tool [email protected]...
installing v2 tool python v3.13.1
Checksum does not match for file /tmp/renovate/cache/containerbase/3fc676f094c91febdecbd8a83b25155a210b97c0f16f2ad6b3399155ca4f57af/python-3.13.1-jammy-x86_64.tar.xz. Expected: 3adb4c9570439b8473906dc9e15bd48c07b39ad86fcbe865fdca4626baf3a5f5915aae541ba38fd6bb646e84468fdc2fd59175728887c4cb1383a8c571b6765c - Got: cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e
Cached file is corrupt, redownloading: /tmp/renovate/cache/containerbase/3fc676f094c91febdecbd8a83b25155a210b97c0f16f2ad6b3399155ca4f57af/python-3.13.1-jammy-x86_64.tar.xz
Download failed: https://github.com/containerbase/python-prebuild/releases/download/3.13.1/python-3.13.1-jammy-x86_64.tar.xz
Download failed, retrying
Download failed: https://github.com/containerbase/python-prebuild/releases/download/3.13.1/python-3.13.1-jammy-x86_64.tar.xz
Download failed, retrying
Download failed: https://github.com/containerbase/python-prebuild/releases/download/3.13.1/python-3.13.1-jammy-x86_64.tar.xz
Download failed: https://github.com/containerbase/python-prebuild/releases/download/3.13.1/python-3.13.1-jammy-x86_64.tar.xz
[14:42:22.502] INFO (1222): Downloading file ...
    url: "https://github.com/containerbase/python-prebuild/releases/download/3.13.1/python-3.13.1-jammy-x86_64.tar.xz"
    output: "/tmp/renovate/cache/containerbase/3fc676f094c91febdecbd8a83b25155a210b97c0f16f2ad6b3399155ca4f57af/python-3.13.1-jammy-x86_64.tar.xz"
[14:42:22.574] ERROR (1222): Response code 504 (Gateway Time-out)
[14:42:22.575] FATAL (1222): Download failed in 73ms.
[14:42:22.630] ERROR (1132): Command failed with exit code 1: /usr/local/containerbase/bin/install-tool.sh python 3.13.1
[14:42:22.631] FATAL (1132): Install tool python failed in 9.1s.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants