chore(deps): update ghcr.io/gothenburgbitfactory/taskchampion-sync-server docker tag to v0.7.1

[soerenschneider]

This PR contains the following updates:

Package	Update	Change
ghcr.io/gothenburgbitfactory/taskchampion-sync-server	minor	0.6.1 -> 0.7.1

---

Release Notes

GothenburgBitFactory/taskchampion-sync-server (ghcr.io/gothenburgbitfactory/taskchampion-sync-server)

v0.7.1

Compare Source

v0.7.0

Compare Source

What's Changed

• Postgres support and additional server options to disable automatic creation of clients
• New documentation for integrating with the sync server
• Fixes to docker images

Breaking Changes

Running the Docker image for this server without specifying DATA_DIR
in releases before this one defaulted to storing the server data in
/var/lib/taskchampion-sync-server. However, the Dockerfile only
specifies that the subdirectory /var/lib/taskchampion-sync-server/data
is a VOLUME. This change fixes the default to match the VOLUME, putting
the server data on an ephemeral volume or, if a --volume $NAME:/var/lib/taskchampion-sync-server/data argument is provided to
docker run, in a named volume.

Before this release, with default settings the server data is stored in
the container's ephemeral writeable layer. When the container is killed,
the data is lost. This issue does not affect deployments with docker compose, as the compose configuration specifies a correct DATA_DIR.

You can determine if your deployment is affected as follows. First,
determine the ID of the running server container, $CONTAINER. Examine
the volumes for that container:

$ docker container inspect $CONTAINER | jq '.[0].Config.Volumes'
{
  "/var/lib/task-champion-sync-server/data": {}
}

Next, find the server data, in a .sqlite3 file:

$ docker exec $CONTAINER find /var/lib/taskchampion-sync-server
/var/lib/taskchampion-sync-server
/var/lib/taskchampion-sync-server/data
/var/lib/taskchampion-sync-server/taskchampion-sync-server.sqlite3

If the data is not in a directory mounted as a volume, then it is
ephemeral. To copy the data out of the container:

docker cp $CONTAINER:/var/lib/taskchampion-sync-server/taskchampion-sync-server.sqlite3 /tmp

You may then upgrade the image and use docker cp to copy the data back
to the correct location, /var/lib/taskchampion-sync-server/data.

Note that, as long as all replicas are fully synced, the TaskChampion
sync protocol is resilient to loss of server data, so even if the server
data has been lost, task sync may continue to work.

New Contributors

• @​awilkins made their first contribution in https://github.com/GothenburgBitFactory/taskchampion-sync-server/pull/112

Full Changelog: GothenburgBitFactory/taskchampion-sync-server@v0.6.1...v0.7.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.