diff --git a/CHANGELOG.md b/CHANGELOG.md
index 496cd6be..644adb76 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,13 @@
 # Changelog
 
+## [v1.0.3](https://github.com/ably/kafka-connect-ably/tree/v1.0.3) (2021-12-31)
+
+[Full Changelog](https://github.com/ably/kafka-connect-ably/compare/v1.0.2...v1.0.3)
+
+**Fixed bugs:**
+
+- Caught exception and printed stack trace instead of throwing it to resume task [\#36](https://github.com/ably/kafka-connect-ably/pull/36) ([ikbalkaya](https://github.com/ikbalkaya))
+
 ## [v1.0.2](https://github.com/ably/kafka-connect-ably/tree/v1.0.2) (2021-09-29)
 
 [Full Changelog](https://github.com/ably/kafka-connect-ably/compare/v1.0.1...v1.0.2)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 56f1d1bd..a8b315f8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -31,16 +31,16 @@ Run the integration tests:
 
 This library uses [semantic versioning](http://semver.org/). For each release, the following needs to be done:
 
-1. Create a branch for the release, named like `release/1.0.2` (where `1.0.2` is the new version you want to release)
+1. Create a branch for the release, named like `release/1.2.3` (where `1.2.3` is the new version you want to release)
 2. Update the version number in the `product.version` element of [`pom.xml`](./pom.xml)
 3. Run [`github_changelog_generator`](https://github.com/github-changelog-generator/github-changelog-generator) to automate the update of the [CHANGELOG](./CHANGELOG.md). This may require some manual intervention, both in terms of how the command is run and how the change log file is modified. Your mileage may vary:
-  * The command you will need to run will look something like this: `github_changelog_generator -u ably -p kafka-connect-ably --since-tag v1.0.1 --output delta.md`
+  * The command you will need to run will look something like this: `github_changelog_generator -u ably -p kafka-connect-ably --since-tag v1.2.2 --output delta.md` (where `1.2.2` is the version number of the previous release)
   * Using the command above, `--output delta.md` writes changes made after `--since-tag` to a new file
   * The contents of that new file (`delta.md`) then need to be manually inserted at the top of the `CHANGELOG.md`, changing the "Unreleased" heading and linking with the current version numbers
   * Also ensure that the "Full Changelog" link points to the new version tag instead of the `HEAD`
   * Commit this change: `git add CHANGELOG.md && git commit -m "Update change log."`
 4. Make a PR against `main`
 5. Once the PR is approved, merge it into `main`
-6. Add a tag and push to origin - e.g.: `git tag v1.0.2 && git push origin v1.0.2`
+6. Add a tag and push to origin - e.g.: `git tag v1.2.3 && git push origin v1.2.3`
 7. Create the release on Github including populating the release notes
-8. Notify the product team that a new ZIP file needs to be sent to Confluent Hub, which can be downloaded at the following URL: https://sdk.ably.com/builds/ably/kafka-connect-ably/main/kafka-connect-ably/ably-kafka-connect-ably-1.0.2.zip
+8. Notify the product team that a new ZIP file needs to be sent to Confluent Hub, which can be downloaded at the following URL (replacing the version number with the version number built, available once [the workflow](.github/workflows/integration-test.yml) has finished executing on `main`): https://sdk.ably.com/builds/ably/kafka-connect-ably/main/kafka-connect-ably/ably-kafka-connect-ably-1.2.3.zip
diff --git a/pom.xml b/pom.xml
index b0d47de5..2887fd6f 100644
--- a/pom.xml
+++ b/pom.xml
@@ -5,7 +5,7 @@
 
     <groupId>com.ably.kafka.connect</groupId>
     <artifactId>kafka-connect-ably</artifactId>
-    <version>1.0.2</version>
+    <version>1.0.3</version>
     <packaging>jar</packaging>
 
     <properties>