From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Mon, 16 Jun 2025 18:02:26 +0000 (-0400)
Subject: changelog edits
X-Git-Tag: rel_1_16_2~1
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a3eb3863dca7a80d50964c0298a356e75526cefd;p=thirdparty%2Fsqlalchemy%2Falembic.git

changelog edits

Change-Id: I5bd111c1a2110bb6c386d40295836aae87922c32
---

diff --git a/docs/build/unreleased/1671.rst b/docs/build/unreleased/1671.rst
new file mode 100644
index 00000000..dc0d5fb1
--- /dev/null
+++ b/docs/build/unreleased/1671.rst
@@ -0,0 +1,10 @@
+.. change::
+    :tags: bug, autogenerate
+    :tickets: 1671
+
+    Fixed issue where dialect-specific keyword arguments in ``dialect_kwargs``
+    were not rendered when rendering the :meth:`.Operations.create_foreign_key`
+    operation.   This prevented dialect-specific keywords from being rendered
+    using custom :class:`.Rewriter` recipes that modify
+    :class:`.ops.CreateForeignKeyOp`, similar to other issues such as
+    :ticket:`1635`.  Pull request courtesy Justin Malin.
diff --git a/docs/build/unreleased/1672.rst b/docs/build/unreleased/1672.rst
deleted file mode 100644
index 0c636bb8..00000000
--- a/docs/build/unreleased/1672.rst
+++ /dev/null
@@ -1,10 +0,0 @@
-.. change::
-    :tags: usecase, operations
-    :tickets: 1671
-    Fixed an issue where dialect-specific keyword arguments, dialect_kwargs, were
-    not passed through when using the op.create_foreign_key() operation. This
-    prevented the use of backend-specific foreign key options, such as
-    postgresql_not_valid for PostgreSQL constraints. The renderer for
-    ops.CreateForeignKeyOp now correctly includes these arguments, aligning its
-    behavior with other constraint operations.
-    Pull request courtesy of Justin Malin.