- 1.11.1

diff --git a/docs/build/changelog.rst b/docs/build/changelog.rst
index 56650049b6d9d3c6869ec463ad0faeca80cdaced..3741d60c3f337900846e37a497e289cfbe990db5 100644 (file)
--- a/docs/build/changelog.rst
+++ b/docs/build/changelog.rst
@@ -5,7 +5,47 @@ Changelog
 
 .. changelog::
     :version: 1.11.1
-    :include_notes_from: unreleased
+    :released: May 17, 2023
+
+    .. change::
+        :tags: bug, autogenerate, regression
+        :tickets: 1243, 1245
+
+        As Alembic 1.11.0 is considered a major release (Alembic does not use
+        semver, nor does its parent project SQLAlchemy; this has been
+        :ref:`clarified <versioning_scheme>` in the documentation), change
+        :ticket:`1130` modified calling signatures for most operations to consider
+        all optional keyword parameters to be keyword-only arguments, to match what
+        was always documented and generated by autogenerate. However, two of these
+        changes were identified as possibly problematic without a more formal
+        deprecation warning being emitted which were the ``table_name`` parameter
+        to :meth:`.Operations.drop_index`, which was generated positionally by
+        autogenerate prior to version 0.6.3 released in 2014, and ``type_`` in
+        :meth:`.Operations.drop_constraint` and
+        :meth:`.BatchOperations.drop_constraint`, which was documented positionally
+        in one example in the batch documentation.
+
+        These two signatures have been
+        restored to allow those particular parameters to be passed positionally. A
+        future change will include formal deprecation paths (with warnings) for
+        these arguments where they will again become keyword-only in a future
+        "Significant Minor" release.
+
+    .. change::
+        :tags: bug, typing
+        :tickets: 1246
+
+        Fixed typing use of :class:`~sqlalchemy.schema.Column` and other
+        generic SQLAlchemy classes.
+
+    .. change::
+        :tags: bug, typing, regression
+        :tickets: 1244
+
+        Restored the output type of :meth:`.Config.get_section` to include
+        ``Dict[str, str]`` as a potential return type, which had been changed to
+        immutable ``Mapping[str, str]``. When a section is returned and the default
+        is not used, a mutable dictionary is returned.
 
 .. changelog::
     :version: 1.11.0

diff --git a/docs/build/conf.py b/docs/build/conf.py
index 4b9674e48594358c91b0072e0c46dfdb7b7ff94b..38b82fa204c12b90b1223cbe5dad5df1ab0a4ea7 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.11.0"
-release_date = "May 15, 2023"
+release = "1.11.1"
+release_date = "May 17, 2023"
 
 
 # The language for content autogenerated by Sphinx. Refer to documentation

diff --git a/docs/build/unreleased/1243.rst b/docs/build/unreleased/1243.rst
deleted file mode 100644 (file)
index e67aeeb..0000000
--- a/docs/build/unreleased/1243.rst
+++ /dev/null
@@ -1,23 +0,0 @@
-.. change::
-    :tags: bug, autogenerate, regression
-    :tickets: 1243, 1245
-
-    As Alembic 1.11.0 is considered a major release (Alembic does not use
-    semver, nor does its parent project SQLAlchemy; this has been
-    :ref:`clarified <versioning_scheme>` in the documentation), change
-    :ticket:`1130` modified calling signatures for most operations to consider
-    all optional keyword parameters to be keyword-only arguments, to match what
-    was always documented and generated by autogenerate. However, two of these
-    changes were identified as possibly problematic without a more formal
-    deprecation warning being emitted which were the ``table_name`` parameter
-    to :meth:`.Operations.drop_index`, which was generated positionally by
-    autogenerate prior to version 0.6.3 released in 2014, and ``type_`` in
-    :meth:`.Operations.drop_constraint` and
-    :meth:`.BatchOperations.drop_constraint`, which was documented positionally
-    in one example in the batch documentation.
-
-    These two signatures have been
-    restored to allow those particular parameters to be passed positionally. A
-    future change will include formal deprecation paths (with warnings) for
-    these arguments where they will again become keyword-only in a future
-    "Significant Minor" release.

diff --git a/docs/build/unreleased/1244.rst b/docs/build/unreleased/1244.rst
deleted file mode 100644 (file)
index a32ffa0..0000000
--- a/docs/build/unreleased/1244.rst
+++ /dev/null
@@ -1,8 +0,0 @@
-.. change::
-    :tags: bug, typing, regression
-    :tickets: 1244
-
-    Restored the output type of :meth:`.Config.get_section` to include
-    ``Dict[str, str]`` as a potential return type, which had been changed to
-    immutable ``Mapping[str, str]``. When a section is returned and the default
-    is not used, a mutable dictionary is returned.

diff --git a/docs/build/unreleased/1246.rst b/docs/build/unreleased/1246.rst
deleted file mode 100644 (file)
index a33de0d..0000000
--- a/docs/build/unreleased/1246.rst
+++ /dev/null
@@ -1,6 +0,0 @@
-.. change::
-    :tags: bug, typing
-    :tickets: 1246
-
-    Fixed typing use of :class:`~sqlalchemy.schema.Column` and other
-    generic SQLAlchemy classes.