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

Bump django-anymail[postmark] from 10.0 to 11.1 #1623

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 8, 2024

Bumps django-anymail[postmark] from 10.0 to 11.1.

Release notes

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

v11.1

Changelog

v11.0.1

Changelog

(This release is solely to update documentation and metadata. Code is identical to v11.0.)

v11.0

  • Breaking changes for Amazon SES; SparkPost (with template_id)
  • New merge_headers feature
  • And more…

Please check the changelog

v10.3

Changelog

v10.2

Changelog

v10.1

Changelog

Changelog

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

v11.1

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

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

2024-06-23

Breaking changes

  • Amazon SES: Drop support for the Amazon SES v1 API. If your EMAIL_BACKEND setting uses amazon_sesv1, or if you are upgrading from Anymail 9.x or earlier directly to 11.0 or later, see

... (truncated)

Commits
  • 6cb1a8b Release 11.1
  • 53dcc1e Docs: note inbound attachments doesn't include inlines
  • 13fa505 CI/CD: Support Django 5.1 release
  • d05f448 Brevo: support proxy open, complained, error events
  • 5e689cd Postal: use larger key for webhook tests
  • e700ac9 Help automated tools recognize BSD 3-Clause License
  • 136ba59 Release 11.0.1
  • 2403171 CI-CD: Fix gh release target
  • f86c019 Docs: Amazon SES: fix IAM policy recommendations
  • 2d9ca13 Docs: update third-party template packages
  • Additional commits viewable in compare view

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [django-anymail[postmark]](https://github.com/anymail/django-anymail) from 10.0 to 11.1.
- [Release notes](https://github.com/anymail/django-anymail/releases)
- [Changelog](https://github.com/anymail/django-anymail/blob/main/CHANGELOG.rst)
- [Commits](anymail/django-anymail@v10.0...v11.1)

---
updated-dependencies:
- dependency-name: django-anymail[postmark]
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Aug 8, 2024
Copy link

codecov bot commented Aug 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.00%. Comparing base (24277af) to head (d228dd7).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1623   +/-   ##
=======================================
  Coverage   78.00%   78.00%           
=======================================
  Files          69       69           
  Lines        2251     2251           
=======================================
  Hits         1756     1756           
  Misses        495      495           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 10, 2024

Superseded by #1638.

@dependabot dependabot bot closed this Sep 10, 2024
@dependabot dependabot bot deleted the dependabot/pip/django-anymail-postmark--11.1 branch September 10, 2024 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants