diff --git a/SQLAlchemy-1.2.10.tar.gz b/SQLAlchemy-1.2.10.tar.gz
deleted file mode 100644
index 4609aae..0000000
--- a/SQLAlchemy-1.2.10.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:72325e67fb85f6e9ad304c603d83626d1df684fdf0c7ab1f0352e71feeab69d8
-size 5615652
diff --git a/SQLAlchemy-1.2.11.tar.gz b/SQLAlchemy-1.2.11.tar.gz
new file mode 100644
index 0000000..3d4184a
--- /dev/null
+++ b/SQLAlchemy-1.2.11.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef6569ad403520ee13e180e1bfd6ed71a0254192a934ec1dbd3dbf48f4aa9524
+size 5611782
diff --git a/python-SQLAlchemy.changes b/python-SQLAlchemy.changes
index eb24dff..9723577 100644
--- a/python-SQLAlchemy.changes
+++ b/python-SQLAlchemy.changes
@@ -1,3 +1,63 @@
+-------------------------------------------------------------------
+Sat Aug 25 18:12:02 UTC 2018 - arun@gmx.de
+
+- update to version 1.2.11:
+  * orm declarative
+    + [bug] [declarative] [orm] Fixed issue in previously untested use
+      case, allowing a declarative mapped class to inherit from a
+      classically-mapped class outside of the declarative base,
+      including that it accommodates for unmapped intermediate
+      classes. An unmapped intermediate class may specify
+      __abstract__, which is now interpreted correctly, or the
+      intermediate class can remain unmarked, and the classically
+      mapped base class will be detected within the hierarchy
+      regardless. In order to anticipate existing scenarios which may
+      be mixing in classical mappings into existing declarative
+      hierarchies, an error is now raised if multiple mapped bases are
+      detected for a given class.   References: #4321
+  * sql
+    + [sql] [bug] Fixed issue that is closely related to #3639 where
+      an expression rendered in a boolean context on a non-native
+      boolean backend would be compared to 1/0 even though it is
+      already an implcitly boolean expression, when
+      ColumnElement.self_group() were used. While this does not affect
+      the user-friendly backends (MySQL, SQLite) it was not handled by
+      Oracle (and possibly SQL Server). Whether or not the expression
+      is implicitly boolean on any database is now determined up front
+      as an additional check to not generate the integer comparison
+      within the compliation of the statement.  References: #4320
+    + [sql] [bug] Added missing window function parameters
+      WithinGroup.over.range_ and WithinGroup.over.rows parameters to
+      the WithinGroup.over() and FunctionFilter.over() methods, to
+      correspond to the range/rows feature added to the “over” method
+      of SQL functions as part of #3049 in version 1.1.  References:
+      #4322
+    + [sql] [bug] Fixed bug where the multi-table support for UPDATE
+      and DELETE statements did not consider the additional FROM
+      elements as targets for correlation, when a correlated SELECT
+      were also combined with the statement. This change now includes
+      that a SELECT statement in the WHERE clause for such a statement
+      will try to auto-correlate back to these additional tables in
+      the parent UPDATE/DELETE or unconditionally correlate if
+      Select.correlate() is used. Note that auto-correlation raises an
+      error if the SELECT statement would have no FROM clauses as a
+      result, which can now occur if the parent UPDATE/DELETE
+      specifies the same tables in its additional set of tables;
+      specify Select.correlate() explicitly to resolve.  References:
+      #4313
+  * oracle
+    + [oracle] [bug] For cx_Oracle, Integer datatypes will now be
+      bound to “int”, per advice from the cx_Oracle
+      developers. Previously, using cx_Oracle.NUMBER caused a loss in
+      precision within the cx_Oracle 6.x series.  References: #4309
+  * misc
+    + [bug] [py3k] Started importing “collections” from
+      “collections.abc” under Python 3.3 and greater for Python 3.8
+      compatibility. Pull request courtesy Nathaniel Knight.
+    + Fixed issue where the “schema” name used for a SQLite database
+      within table reflection would not quote the schema name
+      correctly. Pull request courtesy Phillip Cloud.
+
 -------------------------------------------------------------------
 Sat Jul 14 01:56:32 UTC 2018 - arun@gmx.de
 
diff --git a/python-SQLAlchemy.spec b/python-SQLAlchemy.spec
index ab233f3..bf8e63e 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.10
+Version:        1.2.11
 Release:        0
 Summary:        Database Abstraction Library
 License:        MIT