From 5a91895040b3c5fd8fda931e1958c4392cf5442c Mon Sep 17 00:00:00 2001
From: Samira <54845154+Samira-El@users.noreply.github.com>
Date: Fri, 24 Jul 2020 13:54:33 +0300
Subject: [PATCH] Release 0.20.1 (#486)

* Update setup.py

* Update CHANGELOG.md

* Update CHANGELOG.md
---
 CHANGELOG.md | 10 +++++++++-
 setup.py     |  2 +-
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index e7ec68d19..a0805549a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,11 @@
+0.20.1 (2020-07-24)
+-------------------
+
+**Tap MySQL**
+- revert back to `pipelinewise-tap-mysql` to 1.3.2
+    - 1.3.3 is breaking the replication
+
+
 0.20.0 (2020-07-24)
 -------------------
 
@@ -9,7 +17,7 @@
     - Add `update_buffer_size` parameter to control how many update operation we should keep in the memory before having to make a call to `find` operation to get the documents from the server. The default value is 1, i.e every detected update will be sent to stdout right away.
 
 **Tap MySQL**
-- Bump `pipelinewise-tap-mongodb` to 1.3.3
+- Bump `pipelinewise-tap-mysql` to 1.3.3
     - During `LOG_BASED` runtime, detect new columns, incl renamed ones, by comparing the columns in the binlog event to the stream schema, and if there are any additional columns, run discovery and send a new `SCHEMA` message to target. This helps avoid data loss.
 
 **Tap Zendesk**
diff --git a/setup.py b/setup.py
index a659203e4..9565e797d 100644
--- a/setup.py
+++ b/setup.py
@@ -6,7 +6,7 @@
     LONG_DESCRIPTION = f.read()
 
 setup(name='pipelinewise',
-      version='0.20.0',
+      version='0.20.1',
       description='PipelineWise',
       long_description=LONG_DESCRIPTION,
       long_description_content_type='text/markdown',