diff --git a/SQLAlchemy-1.4.36.tar.gz b/SQLAlchemy-1.4.36.tar.gz
deleted file mode 100644
index f737bfa..0000000
--- a/SQLAlchemy-1.4.36.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:64678ac321d64a45901ef2e24725ec5e783f1f4a588305e196431447e7ace243
-size 8146415
diff --git a/SQLAlchemy-1.4.37.tar.gz b/SQLAlchemy-1.4.37.tar.gz
new file mode 100644
index 0000000..ca9cbff
--- /dev/null
+++ b/SQLAlchemy-1.4.37.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3688f92c62db6c5df268e2264891078f17ecb91e3141b400f2e28d0f75796dea
+size 8155965
diff --git a/python-SQLAlchemy.changes b/python-SQLAlchemy.changes
index 127247e..dc2387a 100644
--- a/python-SQLAlchemy.changes
+++ b/python-SQLAlchemy.changes
@@ -1,3 +1,27 @@
+-------------------------------------------------------------------
+Sat Jun  4 08:49:42 UTC 2022 - Dirk Müller <dmueller@suse.com>
+
+- update to 1.4.37
+  * details on https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-1.4.37
+  * Fixed issue where using a column_property() construct containing a subquery
+    against an already-mapped column attribute would not correctly apply
+    ORM-compilation behaviors to the subquery, including that the “IN” expression
+    added for a single-table inherits expression would fail to be included.
+  * Fixed issue where ORM results would apply incorrect key names to the
+    returned Row objects in the case where the set of columns to be selected
+    were changed, such as when using Select.with_only_columns().
+  * Fixed bug, likely a regression from 1.3, where usage of column names that
+    require bound parameter escaping, more concretely when using Oracle with
+    column names that require quoting such as those that start with an
+    underscore, or in less common cases with some PostgreSQL drivers when using
+    column names that contain percent signs, would cause the ORM versioning
+    feature to not work correctly if the versioning column itself had such a
+    name, as the ORM assumes certain bound parameter naming conventions that
+    were being interfered with via the quotes. This issue is related to #8053
+    and essentially revises the approach towards fixing this, revising the
+    original issue #5653 that created the initial implementation for
+    generalized bound-parameter name quoting.
+
 -------------------------------------------------------------------
 Wed May  4 19:54:39 UTC 2022 - Dirk Müller <dmueller@suse.com>
 
diff --git a/python-SQLAlchemy.spec b/python-SQLAlchemy.spec
index eec5dec..8fa71ff 100644
--- a/python-SQLAlchemy.spec
+++ b/python-SQLAlchemy.spec
@@ -20,7 +20,7 @@
 %define skip_python2 1
 %define oldpython python
 Name:           python-SQLAlchemy
-Version:        1.4.36
+Version:        1.4.37
 Release:        0
 Summary:        Database Abstraction Library
 License:        MIT