[1.7.x] Fixed #23365 -- Added support for timezone-aware datetimes to migrations.

Backport of a407b846b4 from master

2 files changed, 7 insertions, 0 deletions

diff --git a/docs/releases/1.7.1.txt b/docs/releases/1.7.1.txt
index 01edc4c8f5..68370dd44a 100644
--- a/docs/releases/1.7.1.txt
+++ b/docs/releases/1.7.1.txt
@@ -106,3 +106,5 @@ Bugfixes
 
 * Made :func:`~django.utils.http.urlsafe_base64_decode` return the proper
   type (byte string) on Python 3 (:ticket:`23333`).
+
+* :djadmin:`makemigrations` can now serialize timezone-aware values (:ticket:`23365`).
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 739e8ed165..1321d5908d 100755
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -536,12 +536,17 @@ Django can serialize the following:
 - ``int``, ``long``, ``float``, ``bool``, ``str``, ``unicode``, ``bytes``, ``None``
 - ``list``, ``set``, ``tuple``, ``dict``
 - ``datetime.date``, ``datetime.time``, and ``datetime.datetime`` instances
+  (include those that are timezone-aware)
 - ``decimal.Decimal`` instances
 - Any Django field
 - Any function or method reference (e.g. ``datetime.datetime.today``) (must be in module's top-level scope)
 - Any class reference (must be in module's top-level scope)
 - Anything with a custom ``deconstruct()`` method (:ref:`see below <custom-deconstruct-method>`)
 
+.. versionchanged:: 1.7.1
+
+    Support for serializing timezone-aware datetimes was added.
+
 Django can serialize the following on Python 3 only:
 
 - Unbound methods used from within the class body (see below)