diff --git a/alembic-0.8.0.tar.gz b/alembic-0.8.0.tar.gz
deleted file mode 100644
index cacdca5..0000000
--- a/alembic-0.8.0.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ce73b2935ed20dc41a86025f4200203367083d87520b40526b3fc89f7598f85a
-size 918610
diff --git a/alembic-0.8.2.tar.gz b/alembic-0.8.2.tar.gz
new file mode 100644
index 0000000..f37263e
--- /dev/null
+++ b/alembic-0.8.2.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a69d65a766801c40e921ca24ae358bf081a990f54b867bbdc3e2a73e975550be
+size 931914
diff --git a/python-alembic.changes b/python-alembic.changes
index c3ddef8..711c1d1 100644
--- a/python-alembic.changes
+++ b/python-alembic.changes
@@ -1,3 +1,39 @@
+-------------------------------------------------------------------
+Wed Aug 26 14:34:12 UTC 2015 - tbechtold@suse.com
+
+- update to 0.8.2:
+  - Added workaround in new foreign key option detection feature for MySQL’s
+    consideration of the “RESTRICT” option being the default, for which no
+    value is reported from the database; the MySQL impl now corrects for when
+    the model reports RESTRICT but the database reports nothing. A similar
+    rule is in the default FK comparison to accommodate for the default
+    “NO ACTION” setting being present in the model but not necessarily
+    reported by the database, or vice versa.
+  - A custom EnvironmentContext.configure.process_revision_directives hook
+    can now generate op directives within the UpgradeOps and DowngradeOps
+    containers that will be generated as Python code even when the
+    --autogenerate flag is False; provided that revision_environment=True,
+    the full render operation will be run even in “offline” mode.
+  - Implemented support for autogenerate detection of changes in the ondelete,
+    onupdate, initially and deferrable attributes of ForeignKeyConstraint
+    objects on SQLAlchemy backends that support these on reflection (as of
+    SQLAlchemy 1.0.8 currently Postgresql for all four, MySQL for ondelete
+    and onupdate only). A constraint object that modifies these values will
+    be reported as a “diff” and come out as a drop/create of the constraint
+    with the modified values. The fields are ignored for backends which
+    don’t reflect these attributes (as of SQLA 1.0.8 this includes SQLite,
+    Oracle, SQL Server, others).
+  - Repaired the render operation for the ops.AlterColumnOp object to succeed
+  when the “existing_type” field was not present.
+  - Fixed a regression 0.8 whereby the “multidb” environment template failed
+  to produce independent migration script segments for the output template.
+  This was due to the reorganization of the script rendering system for 0.8.
+  To accommodate this change, the MigrationScript structure will in the case
+  of multiple calls to MigrationContext.run_migrations() produce lists for
+  the MigrationScript.upgrade_ops and MigrationScript.downgrade_ops attributes;
+  each UpgradeOps and DowngradeOps instance keeps track of its own upgrade_token
+  and downgrade_token, and each are rendered individually.
+
 -------------------------------------------------------------------
 Fri Aug 21 12:05:28 UTC 2015 - tbechtold@suse.com
 
diff --git a/python-alembic.spec b/python-alembic.spec
index 86fb452..cef97b1 100644
--- a/python-alembic.spec
+++ b/python-alembic.spec
@@ -17,7 +17,7 @@
 
 
 Name:           python-alembic
-Version:        0.8.0
+Version:        0.8.2
 Release:        0
 Url:            http://bitbucket.org/zzzeek/alembic
 Summary:        A database migration tool for SQLAlchemy