- 1.10.0

diff --git a/docs/build/changelog.rst b/docs/build/changelog.rst
index a36b93e00274e39d567fef9ee49cb5f15f96e4f3..ccf8be9e6394f3cc71ea4991f7e9ce5d7e2fa6c5 100644 (file)
--- a/docs/build/changelog.rst
+++ b/docs/build/changelog.rst
@@ -5,7 +5,57 @@ Changelog
 
 .. changelog::
     :version: 1.10.0
-    :include_notes_from: unreleased
+    :released: March 5, 2023
+
+    .. change::
+        :tags: bug, autogenerate
+        :tickets: 1166
+
+        Fixed issue in index detection where autogenerate change detection would
+        consider indexes with the same columns but with different order as equal,
+        while in general they are not equivalent in how a database will use them.
+
+    .. change::
+        :tags: feature, revisioning
+        :tickets: 760
+
+        Recursive traversal of revision files in a particular revision directory is
+        now supported, by indicating ``recursive_version_locations = true`` in
+        alembic.ini. Pull request courtesy ostr00000.
+
+
+    .. change::
+        :tags: bug, autogenerate, sqlite
+        :tickets: 1165
+
+        Fixed issue where indexes on SQLite which include SQL expressions would not
+        compare correctly, generating false positives under autogenerate. These
+        indexes are now skipped, generating a warning, in the same way that
+        expression-based indexes on PostgreSQL are skipped and generate warnings
+        when SQLAlchemy 1.x installations are in use. Note that reflection of
+        SQLite expression-based indexes continues to not yet be supported under
+        SQLAlchemy 2.0, even though PostgreSQL expression-based indexes have now
+        been implemented.
+
+
+
+    .. change::
+        :tags: bug, mssql
+        :tickets: 1187
+
+        Properly escape constraint name on SQL Server when dropping
+        a column while specifying ``mssql_drop_default=True`` or
+        ``mssql_drop_check=True`` or ``mssql_drop_foreign_key=True``.
+
+
+    .. change::
+        :tags: usecase, autogenerate, postgresql
+
+        Added support for autogenerate comparison of indexes on PostgreSQL which
+        include SQL expressions, when using SQLAlchemy 2.0; the previous warning
+        that such indexes were skipped are removed when the new functionality
+        is in use.  When using SQLAlchemy versions prior to the 2.0 series,
+        the indexes continue to be skipped with a warning.
 
 .. changelog::
     :version: 1.9.4

diff --git a/docs/build/conf.py b/docs/build/conf.py
index e991423e511bb25744bca3a421e47cedad270dd4..6460fc5ff4c550b42452b9e75e7df35361d20e0e 100644 (file)
--- a/docs/build/conf.py
+++ b/docs/build/conf.py
@@ -99,8 +99,8 @@ copyright = "2010-2023, Mike Bayer"  # noqa
 # The short X.Y version.
 version = alembic.__version__
 # The full version, including alpha/beta/rc tags.
-release = "1.9.4"
-release_date = "February 16, 2023"
+release = "1.10.0"
+release_date = "March 5, 2023"
 
 
 # The language for content autogenerated by Sphinx. Refer to documentation

diff --git a/docs/build/unreleased/1165.rst b/docs/build/unreleased/1165.rst
deleted file mode 100644 (file)
index b1dbf15..0000000
--- a/docs/build/unreleased/1165.rst
+++ /dev/null
@@ -1,14 +0,0 @@
-.. change::
-    :tags: bug, autogenerate, sqlite
-    :tickets: 1165
-
-    Fixed issue where indexes on SQLite which include SQL expressions would not
-    compare correctly, generating false positives under autogenerate. These
-    indexes are now skipped, generating a warning, in the same way that
-    expression-based indexes on PostgreSQL are skipped and generate warnings
-    when SQLAlchemy 1.x installations are in use. Note that reflection of
-    SQLite expression-based indexes continues to not yet be supported under
-    SQLAlchemy 2.0, even though PostgreSQL expression-based indexes have now
-    been implemented.
-
-

diff --git a/docs/build/unreleased/1166.rst b/docs/build/unreleased/1166.rst
deleted file mode 100644 (file)
index c9b64b9..0000000
--- a/docs/build/unreleased/1166.rst
+++ /dev/null
@@ -1,7 +0,0 @@
-.. change::
-    :tags: bug, autogenerate
-    :tickets: 1166
-
-    Fixed issue in index detection where autogenerate change detection would
-    consider indexes with the same columns but with different order as equal,
-    while in general they are not equivalent in how a database will use them.

diff --git a/docs/build/unreleased/1187.rst b/docs/build/unreleased/1187.rst
deleted file mode 100644 (file)
index 0d9c7dd..0000000
--- a/docs/build/unreleased/1187.rst
+++ /dev/null
@@ -1,8 +0,0 @@
-.. change::
-    :tags: bug, mssql
-    :tickets: 1187
-
-    Properly escape constraint name on SQL Server when dropping
-    a column while specifying ``mssql_drop_default=True`` or
-    ``mssql_drop_check=True`` or ``mssql_drop_foreign_key=True``.
-

diff --git a/docs/build/unreleased/760.rst b/docs/build/unreleased/760.rst
deleted file mode 100644 (file)
index 5f46e10..0000000
--- a/docs/build/unreleased/760.rst
+++ /dev/null
@@ -1,8 +0,0 @@
-.. change::
-    :tags: feature, revisioning
-    :tickets: 760
-
-    Recursive traversal of revision files in a particular revision directory is
-    now supported, by indicating ``recursive_version_locations = true`` in
-    alembic.ini. Pull request courtesy ostr00000.
-

diff --git a/docs/build/unreleased/index_updates.rst b/docs/build/unreleased/index_updates.rst
deleted file mode 100644 (file)
index c210069..0000000
--- a/docs/build/unreleased/index_updates.rst
+++ /dev/null
@@ -1,8 +0,0 @@
-.. change::
-    :tags: usecase, autogenerate, postgresql
-
-    Added support for autogenerate comparison of indexes on PostgreSQL which
-    include SQL expressions, when using SQLAlchemy 2.0; the previous warning
-    that such indexes were skipped are removed when the new functionality
-    is in use.  When using SQLAlchemy versions prior to the 2.0 series,
-    the indexes continue to be skipped with a warning.