Update readme for upcoming release

Author: scadu

README.md

@@ -45,7 +45,7 @@ For example, in the following configuration:
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "**/*"
@@ -78,7 +78,7 @@ This is a sub-section that provides configuration for running commands or trigge
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           watch:
             - path: app/
               config:
@@ -109,7 +109,7 @@ steps:
 steps:
   - label: "Triggering pipelines with plugin"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           watch:
             - path: test/.buildkite/
               config: # Required [trigger step configuration]
@@ -138,7 +138,7 @@ The plugin supports conditional execution of pipeline steps using the `if` key,
 steps:
   - label: "Triggering pipelines with plugin"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           diff: git diff --name-only HEAD~1
           watch:
             - path: services/api
@@ -151,20 +151,20 @@ steps:
                 if: build.tag != null
 ```
 
-In the example above, 
+In the example above,
+
 - The `deploy-api` trigger will only run on the main branch or branches matching `release/*`.
 - The `web deployment` command will run only if the build has a tag.
 
-
 #### `diff` (optional)
 
 This will run the script provided to determine the folder changes.
 Depending on your use case, you may want to determine the point where the branch occurs
-https://stackoverflow.com/questions/1527234/finding-a-branch-point-with-git and perform a diff against the branch point.
+<https://stackoverflow.com/questions/1527234/finding-a-branch-point-with-git> and perform a diff against the branch point.
 
 Default: `git diff --name-only HEAD~1`
 
-#### Sample output:
+#### Sample output
 
 ```
 README.md
@@ -201,7 +201,7 @@ git diff --name-only "$LATEST_TAG"
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "bar-service/"
@@ -228,7 +228,7 @@ A default `config` to run if no paths are matched, the `config` key is not requi
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "bar-service/"
@@ -250,7 +250,7 @@ The object values provided in this configuration will be appended to `env` prope
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "foo-service/"
@@ -272,7 +272,7 @@ Add `log_level` property to set the log level. Supported log levels are `debug`
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           diff: "git diff --name-only HEAD~1"
           log_level: "debug" # defaults to "info"
           watch:
@@ -303,7 +303,7 @@ By setting `wait` to `true`, the build will wait until the triggered pipeline bu
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.5.1:
+      - monorepo-diff#v1.5.2:
           diff: "git diff --name-only $(head -n 1 last_successful_build)"
           interpolation: false
           env:
@@ -358,7 +358,6 @@ Thanks to [@chronotc](https://github.com/chronotc) and [@adikari](https://github
 
 MIT (see [LICENSE](LICENSE))
 
-
 ## How to Contribute
 
 Please read [contributing guide](https://github.com/buildkite-plugins/monorepo-diff-buildkite-plugin/blob/master/CONTRIBUTING.md).