cherry-pick changelog from 1.3.22

diff --git a/doc/build/changelog/changelog_13.rst b/doc/build/changelog/changelog_13.rst
index c7bf4a0d620ce1587c3c0042de4703c4ec90028f..bde93d6bc6b5083ea1335c7941c16465d548f17e 100644 (file)
--- a/doc/build/changelog/changelog_13.rst
+++ b/doc/build/changelog/changelog_13.rst
@@ -12,7 +12,23 @@
 
 .. changelog::
     :version: 1.3.22
-    :include_notes_from: unreleased_13
+    :released: December 18, 2020
+
+    .. change::
+        :tags: bug, oracle
+        :tickets: 5784
+        :versions: 1.4.0b2
+
+        Fixed regression which occured due to :ticket:`5755` which implemented
+        isolation level support for Oracle.   It has been reported that many Oracle
+        accounts don't actually have permission to query the ``v$transaction``
+        view so this feature has been altered to gracefully fallback when it fails
+        upon database connect, where the dialect will assume "READ COMMITTED" is
+        the default isolation level as was the case prior to SQLAlchemy 1.3.21.
+        However, explicit use of the :meth:`_engine.Connection.get_isolation_level`
+        method must now necessarily raise an exception, as Oracle databases with
+        this restriction explicitly disallow the user from reading the current
+        isolation level.
 
 .. changelog::
     :version: 1.3.21

diff --git a/doc/build/changelog/unreleased_13/5784.rst b/doc/build/changelog/unreleased_13/5784.rst
deleted file mode 100644 (file)
index 87ee080..0000000
--- a/doc/build/changelog/unreleased_13/5784.rst
+++ /dev/null
@@ -1,15 +0,0 @@
-.. change::
-    :tags: bug, oracle
-    :tickets: 5784
-    :versions: 1.4.0b2
-
-    Fixed regression which occured due to :ticket:`5755` which implemented
-    isolation level support for Oracle.   It has been reported that many Oracle
-    accounts don't actually have permission to query the ``v$transaction``
-    view so this feature has been altered to gracefully fallback when it fails
-    upon database connect, where the dialect will assume "READ COMMITTED" is
-    the default isolation level as was the case prior to SQLAlchemy 1.3.21.
-    However, explicit use of the :meth:`_engine.Connection.get_isolation_level`
-    method must now necessarily raise an exception, as Oracle databases with
-    this restriction explicitly disallow the user from reading the current
-    isolation level.
\ No newline at end of file