Skip to content

chore: bump live-sync docker tag to v0.7.0 #4641

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
arajkumar merged 1 commit into from
Jan 14, 2026
Merged

chore: bump live-sync docker tag to v0.7.0 #4641

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _partials/_livesync-terminal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ instance to a $SERVICE_LONG:
As you run the $PG_CONNECTOR continuously, best practice is to run it as a Docker daemon.

```shell
docker run -d --rm --name livesync timescale/live-sync:v0.4.0 run \
docker run -d --rm --name livesync timescale/live-sync:v0.7.0 run \
--publication <publication_name> --subscription <subscription_name> \
--source $SOURCE --target $TARGET --table-map <table_map_as_json>
```
Expand Down Expand Up @@ -330,7 +330,7 @@ EOF
Use the `--drop` flag to remove the replication slots created by the $PG_CONNECTOR on the source database.

```shell
docker run -it --rm --name livesync timescale/live-sync:v0.4.0 run \
docker run -it --rm --name livesync timescale/live-sync:v0.7.0 run \
--publication <publication_name> --subscription <subscription_name> \
--source $SOURCE --target $TARGET \
--drop
Expand Down