upgrade to v2.6.3

abra.sh

@@ -1 +0,0 @@
-export PG_BACKUP_VERSION=v1

compose.yml

@@ -3,7 +3,7 @@ version: "3.8"
 
 services:
   app:
-    image: ghcr.io/immich-app/immich-server:v3.0.1
+    image: ghcr.io/immich-app/immich-server:v2.6.3
     volumes:
       - uploads:/usr/src/app/upload
       - /etc/localtime:/etc/localtime:ro
@@ -19,21 +19,18 @@ services:
       - proxy
       - backend
     healthcheck:
-      test: ["CMD-SHELL", "immich-healthcheck"]
-      start_period: 120s
+      disable: false
     depends_on:
       - redis
       - database
     deploy:
-      update_config:
-        failure_action: continue
       labels:
         - "traefik.enable=true"
         - "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=2283"
         - "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`${EXTRA_DOMAINS})"
         - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
         - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
-        - "coop-cloud.${STACK_NAME}.version=1.9.0+v3.0.1"
+        - "coop-cloud.${STACK_NAME}.version=1.4.0+v2.5.6"
         - "backupbot.backup=${ENABLE_BACKUPS:-true}"
         - "backupbot.volumes.model-cache=false"
         - "backupbot.volumes.uploads=false"
@@ -41,7 +38,7 @@ services:
 
 
   immich-machine-learning: # TODO: this has to be that name, as the frontend tries to reach it at: http://immich-machine-learning:3003
-    image: ghcr.io/immich-app/immich-machine-learning:v3.0.1
+    image: ghcr.io/immich-app/immich-machine-learning:v2.6.3
     volumes:
       - model-cache:/cache
     networks:
@@ -50,14 +47,14 @@ services:
       disable: false
 
   redis:
-    image: docker.io/valkey/valkey:9@sha256:3b55fbaa0cd93cf0d9d961f405e4dfcc70efe325e2d84da207a0a8e6d8fde4f9
+    image: docker.io/valkey/valkey:9@sha256:3eeb09785cd61ec8e3be35f8804c8892080f3ca21934d628abc24ee4ed1698f6
     healthcheck:
       test: redis-cli ping || exit 1
     networks:
       - backend
 
   database:
-    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465fb969a68c7ac23e375e21f4c95cfacd0edce5fa1bc31e63b7891891
+    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23
     environment:
       POSTGRES_PASSWORD_FILE: /run/secrets/db_password
       POSTGRES_USER: ${DB_USERNAME}
@@ -70,21 +67,6 @@ services:
       - postgres:/var/lib/postgresql/data
     networks:
       - backend
-    deploy:
-      labels:
-        backupbot.backup: "${ENABLE_BACKUPS:-true}"
-        backupbot.backup.pre-hook: "/pg_backup.sh backup"
-        backupbot.backup.volumes.postgres.path: "backup.sql"
-        backupbot.restore.post-hook: "/pg_backup.sh restore"
-    configs:
-      - source: pg_backup
-        target: /pg_backup.sh
-        mode: 0555
-
-configs:
-  pg_backup:
-    name: ${STACK_NAME}_pg_backup_${PG_BACKUP_VERSION}
-    file: pg_backup.sh
 
 secrets:
   db_password:

pg_backup.sh

@@ -1,27 +0,0 @@
-#!/bin/bash
-
-# Postgres backup/restore hook for immich's VectorChord/pgvecto.rs `database` service.
-# Two image-specific constraints:
-#   1. Never DROP DATABASE — the bundled pgvecto.rs worker PANICs and crashes the server.
-#      So `pg_dump --clean --if-exists` does a per-object replace in the live DB on restore.
-#   2. Restore rewrites the dump's empty search_path back to `public, pg_catalog` so VectorChord
-#      types resolve (per https://docs.immich.app/administration/backup-and-restore).
-
-set -e
-
-BACKUP_FILE='/var/lib/postgresql/data/backup.sql'
-export PGPASSWORD=$(cat "${POSTGRES_PASSWORD_FILE:-/run/secrets/db_password}")
-DB_USER="${POSTGRES_USER:-postgres}"
-DB_NAME="${POSTGRES_DB:-immich}"
-
-function backup {
-  pg_dump --clean --if-exists -U "$DB_USER" "$DB_NAME" | gzip > "$BACKUP_FILE"
-}
-
-function restore {
-  gunzip -c "$BACKUP_FILE" \
-    | sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
-    | psql -U "$DB_USER" -d "$DB_NAME" -f -
-}
-
-$@

release/1.5.0+v2.6.3

@@ -1 +0,0 @@
-there might be some long running db migrations that cause the update to look like it's timed out, check `abra ps` to verify status

release/1.5.1+v2.6.3

@@ -1 +0,0 @@
-patch to fix my tagging screw up

release/1.9.0+v3.0.1

@@ -1 +0,0 @@
-upgrade to immich 3 successfully deployed, but perhaps better check https://immich.app/blog/v3-migration if it affects your deployment