chore(release): set README version 0.2.0

Author: ci-sourcerer

README.md

@@ -17,7 +17,7 @@ curl -sSL https://api.github.com/repos/ci-sourcerer/common-python-tasks/contents
 To install a specific release, set the environment variable `COMMON_PYTHON_TASKS_VERSION`.
 
 ```shell
-COMMON_PYTHON_TASKS_VERSION=0.1.0 \
+COMMON_PYTHON_TASKS_VERSION=0.2.0 \
   sh -c "$(curl -sSL https://api.github.com/repos/ci-sourcerer/common-python-tasks/contents/scripts/add-common-python-tasks.sh | jq -r '.content' | base64 -d)"
 ```
 
@@ -38,9 +38,9 @@ There's no real reason to run the automated script; I just like automating every
     ```toml
     [project]
     name = "my-awesome-project"
-    version = "0.1.0"
+    version = "0.2.0"
     dependencies = [
-        "common-python-tasks==0.1.0",  # Always pin to a specific version
+        "common-python-tasks==0.2.0",  # Always pin to a specific version
     ]
 
     [tool.poe]
@@ -254,8 +254,8 @@ By default, `tasks()` exposes the common task set. You can still include or excl
 ```toml
 [project]
 name = "simple-cli-tool"
-version = "0.1.0"
-dependencies = ["common-python-tasks==0.1.0"]
+version = "0.2.0"
+dependencies = ["common-python-tasks==0.2.0"]
 
 [tool.poe]
 include_script = "common_python_tasks:tasks()"
@@ -268,8 +268,8 @@ Available tasks: common defaults such as `format`, `lint`, `test`, and `build`.
 ```toml
 [project]
 name = "containerized-app"
-version = "0.1.0"
-dependencies = ["common-python-tasks==0.1.0"]
+version = "0.2.0"
+dependencies = ["common-python-tasks==0.2.0"]
 
 [tool.poe]
 include_script = "common_python_tasks:tasks(include_tags=['common', 'containers'])"
@@ -286,7 +286,7 @@ Available tasks: All tasks including `build-image` and `push-image`.
 ```toml
 [project]
 name = "custom-test-setup"
-dependencies = ["common-python-tasks==0.1.0"]
+dependencies = ["common-python-tasks==0.2.0"]
 dynamic = ["version"]
 
 [tool.poe]