- 1.5.3

diff --git a/docs/build/changelog.rst b/docs/build/changelog.rst
index e3c5d7702d8f3442bd58b5e9de6d87215be381cd..13b37555367055e7d5b5ce29f0a66e46b6ef672a 100644 (file)
--- a/docs/build/changelog.rst
+++ b/docs/build/changelog.rst
@@ -5,7 +5,36 @@ Changelog
 
 .. changelog::
     :version: 1.5.3
-    :include_notes_from: unreleased
+    :released: January 29, 2021
+
+    .. change::
+        :tags: bug, autogenerate
+        :tickets: 786
+
+        Changed the default ordering of "CREATE" and "DROP" statements indexes and
+        unique constraints within the autogenerate process, so that for example in
+        an upgrade() operation, a particular index or constraint that is to be
+        replaced such as for a casing convention change will not produce any naming
+        conflicts. For foreign key constraint objects, this is already how
+        constraints are ordered, and for table objects, users would normally want
+        to use :meth:`.Operations.rename_table` in any case.
+
+    .. change::
+        :tags: bug, autogenerate, mssql
+        :tickets: 787
+
+        Fixed assorted autogenerate issues with SQL Server:
+
+        * ignore default reflected identity on primary_key columns
+        * improve server default comparison
+
+    .. change::
+        :tags: bug, mysql, autogenerate
+        :tickets: 788
+
+        Fixed issue where autogenerate rendering of ``op.alter_column()`` would
+        fail to include MySQL ``existing_nullable=False`` if the column were part
+        of a primary key constraint within the table metadata.
 
 .. changelog::
     :version: 1.5.2

diff --git a/docs/build/conf.py b/docs/build/conf.py
index 7b16edd2b2e671536a42c0bfcb4f93b4b9625337..8a2c82c1ea8ff1cb914efe29a770041d7bdb1301 100644 (file)
--- a/docs/build/conf.py
+++ b/docs/build/conf.py
@@ -85,8 +85,8 @@ copyright = u"2010-2021, Mike Bayer"  # noqa
 # The short X.Y version.
 version = alembic.__version__
 # The full version, including alpha/beta/rc tags.
-release = "1.5.2"
-release_date = "January 20, 2021"
+release = "1.5.3"
+release_date = "January 29, 2021"
 
 
 # The language for content autogenerated by Sphinx. Refer to documentation

diff --git a/docs/build/unreleased/786.rst b/docs/build/unreleased/786.rst
deleted file mode 100644 (file)
index fea1a37..0000000
--- a/docs/build/unreleased/786.rst
+++ /dev/null
@@ -1,11 +0,0 @@
-.. change::
-    :tags: bug, autogenerate
-    :tickets: 786
-
-    Changed the default ordering of "CREATE" and "DROP" statements indexes and
-    unique constraints within the autogenerate process, so that for example in
-    an upgrade() operation, a particular index or constraint that is to be
-    replaced such as for a casing convention change will not produce any naming
-    conflicts. For foreign key constraint objects, this is already how
-    constraints are ordered, and for table objects, users would normally want
-    to use :meth:`.Operations.rename_table` in any case.

diff --git a/docs/build/unreleased/787.rst b/docs/build/unreleased/787.rst
deleted file mode 100644 (file)
index 90fce9a..0000000
--- a/docs/build/unreleased/787.rst
+++ /dev/null
@@ -1,8 +0,0 @@
-.. change::
-    :tags: bug, autogenerate, mssql
-    :tickets: 787
-
-    Fixed assorted autogenerate issues with SQL Server:
-
-    * ignore default reflected identity on primary_key columns
-    * improve server default comparison

diff --git a/docs/build/unreleased/788.rst b/docs/build/unreleased/788.rst
deleted file mode 100644 (file)
index 6844cea..0000000
--- a/docs/build/unreleased/788.rst
+++ /dev/null
@@ -1,7 +0,0 @@
-.. change::
-    :tags: bug, mysql, autogenerate
-    :tickets: 788
-
-    Fixed issue where autogenerate rendering of ``op.alter_column()`` would
-    fail to include MySQL ``existing_nullable=False`` if the column were part
-    of a primary key constraint within the table metadata.