From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Mon, 14 Mar 2022 19:39:01 +0000 (-0400)
Subject: - 1.7.7
X-Git-Tag: rel_1_7_7
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7b55158fee2efd437f1f462c1730cb47fb25a259;p=thirdparty%2Fsqlalchemy%2Falembic.git

- 1.7.7
---

diff --git a/docs/build/changelog.rst b/docs/build/changelog.rst
index 7538d37d..5bd9a032 100644
--- a/docs/build/changelog.rst
+++ b/docs/build/changelog.rst
@@ -5,7 +5,41 @@ Changelog
 
 .. changelog::
     :version: 1.7.7
-    :include_notes_from: unreleased
+    :released: March 14, 2022
+
+    .. change::
+        :tags: bug, operations
+        :tickets: 1004
+
+        Fixed issue where using :meth:`.Operations.create_table` in conjunction
+        with a :class:`.CheckConstraint` that referred to table-bound
+        :class:`.Column` objects rather than string expressions would be added to
+        the parent table potentially multiple times, resulting in an incorrect DDL
+        sequence. Pull request courtesy Nicolas CANIART.
+
+    .. change::
+        :tags: bug, environment
+        :tickets: 986
+
+        The ``logging.fileConfig()`` line in ``env.py`` templates, which is used
+        to setup Python logging for the migration run, is now conditional on
+        :attr:`.Config.config_file_name` not being ``None``.  Otherwise, the line
+        is skipped as there is no default logging configuration present.
+
+
+    .. change::
+        :tags: bug, mssql
+        :tickets: 977
+
+        Fixed bug where an :meth:`.Operations.alter_column` operation would change
+        a "NOT NULL" column to "NULL" by emitting an ALTER COLUMN statement that
+        did not specify "NOT NULL". (In the absence of "NOT NULL" T-SQL was
+        implicitly assuming "NULL"). An :meth:`.Operations.alter_column` operation
+        that specifies :paramref:`.Operations.alter_column.type` should also
+        specify include either :paramref:`.Operations.alter_column.nullable` or
+        :paramref:`.Operations.alter_column.existing_nullable` to inform Alembic as
+        to whether the emitted DDL should include "NULL" or "NOT NULL"; a warning
+        is now emitted if this is missing under this scenario.
 
 .. changelog::
     :version: 1.7.6
diff --git a/docs/build/conf.py b/docs/build/conf.py
index dd984622..d9449d49 100644
--- a/docs/build/conf.py
+++ b/docs/build/conf.py
@@ -92,8 +92,8 @@ copyright = u"2010-2022, Mike Bayer"  # noqa
 # The short X.Y version.
 version = alembic.__version__
 # The full version, including alpha/beta/rc tags.
-release = "1.7.6"
-release_date = "February 1, 2022"
+release = "1.7.7"
+release_date = "March 14, 2022"
 
 
 # The language for content autogenerated by Sphinx. Refer to documentation
diff --git a/docs/build/unreleased/1004.rst b/docs/build/unreleased/1004.rst
deleted file mode 100644
index d629306b..00000000
--- a/docs/build/unreleased/1004.rst
+++ /dev/null
@@ -1,9 +0,0 @@
-.. change::
-    :tags: bug, operations
-    :tickets: 1004
-
-    Fixed issue where using :meth:`.Operations.create_table` in conjunction
-    with a :class:`.CheckConstraint` that referred to table-bound
-    :class:`.Column` objects rather than string expressions would be added to
-    the parent table potentially multiple times, resulting in an incorrect DDL
-    sequence. Pull request courtesy Nicolas CANIART.
diff --git a/docs/build/unreleased/977.rst b/docs/build/unreleased/977.rst
deleted file mode 100644
index 91fb76ac..00000000
--- a/docs/build/unreleased/977.rst
+++ /dev/null
@@ -1,13 +0,0 @@
-.. change::
-    :tags: bug, mssql
-    :tickets: 977
-
-    Fixed bug where an :meth:`.Operations.alter_column` operation would change
-    a "NOT NULL" column to "NULL" by emitting an ALTER COLUMN statement that
-    did not specify "NOT NULL". (In the absence of "NOT NULL" T-SQL was
-    implicitly assuming "NULL"). An :meth:`.Operations.alter_column` operation
-    that specifies :paramref:`.Operations.alter_column.type` should also
-    specify include either :paramref:`.Operations.alter_column.nullable` or
-    :paramref:`.Operations.alter_column.existing_nullable` to inform Alembic as
-    to whether the emitted DDL should include "NULL" or "NOT NULL"; a warning
-    is now emitted if this is missing under this scenario.
diff --git a/docs/build/unreleased/986.rst b/docs/build/unreleased/986.rst
deleted file mode 100644
index a1b48cc5..00000000
--- a/docs/build/unreleased/986.rst
+++ /dev/null
@@ -1,9 +0,0 @@
-.. change::
-    :tags: bug, environment
-    :tickets: 986
-
-    The ``logging.fileConfig()`` line in ``env.py`` templates, which is used
-    to setup Python logging for the migration run, is now conditional on
-    :attr:`.Config.config_file_name` not being ``None``.  Otherwise, the line
-    is skipped as there is no default logging configuration present.
-