Release 8.6

Author: medmunds

CHANGELOG.rst

@@ -25,10 +25,13 @@ Release history
 ^^^^^^^^^^^^^^^
     ..  This extra heading level keeps the ToC from becoming unmanageably long
 
-vNext
------
+v8.6 LTS
+--------
+
+*2022-05-15*
 
-*Unreleased changes in main branch*
+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
 ~~~~~
@@ -42,11 +45,10 @@ Fixes
   Anymail documentation now recommends using Mailgun's and SendGrid's "raw MIME"
   inbound options, which avoid the problem and preserve all attachments.
 
-  See `Mailgun inbound <https://anymail.readthedocs.io/en/latest/esps/mailgun/#mailgun-inbound>`__
-  and `SendGrid inbound <https://anymail.readthedocs.io/en/latest/esps/sendgrid/#sendgrid-inbound>`__
+  See `Mailgun inbound <https://anymail.readthedocs.io/en/stable/esps/mailgun/#mailgun-inbound>`__
+  and `SendGrid inbound <https://anymail.readthedocs.io/en/stable/esps/sendgrid/#sendgrid-inbound>`__
   for details. (Thanks to `@erikdrums`_ for reporting and helping investigate the problem.)
 
-
 Other
 ~~~~~
 
@@ -57,6 +59,16 @@ Other
 * **Mandrill:** Document Mandrill's incorrect handling of non-ASCII attachment filenames.
   (Thanks to `@Thorbenl`_ for reporting the issue and following up with MailChimp.)
 
+* Documentation (for all releases) is now hosted at anymail.dev (moved from anymail.info).
+
+Deprecations
+~~~~~~~~~~~~
+
+*  This will be the last Anymail release to support Django 2.0--2.2 and Python 3.5.
+
+If these deprecations affect you and you cannot upgrade, set your requirements to
+`django-anymail~=8.6` (a "compatible release" specifier, equivalent to `>=8.6,==8.*`).
+
 
 v8.5
 ----

anymail/_version.py

@@ -1,3 +1,3 @@
-VERSION = (8, 5)
+VERSION = (8, 6)
 __version__ = '.'.join([str(x) for x in VERSION])  # major.minor.patch or major.minor.devN
 __minor_version__ = '.'.join([str(x) for x in VERSION[:2]])  # Sphinx's X.Y "version"

docs/esps/mailgun.rst

@@ -529,7 +529,7 @@ forwarding url) with Mailgun inbound routing.
     To use Mailgun's fully-parsed format, change :samp:`.../inbound_mime/` to just
     :samp:`.../inbound/` at the end of the route forwarding url.
 
-    .. versionchanged:: vNext
+    .. versionchanged:: 8.6
        Using Mailgun's full-parsed (not raw MIME) inbound message format is no longer recommended.
 
 

docs/esps/sendgrid.rst

@@ -443,7 +443,7 @@ incoming emails for spam" checkbox.
     Using raw MIME also avoids a limitation in Django's :mimetype:`multipart/form-data` handling
     that can strip attachments with certain filenames.
 
-    .. versionchanged:: vNext
+    .. versionchanged:: 8.6
        Leaving SendGrid's "full MIME" checkbox disabled is no longer recommended.