diff --git a/SQLAlchemy-1.2.4.tar.gz b/SQLAlchemy-1.2.4.tar.gz
deleted file mode 100644
index 9fb264f..0000000
--- a/SQLAlchemy-1.2.4.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:6997507af46b10630e13b605ac278b78885fd683d038896dbee0e7ec41d809d2
-size 5555033
diff --git a/SQLAlchemy-1.2.5.tar.gz b/SQLAlchemy-1.2.5.tar.gz
new file mode 100644
index 0000000..5c7105c
--- /dev/null
+++ b/SQLAlchemy-1.2.5.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:249000654107a420a40200f1e0b555a79dfd4eff235b2ff60bc77714bd045f2d
+size 5559969
diff --git a/python-SQLAlchemy.changes b/python-SQLAlchemy.changes
index 0d3d1fa..b99c298 100644
--- a/python-SQLAlchemy.changes
+++ b/python-SQLAlchemy.changes
@@ -1,3 +1,49 @@
+-------------------------------------------------------------------
+Thu Mar  8 04:50:46 UTC 2018 - arun@gmx.de
+
+- update to version 1.2.5:
+  * orm
+    + [orm] [feature] Added new feature
+      Query.only_return_tuples(). Causes the Query object to return
+      keyed tuple objects unconditionally even if the query is against
+      a single entity. Pull request courtesy Eric Atkin.
+    + [orm] [bug] Fixed bug in new “polymorphic selectin” loading when
+      a selection of polymorphic objects were to be partially loaded
+      from a relationship lazy loader, leading to an “empty IN”
+      condition within the load that raises an error for the “inline”
+      form of “IN”. References: #4199
+    + [orm] [bug] Fixed 1.2 regression where a mapper option that
+      contains an AliasedClass object, as is typical when using the
+      QueryableAttribute.of_type() method, could not be pickled. 1.1’s
+      behavior was to omit the aliased class objects from the path, so
+      this behavior is restored.  References: #4209
+  * sql
+    + [sql] [bug] Fixed bug in :class:.`CTE` construct along the same
+      lines as that of #4204 where a CTE that was aliased would not
+      copy itself correctly during a “clone” operation as is frequent
+      within the ORM as well as when using the ClauseElement.params()
+      method.  References: #4210
+    + [sql] [bug] Fixed bug in CTE rendering where a CTE that was also
+      turned into an Alias would not render its “ctename AS aliasname”
+      clause appropriately if there were more than one reference to
+      the CTE in a FROM clause.  References: #4204
+    + [sql] [bug] Fixed bug in new “expanding IN parameter” feature
+      where the bind parameter processors for values wasn’t working at
+      all, tests failed to cover this pretty basic case which includes
+      that ENUM values weren’t working.  References: #4198
+  * postgresql
+    + [postgresql] [bug] [py3k] Fixed bug in Postgresql COLLATE /
+      ARRAY adjustment first introduced in #4006 where new behaviors
+      in Python 3.7 regular expressions caused the fix to fail.  This
+      change is also backported to: 1.1.18 References: #4208
+  * mysql
+    + [mysql] [bug] MySQL dialects now query the server version using
+      SELECT @@version explicitly to the server to ensure we are
+      getting the correct version information back. Proxy servers like
+      MaxScale interfere with the value that is passed to the DBAPI’s
+      connection.server_version value so this is no longer reliable.
+      This change is also backported to: 1.1.18 References: #4205
+
 -------------------------------------------------------------------
 Fri Feb 23 23:48:41 UTC 2018 - arun@gmx.de
 
diff --git a/python-SQLAlchemy.spec b/python-SQLAlchemy.spec
index dea8868..89332ec 100644
--- a/python-SQLAlchemy.spec
+++ b/python-SQLAlchemy.spec
@@ -21,7 +21,7 @@
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 %define oldpython python
 Name:           python-SQLAlchemy
-Version:        1.2.4
+Version:        1.2.5
 Release:        0
 Url:            http://www.sqlalchemy.org
 Summary:        Database Abstraction Library