chore(release): 0.2.2 (#51)

Cuts the Unreleased section and repoints the Action examples at the new tag.

This release is the one where pull request mirroring first works. The
feature shipped in 0.2.1, but four defects made it inoperable in practice:
the destination repository path was owner relative where every API wanted
it qualified, Azure DevOps duplicated the project into paths that already
carried it, concurrent repositories raced on shared state, and a pull
request with no labels failed its own update. Two further fixes here,
Docker Hub session tokens and config discovery, affect anyone running
0.2.1 today regardless of whether they mirror pull requests at all.

Co-authored-by: Anmol Nagpal <ianmolnagpal@gmail.com>

Author: clouddrove-ci

CHANGELOG.md

@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.2] - 2026-08-19
+
 ### Fixed
 - `pull_requests.mirror_objects` could not work against GitHub, GitLab, or Bitbucket. The engine handed the destination side the rendered repository name, which is owner relative because the clone URL and repository creation prepend the owner themselves, while every destination pull request and comment endpoint interpolates that value as a fully qualified path: a GitHub destination asked for `/repos/widget/pulls` rather than `/repos/acme/widget/pulls` and every call answered 404. Azure DevOps failed the other way, duplicating the project into a path that already carried it, so listing pull requests 404d for every repository
 - Mirroring several repositories at once could abort the process. Pull request records were written into the shared git state from inside the engine's worker pool without the lock the engine uses for its own access, and two repositories finishing together is a concurrent map write, which Go turns into an unrecoverable crash. The state type now guards its own maps

README.md

@@ -121,7 +121,7 @@ Requires Go 1.23+ to build from source.
 Add SyncerD to your workflow:
 
 ```yaml
-- uses: clouddrove/syncerd@v0.2.1
+- uses: clouddrove/syncerd@v0.2.2
   with:
     config: syncerd.yaml
     once: "true"
@@ -139,7 +139,7 @@ For **AWS ECR**, add `aws-actions/configure-aws-credentials` before SyncerD and
     role-to-assume: arn:aws:iam::123456789012:role/syncerd
     aws-region: eu-west-1
 
-- uses: clouddrove/syncerd@v0.2.1
+- uses: clouddrove/syncerd@v0.2.2
   with:
     config: syncerd.yaml
 ```
@@ -157,7 +157,7 @@ steps:
       username: ${{ github.actor }}
       password: ${{ secrets.GITHUB_TOKEN }}
 
-  - uses: clouddrove/syncerd@v0.2.1
+  - uses: clouddrove/syncerd@v0.2.2
     env:
       DOCKER_CONFIG: /github/workspace/.docker     # same directory, path inside the container
     with:
@@ -181,7 +181,7 @@ steps:
 Since the default push mode deletes destination refs that are absent at the source, **run once with `dry-run: "true"` before trusting a new mirror config**:
 
 ```yaml
-- uses: clouddrove/syncerd@v0.2.1
+- uses: clouddrove/syncerd@v0.2.2
   with:
     command: git-sync
     config: syncerd.yaml
@@ -195,7 +195,7 @@ Since the default push mode deletes destination refs that are absent at the sour
 Once the dry run output looks right, drop `dry-run` (or set it to `"false"`) to let it write for real:
 
 ```yaml
-- uses: clouddrove/syncerd@v0.2.1
+- uses: clouddrove/syncerd@v0.2.2
   with:
     command: git-sync
     config: syncerd.yaml