- 1.4.44

diff --git a/doc/build/changelog/changelog_14.rst b/doc/build/changelog/changelog_14.rst
index 69353f9c5ab4ce4f71fe82360f82b14a43352c71..ef0b83c3b4bae522bd318b60a3074cac93fd6237 100644 (file)
--- a/doc/build/changelog/changelog_14.rst
+++ b/doc/build/changelog/changelog_14.rst
@@ -15,7 +15,62 @@ This document details individual issue-level changes made throughout
 
 .. changelog::
     :version: 1.4.44
-    :include_notes_from: unreleased_14
+    :released: November 12, 2022
+
+    .. change::
+        :tags: bug, sql
+        :tickets: 8790
+
+        Fixed critical memory issue identified in cache key generation, where for
+        very large and complex ORM statements that make use of lots of ORM aliases
+        with subqueries, cache key generation could produce excessively large keys
+        that were orders of magnitude bigger than the statement itself. Much thanks
+        to Rollo Konig Brock for their very patient, long term help in finally
+        identifying this issue.
+
+    .. change::
+        :tags: bug, postgresql, mssql
+        :tickets: 8770
+
+        For the PostgreSQL and SQL Server dialects only, adjusted the compiler so
+        that when rendering column expressions in the RETURNING clause, the "non
+        anon" label that's used in SELECT statements is suggested for SQL
+        expression elements that generate a label; the primary example is a SQL
+        function that may be emitting as part of the column's type, where the label
+        name should match the column's name by default. This restores a not-well
+        defined behavior that had changed in version 1.4.21 due to :ticket:`6718`,
+        :ticket:`6710`. The Oracle dialect has a different RETURNING implementation
+        and was not affected by this issue. Version 2.0 features an across the
+        board change for its widely expanded support of RETURNING on other
+        backends.
+
+
+    .. change::
+        :tags: bug, oracle
+
+        Fixed issue in the Oracle dialect where an INSERT statement that used
+        ``insert(some_table).values(...).returning(some_table)`` against a full
+        :class:`.Table` object at once would fail to execute, raising an exception.
+
+    .. change::
+        :tags: bug, tests
+        :tickets: 8793
+
+        Fixed issue where the ``--disable-asyncio`` parameter to the test suite
+        would fail to not actually run greenlet tests and would also not prevent
+        the suite from using a "wrapping" greenlet for the whole suite. This
+        parameter now ensures that no greenlet or asyncio use will occur within the
+        entire run when set.
+
+    .. change::
+        :tags: bug, tests
+
+        Adjusted the test suite which tests the Mypy plugin to accommodate for
+        changes in Mypy 0.990 regarding how it handles message output, which affect
+        how sys.path is interpreted when determining if notes and errors should be
+        printed for particular files. The change broke the test suite as the files
+        within the test directory itself no longer produced messaging when run
+        under the mypy API.
 
 .. changelog::
     :version: 1.4.43

diff --git a/doc/build/changelog/unreleased_14/8770.rst b/doc/build/changelog/unreleased_14/8770.rst
deleted file mode 100644 (file)
index 8968b03..0000000
--- a/doc/build/changelog/unreleased_14/8770.rst
+++ /dev/null
@@ -1,23 +0,0 @@
-.. change::
-    :tags: bug, postgresql, mssql
-    :tickets: 8770
-
-    For the PostgreSQL and SQL Server dialects only, adjusted the compiler so
-    that when rendering column expressions in the RETURNING clause, the "non
-    anon" label that's used in SELECT statements is suggested for SQL
-    expression elements that generate a label; the primary example is a SQL
-    function that may be emitting as part of the column's type, where the label
-    name should match the column's name by default. This restores a not-well
-    defined behavior that had changed in version 1.4.21 due to :ticket:`6718`,
-    :ticket:`6710`. The Oracle dialect has a different RETURNING implementation
-    and was not affected by this issue. Version 2.0 features an across the
-    board change for its widely expanded support of RETURNING on other
-    backends.
-
-
-.. change::
-    :tags: bug, oracle
-
-    Fixed issue in the Oracle dialect where an INSERT statement that used
-    ``insert(some_table).values(...).returning(some_table)`` against a full
-    :class:`.Table` object at once would fail to execute, raising an exception.

diff --git a/doc/build/changelog/unreleased_14/8790.rst b/doc/build/changelog/unreleased_14/8790.rst
deleted file mode 100644 (file)
index a321480..0000000
--- a/doc/build/changelog/unreleased_14/8790.rst
+++ /dev/null
@@ -1,10 +0,0 @@
-.. change::
-    :tags: bug, sql
-    :tickets: 8790
-
-    Fixed critical memory issue identified in cache key generation, where for
-    very large and complex ORM statements that make use of lots of ORM aliases
-    with subqueries, cache key generation could produce excessively large keys
-    that were orders of magnitude bigger than the statement itself. Much thanks
-    to Rollo Konig Brock for their very patient, long term help in finally
-    identifying this issue.

diff --git a/doc/build/changelog/unreleased_14/8793.rst b/doc/build/changelog/unreleased_14/8793.rst
deleted file mode 100644 (file)
index 36f1003..0000000
--- a/doc/build/changelog/unreleased_14/8793.rst
+++ /dev/null
@@ -1,9 +0,0 @@
-.. change::
-    :tags: bug, tests
-    :tickets: 8793
-
-    Fixed issue where the ``--disable-asyncio`` parameter to the test suite
-    would fail to not actually run greenlet tests and would also not prevent
-    the suite from using a "wrapping" greenlet for the whole suite. This
-    parameter now ensures that no greenlet or asyncio use will occur within the
-    entire run when set.

diff --git a/doc/build/changelog/unreleased_14/mypy_fixes.rst b/doc/build/changelog/unreleased_14/mypy_fixes.rst
deleted file mode 100644 (file)
index 32e4f14..0000000
--- a/doc/build/changelog/unreleased_14/mypy_fixes.rst
+++ /dev/null
@@ -1,9 +0,0 @@
-.. change::
-    :tags: bug, tests
-
-    Adjusted the test suite which tests the Mypy plugin to accommodate for
-    changes in Mypy 0.990 regarding how it handles message output, which affect
-    how sys.path is interpreted when determining if notes and errors should be
-    printed for particular files. The change broke the test suite as the files
-    within the test directory itself no longer produced messaging when run
-    under the mypy API.

diff --git a/doc/build/conf.py b/doc/build/conf.py
index 4f9550225bd3119bab2ba136b7e71b06fe272bc7..baa10ab30eb10b25e517aca5350dbb1be767f7dc 100644 (file)
--- a/doc/build/conf.py
+++ b/doc/build/conf.py
@@ -213,9 +213,9 @@ copyright = u"2007-2022, the SQLAlchemy authors and contributors"  # noqa
 # The short X.Y version.
 version = "1.4"
 # The full version, including alpha/beta/rc tags.
-release = "1.4.43"
+release = "1.4.44"
 
-release_date = "November 4, 2022"
+release_date = "November 12, 2022"
 
 site_base = os.environ.get("RTD_SITE_BASE", "https://www.sqlalchemy.org")
 site_adapter_template = "docs_adapter.mako"