chore: upgrade immich-server to v3.0.3 #4
Reference in New Issue
Block a user
No description provided.
Delete Branch "upgrade-2dcc1c1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Recipe upgrade: immich v3.0.1 → v3.0.3 (PATCH bump; stacks v3.0.2 + v3.0.3 bugfix releases).
Image tag changes
ghcr.io/immich-app/immich-server:v3.0.1ghcr.io/immich-app/immich-server:v3.0.3ghcr.io/immich-app/immich-machine-learning:v3.0.1ghcr.io/immich-app/immich-machine-learning:v3.0.3valkey:9@sha256:3b55fbaa…valkey:9@sha256:4963247afc4cd…valkey:9has since moved to8e8d64b4…but that build is NOT tested with immich v3.0.3postgres:14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465…Upstream release notes
Upstream release notes: immich-server v3.0.1→v3.0.3: https://github.com/immich-app/immich/releases/tag/v3.0.3
Upstream release notes: immich-machine-learning v3.0.1→v3.0.3: https://github.com/immich-app/immich/releases/tag/v3.0.3
Full changelog v3.0.1...v3.0.3: https://github.com/immich-app/immich/compare/v3.0.1...v3.0.3
Operator notes
1782500000000-RestoreLivePhotoStillVisibility) — ran cleanly in the dev deploy below.3b55fbaa…(origin/main pin) to4963247afc4cd…= EXACTLY what immich v3.0.3's owndocker/docker-compose.ymlpins. The livevalkey:9tag has since been re-pointed to8e8d64b4…, but that newer 9.x build is NOT the combo immich v3.0.3 ships/tests against, so pinning to immich's shipped digest for reproducibility.docker buildx imagetools inspect.coop-cloud.${STACK_NAME}.versionlabel is left untouched in this PR (per convention); the operator runs the release command below to bump + tag + publish.Recommended release command (operator, after merge)
abra recipe release immich -zVerification
Chaos-deployed as
dev-immichon cc-ci from this branch head:Immich Microservices is running [v3.0.3], ML server healthy, DB migration1782500000000-RestoreLivePhotoStillVisibilitysucceeded, HTTP 200 via Traefik.!testmeresults below.Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
immich@2dcc1c1a✅ passedfull logs · dashboard
chore: re-pin valkey to 9.1.0to chore: upgrade to v3.0.1!testme
🌻 cc-ci —
immich@5bf5bdc4✅ passedfull logs · dashboard
chore: upgrade to v3.0.1to chore: upgrade to v3.0.2!testme
🌻 cc-ci —
immich@b81694ed✅ passedfull logs · dashboard
chore: upgrade to v3.0.2to chore: upgrade immich-server to v3.0.3!testme
🌻 cc-ci —
immich@f652ed33✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.