diff --git a/clusters/base/apps/immich/helmrelease-ml.yaml b/clusters/base/apps/immich/helmrelease-ml.yaml
index 760a2ae..8a2ff6a 100644
--- a/clusters/base/apps/immich/helmrelease-ml.yaml
+++ b/clusters/base/apps/immich/helmrelease-ml.yaml
@@ -24,7 +24,7 @@ spec:
               # an internal API contract that isn't guaranteed compatible
               # across versions.
               repository: ghcr.io/immich-app/immich-machine-learning
-              tag: v2.7.5
+              tag: v3.1.0
             env:
               TZ: Europe/Moscow
             resources:
diff --git a/clusters/base/apps/immich/helmrelease-server.yaml b/clusters/base/apps/immich/helmrelease-server.yaml
index eaf7269..94cdd62 100644
--- a/clusters/base/apps/immich/helmrelease-server.yaml
+++ b/clusters/base/apps/immich/helmrelease-server.yaml
@@ -76,16 +76,8 @@ spec:
           app:
             image:
               repository: ghcr.io/immich-app/immich-server
-              # pinned to match the DB backup being restored
-              # (immich-db-backup-20260711T020000-v2.7.5-pg14.19.sql.gz) -
-              # a newer server expects a newer DB schema than what that
-              # backup contains, so it has to match at restore time. Once
-              # the restore is done and v2.7.5 has come up cleanly against
-              # it, bump back to "release" - v2.7.5's own migrations will
-              # carry the schema forward from there, which is the safe
-              # supported upgrade path (vs. jumping straight to a much
-              # newer server against a much older schema).
-              tag: v2.7.5
+              # make sure immich-machine-learning version match this 
+              tag: v3.1.0
             env:
               TZ: Europe/Moscow
               DB_HOSTNAME: immich-postgres