diff --git a/SQLAlchemy-1.2.13.tar.gz b/SQLAlchemy-1.2.13.tar.gz
deleted file mode 100644
index bac5bf5..0000000
--- a/SQLAlchemy-1.2.13.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:84412de3794acee05630e7788f25e80e81f78eb4837e7b71d0499129f660486a
-size 5650472
diff --git a/SQLAlchemy-1.2.14.tar.gz b/SQLAlchemy-1.2.14.tar.gz
new file mode 100644
index 0000000..0456f50
--- /dev/null
+++ b/SQLAlchemy-1.2.14.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9de7c7dabcf06319becdb7e15099c44e5e34ba7062f9ba10bc00e562f5db3d04
+size 5657372
diff --git a/python-SQLAlchemy.changes b/python-SQLAlchemy.changes
index 0d4ded5..edc9da9 100644
--- a/python-SQLAlchemy.changes
+++ b/python-SQLAlchemy.changes
@@ -1,3 +1,33 @@
+-------------------------------------------------------------------
+Mon Nov 12 06:16:33 UTC 2018 - Arun Persaud <arun@gmx.de>
+
+- update to version 1.2.14:
+  * orm
+    + [orm] [bug] Fixed bug in Session.bulk_update_mappings() where
+      alternate mapped attribute names would result in the primary key
+      column of the UPDATE statement being included in the SET clause,
+      as well as the WHERE clause; while usually harmless, for SQL
+      Server this can raise an error due to the IDENTITY column. This
+      is a continuation of the same bug that was fixed in #3849, where
+      testing was insufficient to catch this additional flaw.
+      References: #4357
+    + [orm] [bug] Fixed a minor performance issue which could in some
+      cases add unnecessary overhead to result fetching, involving the
+      use of ORM columns and entities that include those same columns
+      at the same time within a query. The issue has to do with hash /
+      eq overhead when referring to the column in different ways.
+      References: #4347
+  * mysql
+    + [mysql] [bug] Fixed regression caused by #4344 released in
+      1.2.13, where the fix for MySQL 8.0’s case sensitivity problem
+      with referenced column names when reflecting foreign key
+      referents is worked around using the information_schema.columns
+      view. The workaround was failing on OSX /
+      lower_case_table_names=2 which produces non-matching casing for
+      the information_schema.columns vs. that of SHOW CREATE TABLE, so
+      in case-insensitive SQL modes case-insensitive matching is now
+      used.  References: #4361
+
 -------------------------------------------------------------------
 Thu Nov  1 22:48:27 UTC 2018 - Arun Persaud <arun@gmx.de>
 
diff --git a/python-SQLAlchemy.spec b/python-SQLAlchemy.spec
index 523796e..ef53749 100644
--- a/python-SQLAlchemy.spec
+++ b/python-SQLAlchemy.spec
@@ -20,7 +20,7 @@
 %define oldpython python
 %bcond_without tests
 Name:           python-SQLAlchemy
-Version:        1.2.13
+Version:        1.2.14
 Release:        0
 Summary:        Database Abstraction Library
 License:        MIT