From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Thu, 29 Jan 2026 20:23:20 +0000 (-0500)
Subject: - 1.18.3
X-Git-Tag: rel_1_18_3
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d3f66e6b769eeeddae220a348d767890a4ea2c4b;p=thirdparty%2Fsqlalchemy%2Falembic.git

- 1.18.3
---

diff --git a/docs/build/changelog.rst b/docs/build/changelog.rst
index 041f9dcb..b32fd57a 100644
--- a/docs/build/changelog.rst
+++ b/docs/build/changelog.rst
@@ -5,7 +5,46 @@ Changelog
 
 .. changelog::
     :version: 1.18.3
-    :include_notes_from: unreleased
+    :released: January 29, 2026
+
+    .. change::
+        :tags: bug, autogenerate
+        :tickets: 1787
+
+        Fixed regression in version 1.18.0 due to :ticket:`1771` where autogenerate
+        would raise ``NoReferencedTableError`` when a foreign key constraint
+        referenced a table that was not part of the initial table load, including
+        tables filtered out by the
+        :paramref:`.EnvironmentContext.configure.include_name` callable or tables
+        in remote schemas that were not included in the initial reflection run.
+
+        The change in :ticket:`1771` was a performance optimization that eliminated
+        additional reflection queries for tables that were only referenced by
+        foreign keys but not explicitly included in the main reflection run.
+        However, this optimization inadvertently removed the creation of
+        :class:`.Table` objects for these referenced tables, causing autogenerate
+        to fail when processing foreign key constraints that pointed to them.
+
+        The fix creates placeholder :class:`.Table` objects for foreign key targets
+        that are not reflected, allowing the autogenerate comparison to proceed
+        without error while maintaining the performance improvement from
+        :ticket:`1771`. When multiple foreign keys reference different columns in
+        the same filtered table, the placeholder table accumulates all necessary
+        columns. These placeholder tables may be visible when using the
+        :paramref:`.EnvironmentContext.configure.include_object` callable to
+        inspect :class:`.ForeignKeyConstraint` objects; they will have the name,
+        schema and basic column information for the relevant columns present.
+
+    .. change::
+        :tags: bug, general
+        :tickets: 1788
+
+        Fixed regression caused by :ticket:`1669` which requires SQLAlchemy objects
+        to support generic type subscripting; for the older SQLAlchemy 1.4 series,
+        this requires version 1.4.23.  Changed the minimum requirements to require
+        version 1.4.23 rather than 1.4.0.
+
+
 
 .. changelog::
     :version: 1.18.2
diff --git a/docs/build/conf.py b/docs/build/conf.py
index 9c288d80..2ed6f334 100644
--- a/docs/build/conf.py
+++ b/docs/build/conf.py
@@ -101,8 +101,8 @@ author = "Mike Bayer"
 # The short X.Y version.
 version = alembic.__version__
 # The full version, including alpha/beta/rc tags.
-release = "1.18.2"
-release_date = "January 28, 2026"
+release = "1.18.3"
+release_date = "January 29, 2026"
 
 
 # The language for content autogenerated by Sphinx. Refer to documentation
diff --git a/docs/build/unreleased/1787.rst b/docs/build/unreleased/1787.rst
deleted file mode 100644
index 09daa532..00000000
--- a/docs/build/unreleased/1787.rst
+++ /dev/null
@@ -1,27 +0,0 @@
-.. change::
-    :tags: bug, autogenerate
-    :tickets: 1787
-
-    Fixed regression in version 1.18.0 due to :ticket:`1771` where autogenerate
-    would raise ``NoReferencedTableError`` when a foreign key constraint
-    referenced a table that was not part of the initial table load, including
-    tables filtered out by the
-    :paramref:`.EnvironmentContext.configure.include_name` callable or tables
-    in remote schemas that were not included in the initial reflection run.
-
-    The change in :ticket:`1771` was a performance optimization that eliminated
-    additional reflection queries for tables that were only referenced by
-    foreign keys but not explicitly included in the main reflection run.
-    However, this optimization inadvertently removed the creation of
-    :class:`.Table` objects for these referenced tables, causing autogenerate
-    to fail when processing foreign key constraints that pointed to them.
-
-    The fix creates placeholder :class:`.Table` objects for foreign key targets
-    that are not reflected, allowing the autogenerate comparison to proceed
-    without error while maintaining the performance improvement from
-    :ticket:`1771`. When multiple foreign keys reference different columns in
-    the same filtered table, the placeholder table accumulates all necessary
-    columns. These placeholder tables may be visible when using the
-    :paramref:`.EnvironmentContext.configure.include_object` callable to
-    inspect :class:`.ForeignKeyConstraint` objects; they will have the name,
-    schema and basic column information for the relevant columns present.
diff --git a/docs/build/unreleased/1788.rst b/docs/build/unreleased/1788.rst
deleted file mode 100644
index 6e19d23d..00000000
--- a/docs/build/unreleased/1788.rst
+++ /dev/null
@@ -1,10 +0,0 @@
-.. change::
-    :tags: bug, general
-    :tickets: 1788
-
-    Fixed regression caused by :ticket:`1669` which requires SQLAlchemy objects
-    to support generic type subscripting; for the older SQLAlchemy 1.4 series,
-    this requires version 1.4.23.  Changed the minimum requirements to require
-    version 1.4.23 rather than 1.4.0.
-
-