Extends this open upgrade PR (branch upgrade-9c3bf2a) with the newer upstream stable release v3.3.1 (2026-10-08) on top of the existing v3.2.4 bump. One evolving upgrade PR per recipe.
The redis re-pin follows immich's own docker/docker-compose.yml @ v3.3.1, which now ships valkey:9@sha256:c123e371… (9.1.2) — immich's tested combo (per the 2026-07-17 precedent: pin
immich's tested digest, NOT the live 9 tag, which has since drifted to 418652cf…). The database
pin is byte-identical to immich v3.3.1's compose (immich did not move vectorchord/pgvectors).
None required. v3.3.0 is a feature release (people sharing, birthday memories, auto-stacked
mobile edits, higher-quality thumbnails, OAuth claim sync on login) and v3.3.1 a bugfix patch; docker/example.env @ v3.3.1 is byte-identical to v3.2.4 (no new/renamed config, no new required
env var). TypeORM migrations (ConvertUserOAuthIdEmptyStringToNull, RenameGeoNamesCountries, PersonSharing, AddPersonUserTableSharedBySharedWithConstraint) auto-run on start and all succeeded
in a live v3.2.4→v3.3.1 deploy. Two opt-in items only: MACHINE_LEARNING_MODEL_REVISION=v2
(optimized ML models; numerically equivalent, no job re-run) and the people-sharing cluster-groups
feature (user-triggered; not a deploy migration).
Recommended release bump
New upstream features → minor bump. Operator, after merge, run verbatim: abra recipe release immich -y
(no --dry-run; bumps the label + tags + publishes — this PR deliberately leaves coop-cloud.${STACK_NAME}.version untouched).
Evidence
Direct dev-immich--chaos deploy on cc-ci: all 4 services 1/1; /api/server/version → {"major":3,"minor":3,"patch":1,"prerelease":null}; /api/server/ping → pong; web root HTTP 200;
all 4 migrations succeeded; torn down afterwards (0 stacks / 0 volumes).
Deterministic advisory scan: 0 CVEs identified as fixed by this window; CVE-2026-25243 (valkey,
vendor-page-only) still unclassified — not counted as fixed.
NOT merged — operator review.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
## immich upgrade — v3.2.4 → v3.3.1 (app + machine-learning) + valkey re-pin
Extends this open upgrade PR (branch `upgrade-9c3bf2a`) with the newer upstream stable release
**v3.3.1** (2026-10-08) on top of the existing v3.2.4 bump. One evolving upgrade PR per recipe.
### Image tag table
| service | image | current | new |
|---|---|---|---|
| app | ghcr.io/immich-app/immich-server | v3.2.4 | **v3.3.1** |
| immich-machine-learning | ghcr.io/immich-app/immich-machine-learning | v3.2.4 | **v3.3.1** |
| redis | docker.io/valkey/valkey:9 | 9.1.1 (`@sha256:70739f85…`) | 9.1.2 (`@sha256:c123e371…`) |
| database | ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0 | `@sha256:bcf63357…` | unchanged |
The redis re-pin follows immich's own `docker/docker-compose.yml` @ v3.3.1, which now ships
`valkey:9@sha256:c123e371…` (9.1.2) — immich's tested combo (per the 2026-07-17 precedent: pin
immich's tested digest, NOT the live `9` tag, which has since drifted to `418652cf…`). The `database`
pin is byte-identical to immich v3.3.1's compose (immich did not move vectorchord/pgvectors).
### Upstream release notes
**Upstream release notes:** app `ghcr.io/immich-app/immich-server` v3.2.4→v3.3.1: https://github.com/immich-app/immich/releases/tag/v3.3.1 (see also v3.3.0: https://github.com/immich-app/immich/releases/tag/v3.3.0)
**Upstream release notes:** immich-machine-learning v3.2.4→v3.3.1: https://github.com/immich-app/immich/releases/tag/v3.3.1
**Upstream release notes:** redis valkey 9.1.1→9.1.2: https://github.com/valkey-io/valkey/releases
### Operator Action Required
**None required.** v3.3.0 is a feature release (people sharing, birthday memories, auto-stacked
mobile edits, higher-quality thumbnails, OAuth claim sync on login) and v3.3.1 a bugfix patch;
`docker/example.env` @ v3.3.1 is **byte-identical** to v3.2.4 (no new/renamed config, no new required
env var). TypeORM migrations (`ConvertUserOAuthIdEmptyStringToNull`, `RenameGeoNamesCountries`,
`PersonSharing`, `AddPersonUserTableSharedBySharedWithConstraint`) auto-run on start and all succeeded
in a live v3.2.4→v3.3.1 deploy. Two **opt-in** items only: `MACHINE_LEARNING_MODEL_REVISION=v2`
(optimized ML models; numerically equivalent, no job re-run) and the people-sharing cluster-groups
feature (user-triggered; not a deploy migration).
### Recommended release bump
New upstream features → **minor** bump. Operator, after merge, run verbatim:
`abra recipe release immich -y`
(no `--dry-run`; bumps the label + tags + publishes — this PR deliberately leaves
`coop-cloud.${STACK_NAME}.version` untouched).
### Evidence
- Direct `dev-immich` `--chaos` deploy on cc-ci: all 4 services 1/1; `/api/server/version` →
`{"major":3,"minor":3,"patch":1,"prerelease":null}`; `/api/server/ping` → `pong`; web root HTTP 200;
all 4 migrations succeeded; torn down afterwards (0 stacks / 0 volumes).
- Deterministic advisory scan: 0 CVEs identified as fixed by this window; CVE-2026-25243 (valkey,
vendor-page-only) still unclassified — not counted as fixed.
- NOT merged — operator review.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
autonomic-bot
changed title from chore: upgrade immich-server + immich-machine-learning to v3.2.4 to chore: upgrade immich-server + immich-machine-learning to v3.3.12026-10-09 02:51:09 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
immich upgrade — v3.2.4 → v3.3.1 (app + machine-learning) + valkey re-pin
Extends this open upgrade PR (branch
upgrade-9c3bf2a) with the newer upstream stable releasev3.3.1 (2026-10-08) on top of the existing v3.2.4 bump. One evolving upgrade PR per recipe.
Image tag table
@sha256:70739f85…)@sha256:c123e371…)@sha256:bcf63357…The redis re-pin follows immich's own
docker/docker-compose.yml@ v3.3.1, which now shipsvalkey:9@sha256:c123e371…(9.1.2) — immich's tested combo (per the 2026-07-17 precedent: pinimmich's tested digest, NOT the live
9tag, which has since drifted to418652cf…). Thedatabasepin is byte-identical to immich v3.3.1's compose (immich did not move vectorchord/pgvectors).
Upstream release notes
Upstream release notes: app
ghcr.io/immich-app/immich-serverv3.2.4→v3.3.1: https://github.com/immich-app/immich/releases/tag/v3.3.1 (see also v3.3.0: https://github.com/immich-app/immich/releases/tag/v3.3.0)Upstream release notes: immich-machine-learning v3.2.4→v3.3.1: https://github.com/immich-app/immich/releases/tag/v3.3.1
Upstream release notes: redis valkey 9.1.1→9.1.2: https://github.com/valkey-io/valkey/releases
Operator Action Required
None required. v3.3.0 is a feature release (people sharing, birthday memories, auto-stacked
mobile edits, higher-quality thumbnails, OAuth claim sync on login) and v3.3.1 a bugfix patch;
docker/example.env@ v3.3.1 is byte-identical to v3.2.4 (no new/renamed config, no new requiredenv var). TypeORM migrations (
ConvertUserOAuthIdEmptyStringToNull,RenameGeoNamesCountries,PersonSharing,AddPersonUserTableSharedBySharedWithConstraint) auto-run on start and all succeededin a live v3.2.4→v3.3.1 deploy. Two opt-in items only:
MACHINE_LEARNING_MODEL_REVISION=v2(optimized ML models; numerically equivalent, no job re-run) and the people-sharing cluster-groups
feature (user-triggered; not a deploy migration).
Recommended release bump
New upstream features → minor bump. Operator, after merge, run verbatim:
abra recipe release immich -y(no
--dry-run; bumps the label + tags + publishes — this PR deliberately leavescoop-cloud.${STACK_NAME}.versionuntouched).Evidence
dev-immich--chaosdeploy on cc-ci: all 4 services 1/1;/api/server/version→{"major":3,"minor":3,"patch":1,"prerelease":null};/api/server/ping→pong; web root HTTP 200;all 4 migrations succeeded; torn down afterwards (0 stacks / 0 volumes).
vendor-page-only) still unclassified — not counted as fixed.
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@9c3bf2a0✅ passedfull logs · dashboard
chore: upgrade immich-server + immich-machine-learning to v3.2.4to chore: upgrade immich-server + immich-machine-learning to v3.3.1!testme
🌻 cc-ci —
immich@b4864537✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.