From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Tue, 10 Feb 2026 15:57:53 +0000 (-0500)
Subject: - 1.18.4
X-Git-Tag: rel_1_18_4
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=766b5ee98e0aeea85a18f272a1ac813712ee0697;p=thirdparty%2Fsqlalchemy%2Falembic.git

- 1.18.4
---

diff --git a/docs/build/changelog.rst b/docs/build/changelog.rst
index d259ab5a..6e45f7e0 100644
--- a/docs/build/changelog.rst
+++ b/docs/build/changelog.rst
@@ -5,7 +5,32 @@ Changelog
 
 .. changelog::
     :version: 1.18.4
-    :include_notes_from: unreleased
+    :released: February 10, 2026
+
+    .. change::
+        :tags: bug, operations
+        :tickets: 1232
+
+        Reverted the behavior of :meth:`.Operations.add_column` that would
+        automatically render the "PRIMARY KEY" keyword inline when a
+        :class:`.Column` with ``primary_key=True`` is added. The automatic
+        behavior, added in version 1.18.2, is now opt-in via the new
+        :paramref:`.Operations.add_column.inline_primary_key` parameter. This
+        change restores the ability to render a PostgreSQL SERIAL column, which is
+        required to be ``primary_key=True``, while not impacting the ability to
+        render a separate primary key constraint. This also provides consistency
+        with the :paramref:`.Operations.add_column.inline_references` parameter and
+        gives users explicit control over SQL generation.
+
+        To render PRIMARY KEY inline, use the
+        :paramref:`.Operations.add_column.inline_primary_key` parameter set to
+        ``True``::
+
+            op.add_column(
+                "my_table",
+                Column("id", Integer, primary_key=True),
+                inline_primary_key=True
+            )
 
 .. changelog::
     :version: 1.18.3
diff --git a/docs/build/conf.py b/docs/build/conf.py
index 2ed6f334..127a5ec7 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.3"
-release_date = "January 29, 2026"
+release = "1.18.4"
+release_date = "February 10, 2026"
 
 
 # The language for content autogenerated by Sphinx. Refer to documentation
diff --git a/docs/build/unreleased/1232_amendment.rst b/docs/build/unreleased/1232_amendment.rst
deleted file mode 100644
index c83644ea..00000000
--- a/docs/build/unreleased/1232_amendment.rst
+++ /dev/null
@@ -1,24 +0,0 @@
-.. change::
-    :tags: bug, operations
-    :tickets: 1232
-
-    Reverted the behavior of :meth:`.Operations.add_column` that would
-    automatically render the "PRIMARY KEY" keyword inline when a
-    :class:`.Column` with ``primary_key=True`` is added. The automatic
-    behavior, added in version 1.18.2, is now opt-in via the new
-    :paramref:`.Operations.add_column.inline_primary_key` parameter. This
-    change restores the ability to render a PostgreSQL SERIAL column, which is
-    required to be ``primary_key=True``, while not impacting the ability to
-    render a separate primary key constraint. This also provides consistency
-    with the :paramref:`.Operations.add_column.inline_references` parameter and
-    gives users explicit control over SQL generation.
-
-    To render PRIMARY KEY inline, use the
-    :paramref:`.Operations.add_column.inline_primary_key` parameter set to
-    ``True``::
-
-        op.add_column(
-            "my_table",
-            Column("id", Integer, primary_key=True),
-            inline_primary_key=True
-        )