From d975b81bc3d6e3735bc684e9faa0814d98f292c4 Mon Sep 17 00:00:00 2001 From: trav Date: Mon, 25 May 2026 20:29:28 +0100 Subject: [PATCH 1/3] chore: upgrade to 7.2.0+v1.153.0 --- compose.mas.yml | 2 +- compose.yml | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/compose.mas.yml b/compose.mas.yml index 64f7670..5050c99 100644 --- a/compose.mas.yml +++ b/compose.mas.yml @@ -5,7 +5,7 @@ version: "3.8" services: mas: - image: ghcr.io/element-hq/matrix-authentication-service:1.14.0 + image: ghcr.io/element-hq/matrix-authentication-service:1.17.0 command: ["server", "--config=/etc/mas/config.yaml"] environment: - DOMAIN diff --git a/compose.yml b/compose.yml index 54c2d63..26962c6 100644 --- a/compose.yml +++ b/compose.yml @@ -3,7 +3,7 @@ version: "3.8" services: web: - image: nginx:1.29.6 + image: nginx:1.31.1 networks: - proxy - internal @@ -43,7 +43,7 @@ services: start_period: 2m app: - image: "matrixdotorg/synapse:v1.149.1" + image: "matrixdotorg/synapse:v1.153.0" volumes: - "data:/data" secrets: @@ -114,7 +114,7 @@ services: restart_policy: condition: on-failure labels: - - "coop-cloud.${STACK_NAME}.version=7.1.1+v1.149.1" + - "coop-cloud.${STACK_NAME}.version=7.2.0+v1.153.0" - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT}" healthcheck: test: ["CMD", "curl", "-f", "http://localhost:8008/health"] @@ -124,7 +124,7 @@ services: start_period: 1m db: - image: pgautoupgrade/pgautoupgrade:17-alpine + image: pgautoupgrade/pgautoupgrade:18-alpine secrets: - db_password environment: -- 2.49.0 From a1771ce37186d7ccd51f2fe5257a8fdbd7c2d7d8 Mon Sep 17 00:00:00 2001 From: notplants <@notplants> Date: Fri, 5 Jun 2026 03:13:43 +0000 Subject: [PATCH 2/3] chore: upgrade to 7.3.0+v1.154.0 --- compose.mas.yml | 2 +- compose.yml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/compose.mas.yml b/compose.mas.yml index 5050c99..9307c0c 100644 --- a/compose.mas.yml +++ b/compose.mas.yml @@ -5,7 +5,7 @@ version: "3.8" services: mas: - image: ghcr.io/element-hq/matrix-authentication-service:1.17.0 + image: ghcr.io/element-hq/matrix-authentication-service:1.18.0 command: ["server", "--config=/etc/mas/config.yaml"] environment: - DOMAIN diff --git a/compose.yml b/compose.yml index 26962c6..d349333 100644 --- a/compose.yml +++ b/compose.yml @@ -43,7 +43,7 @@ services: start_period: 2m app: - image: "matrixdotorg/synapse:v1.153.0" + image: "matrixdotorg/synapse:v1.154.0" volumes: - "data:/data" secrets: @@ -114,7 +114,7 @@ services: restart_policy: condition: on-failure labels: - - "coop-cloud.${STACK_NAME}.version=7.2.0+v1.153.0" + - "coop-cloud.${STACK_NAME}.version=7.3.0+v1.154.0" - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT}" healthcheck: test: ["CMD", "curl", "-f", "http://localhost:8008/health"] -- 2.49.0 From c94186132cf074d71ec9ae85185cd92a8fe1b345 Mon Sep 17 00:00:00 2001 From: notplants <@notplants> Date: Mon, 8 Jun 2026 20:45:44 +0000 Subject: [PATCH 3/3] fix: pin PGDATA so the postgres 18 bump upgrades in place postgres:18 (tracked by pgautoupgrade) relocated the default PGDATA from /var/lib/postgresql/data to /var/lib/postgresql/18/docker. Since the db volume is mounted at the legacy path, pg18 would init a fresh empty cluster there and orphan all existing data (pgautoupgrade never runs the upgrade). Pinning PGDATA to the legacy path makes pg18 find the existing cluster and upgrade it in place. --- compose.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/compose.yml b/compose.yml index d349333..09f782e 100644 --- a/compose.yml +++ b/compose.yml @@ -128,6 +128,10 @@ services: secrets: - db_password environment: + # postgres:18 relocated the default PGDATA to /var/lib/postgresql/18/docker. + # Pin it to the legacy path so pgautoupgrade finds the existing cluster on the + # mounted volume and upgrades it in place, instead of init'ing an empty one. + - PGDATA=/var/lib/postgresql/data - LC_COLLATE=C - LC_CTYPE=C - POSTGRES_DB=synapse -- 2.49.0