From c420e57f948db9a3273a9cf75b084bb8fb9d1bb1 Mon Sep 17 00:00:00 2001 From: autonomic-bot <64+autonomic-bot@noreply.git.autonomic.zone> Date: Fri, 20 Nov 2026 04:38:26 +0000 Subject: [PATCH] upstream(immich): release-notes sources --- cc-ci-plan/upstream/immich.md | 183 ++++------------------------------ 1 file changed, 22 insertions(+), 161 deletions(-) diff --git a/cc-ci-plan/upstream/immich.md b/cc-ci-plan/upstream/immich.md index 12c5878..ec892ac 100644 --- a/cc-ci-plan/upstream/immich.md +++ b/cc-ci-plan/upstream/immich.md @@ -1,164 +1,25 @@ -# Upstream sources — immich +# immich upstream sources -| service | image | source repo | releases / changelog | -|---------|-------|-------------|----------------------| -| app | ghcr.io/immich-app/immich-server | https://github.com/immich-app/immich | https://github.com/immich-app/immich/releases | -| immich-machine-learning | ghcr.io/immich-app/immich-machine-learning | https://github.com/immich-app/immich | https://github.com/immich-app/immich/releases | -| redis | docker.io/valkey/valkey | https://github.com/valkey-io/valkey | https://github.com/valkey-io/valkey/releases | -| database | ghcr.io/immich-app/postgres | https://github.com/immich-app/base-images | https://github.com/immich-app/immich/blob/main/docker/docker-compose.yml | +## ghcr.io/immich-app/immich-server +- image: ghcr.io/immich-app/immich-server +- source: https://github.com/immich-app/immich +- releases: https://github.com/immich-app/immich/releases +- security: https://github.com/immich-app/immich/security/advisories -## Standing notes +## ghcr.io/immich-app/immich-machine-learning +- image: ghcr.io/immich-app/immich-machine-learning +- source: https://github.com/immich-app/immich +- releases: https://github.com/immich-app/immich/releases +- security: https://github.com/immich-app/immich/security/advisories -- **DB image is pinned BY immich-server, not bumped independently.** abra cannot survey/upgrade this - recipe (`FATA … Docker references with both a tag and digest are currently not supported`) because - `database` is pinned `image:tag@sha256:…`. Use the box-item-4 direct check: the authoritative source - for the DB tag is **immich's own `docker/docker-compose.yml` at the immich-server release tag** - (`https://raw.githubusercontent.com/immich-app/immich//docker/docker-compose.yml`). Pin the - recipe's `database` image to EXACTLY what that compose pins for the matching immich-server version — - do NOT take the newest `ghcr.io/immich-app/postgres` tag. Newer tags (pg-15/16/17/18, - vectorchord0.5.x, pgvectors0.3.0) exist but moving ahead of what immich-server ships forces a - **pg-major data migration** and an unsupported extension combo. -- **immich-server v3.0.3 (latest, 2026-07-15) pins** (from its `docker/docker-compose.yml` at the - v3.0.3 tag): `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191…` and - `valkey:9@sha256:4963247afc4cd33c7d3b2d2816b9f7f8eeebab148d29056c2ca4d7cbc966f2d9` (same valkey - pin as v3.0.2). The recipe (origin/main, published `1.9.0+v3.0.1`) is AHEAD on - `postgres:14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465…` (pgvectors 0.2.0→0.3.0, backward- - compatible — keep it, do NOT downgrade to immich's 0.2.0). Digest re-verified identical via - `docker buildx imagetools inspect` on cc-ci (2026-07-17). The recipe's valkey pin - `valkey:9@sha256:3b55fbaa…` (origin/main) is a STALE old digest for tag `9`; immich v3.0.3 ships - `4963247afc4cd…`, so the recipe is re-pinned to that (the tested combo) — NOTE the *live* `valkey:9` - tag now resolves further to `sha256:8e8d64b4…` (newer 9.x build, NOT tested with immich v3.0.3), so - pin to immich's `4963247afc4cd…` for reproducibility, not the live tag digest. Refreshed to - `4963247afc4cd…` in the 2026-07-17 upgrade (v3.0.1→v3.0.3, extending PR #4). -- **immich-server v3.1.0 (2026-07-29) pins** (from its `docker/docker-compose.yml` at the v3.1.0 tag): - `valkey:9@sha256:8e8d64b405ce18f41b8e5ee20aa4687a8ed0022d1298f2ce31cdcf3a76e09411` - (a NEWER valkey build than v3.0.3's `4963247afc4cd…` — this `8e8d64b4…` is the same digest the live `9` - tag had already moved to at the 2026-07-17 run; immich v3.1.0 now officially ships it, so it IS the - immich-tested combo → re-pin the recipe's `redis` service to `8e8d64b4…` for the v3.1.0 upgrade) and - `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191…` (SAME combo as v3.0.3 — immich did NOT - bump vectorchord/pgvectors, so the recipe STAYS AHEAD on `pgvectors0.3.0@sha256:87c050465…`; do NOT - downgrade). Only **breaking change in v3.1.0** is `chore(mobile): drop support for iOS 14` (mobile - client, NOT server-side — no server migration, no DB migration, no operator action for the recipe). - Done in the 2026-07-31 upgrade (v3.0.1→v3.1.0, extending PR #4 again). -- **2026-08-07: upstream main MOVED to v3.1.0 (published `1.10.0+v3.1.0`, commit `794560f`).** The - coopcloud maintainer published v3.1.0 independently of PR #4 (PR #4 tip `77d7937` is NOT in upstream - main, so the reconcile leaves it open — functionally superseded on the version bump). Upstream main - pins: `immich-server/ML v3.1.0`, `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf633…` (immich's - OFFICIAL v3.1.0 combo — a DOWNGRADE from the recipe's prior `pgvectors0.3.0@87c0…`), and - `valkey:9@sha256:3acc0687f2a2e1091fae6450d7842dd658c941338cf0a873ddd9e14b9e4ea4dd` (DIVERGES from - immich v3.1.0's official valkey pin `8e8d64b4…` — upstream pin hygiene discrepancy, not an upgrade). - Immich is now **up-to-date** (v3.1.0 is latest stable per GitHub releases; no v3.1.x patch / v3.2.x). - PR #4 now diverges from upstream main only on `database` (pgvectors0.3.0 vs 0.2.0) + `redis` - (valkey:9@8e8d64b4 vs @3acc0687) pins — operator decides merge-vs-close. -- **immich-server v3.2.0 (2026-09-10) pins** (from its `docker/docker-compose.yml` at the v3.2.0 tag): - `valkey:9@sha256:70739f85ad2ee01a726a965584a0f94895f01b0c60b3cc8b0aeef11eaa6888cf` - (= valkey **9.1.1** per image env; a NEWER build than v3.1.0's `8e8d64b4…` = 9.1.0 — but OLDER - than the live `9` tag, which by 2026-09-11 moved to `c123e371…` = 9.1.2; pin immich's tested - `70739f85…`, NOT the live tag, per the 2026-07-17 precedent) and - `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` (SAME combo as v3.1.0 — DB - unchanged). No breaking server-side changes in v3.2.0; `example.env` byte-identical to v3.1.0; - TypeORM migrations auto-run. Operator-info only: the new opt-in cluster-groups feature requires - a per-group facial-recognition reset (user-triggered button, not a deploy migration). **ghcr - pagination gotcha (hit 2026-09-11):** `ghcr.io/v2/immich-app/postgres/tags/list` pages are ~100 - tags, NOT purely lexicographic, and the `Link:` header returns a RELATIVE url (`/v2/...`) — - prefix the host or pagination silently stops at page 1; the pinned pg tag `14-vectorchord0.4.3- - pgvectors0.2.0` is on **page 2** of 174 (a first-page probe wrongly suggests it's gone). Upstream - coopcloud has open renovate PRs #18 (v3.2.0 monorepo bump = server+ML only), #17 (valkey digest - → live c123e37 — not immich's tested pin), #16 (postgres → pg16 — unsupported by immich v3.2.0, - reject). Done in the 2026-09-11 upgrade (v3.1.0→v3.2.0, extending PR #4 from upstream main - 794560f; PR #4's pgvectors0.3.0/valkey-8e8d64b4 divergences superseded — DB realigned to - immich's official combo, which upstream main itself chose 2026-08-07). -- **immich-server v3.2.1 (2026-09-14) + v3.2.2 (2026-09-15) pins** (from `docker/docker-compose.yml` - @ the v3.2.2 tag): `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` and - `valkey:9@sha256:70739f85ad…` — **BOTH identical to the recipe's v3.2.0-era pins** (DB and - redis stay put; live valkey `9` tag has drifted to `c123e371…` = 9.1.2 but immich's tested - pin `70739f85…` = 9.1.1 is kept per the 2026-07-17 precedent; live postgres tag digest - re-verified = the pin, not stale). `example.env` @ v3.2.2 byte-identical to v3.2.0. Both - releases are bug-fix-only (v3.2.1: sync connection-pool exhaustion, search modal, partner - assets on people page, person merge, server auto-VACUUM after TypeORM migrations; v3.2.2: - reassign-faces fix) — no breaking changes, no config additions, no operator action. Done in - the 2026-09-18 upgrade (v3.2.0→v3.2.2, app+ML only; fresh PR — PR #4 was closed when its - v3.2.0 content merged upstream as #19 / `1.11.0+v3.2.0`). -- **immich-server v3.2.4 (2026-09-28, latest stable) pins** (from `docker/docker-compose.yml` @ the - v3.2.4 tag): `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` and - `valkey:9@sha256:70739f85ad…` — **BOTH identical to the recipe's v3.2.2-era pins** (DB + redis stay - put; live `valkey:9` tag has now moved to `ac9c858b…` = **9.1.2**, but immich's tested - `70739f85…` = 9.1.1 is kept per the 2026-07-17 precedent). `example.env` @ v3.2.4 byte-identical to - v3.2.2. Window v3.2.2→v3.2.4 is 4 commits: mobile sync-status fix (#31644), an internal `v3.2.3` - version commit (no Release object), a base-image dep bump to `202609281550` (#31854), and `v3.2.4`. - The v3.2.4 release body: "small patch that primarily fixes the memory leak people have observed - through a dependency update." **No breaking changes, no config additions, no operator action.** - The base-image bump (`202608300913`→`202609281550`, immich-app/base-images) adds a hardened - ImageMagick security policy (#390), reduces server image size (#388), and restores `curl` in the - prod image so `immich-healthcheck` works (#391) — all internal to the server image. `v3.3.0-rc.0/1` - are pre-releases (2026-09-29/30) — do NOT bump to rc. Done in the 2026-10-02 upgrade - (v3.2.2→v3.2.4, app+ML only, fresh PR). Direct registry check confirmed - `immich-server/ml:v3.2.4` exist; `abra recipe upgrade` still FATAs on the tag+digest DB pin. - Valkey CVE note: CVE-2026-56684 / CVE-2026-63639 (UAF→RCE) are fixed in 9.1.1 and are therefore - ** already closed** by the recipe's pinned 9.1.1 — not by this app bump; ignore the live-`9`-tag - drift. CVE-2026-25243 (valkey RESTORE zipmap) is vendor-page-only and undecided. -- **immich-server v3.3.0 (2026-10-07) + v3.3.1 (2026-10-08, latest stable) pins** (from - `docker/docker-compose.yml` @ the v3.3.1 tag): `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` - (UNCHANGED vs v3.2.4) and `valkey:9@sha256:c123e3715db63d06d4ad6964884037aa0d5d4d703939b9929954112889708e1d` - — the **valkey pin moved** 9.1.1 (`70739f85…`) → **9.1.2 (`c123e371…`)**, which is now immich's own - official tested pin (the live `9` tag has since drifted to `418652cf…`; keep immich's `c123e371…` - per the 2026-07-17 precedent). `example.env` @ v3.3.1 is **byte-identical** to v3.2.4. v3.3.0 is a - feature release (people sharing / cluster groups, birthday memories, auto-stacked mobile edits, - higher-quality thumbnails via linear-light resampling, OAuth claims synced on every login, PP-OCRv6 - OCR models); v3.3.1 is a patch (people-sharing + mobile scroll fixes). **No breaking server-side - changes, no required config, no operator action.** New TypeORM migrations auto-run - (`ConvertUserOAuthIdEmptyStringToNull`, `RenameGeoNamesCountries`, `PersonSharing`, - `AddPersonUserTableSharedBySharedWithConstraint`) — all succeeded in a live v3.2.4→v3.3.1 deploy. - Opt-in only: `MACHINE_LEARNING_MODEL_REVISION=v2` (optimized models, numerically equivalent, no job - re-run) and the people-sharing feature (user-triggered button, not a deploy migration). Done in the - 2026-10-09 upgrade (v3.2.4→v3.3.1, app+ML+valkey, extending PR #6; fresh `!testme` GREEN — build #45). -- **immich-server v3.3.3 (2026-10-14) + v3.3.4 (2026-10-20) + v3.3.5 (2026-10-21, latest stable) pins** (from - `docker/docker-compose.yml` @ the v3.3.5 tag): `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` - (UNCHANGED since v3.3.0) and `valkey:9@sha256:c123e371…` (immich's tested 9.1.2, also unchanged). Upstream - coopcloud published v3.3.4 as `1.12.0+v3.3.4` (`6b294fce`) and moved the recipe's `redis` pin to the then-live - `418652cf…`; that divergence is left as upstream has it (no reason to churn a sidecar in an app bump). - `docker/docker-compose.yml` and `docker/example.env` are byte-identical between v3.3.4 and v3.3.5. - v3.3.3 = bug fixes (mobile memories date, people-query perf); v3.3.4 = further people-query perf + translation; - **v3.3.5 = security patch** (certifi CA-trust fix + October 2026 Node.js security patches). No schema - migration, no config/env change, no breaking server-side change. Done in the 2026-10-23 upgrade - (v3.3.4→v3.3.5, app+ML only, extending PR #6; live v3.3.4→v3.3.5 dev deploy healthy — migrations finished, - `vector`/`vchord` present, no pgvectors drop; `!testme` GREEN first run — build #78). -- **2026-10-30: postgres sidecar pgvectors 0.2.0 → 0.3.0 (same PG14 + VectorChord 0.4.3 scheme).** With - app/ML already at v3.3.5, the only newer same-scheme tag is - `ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.3.0` (multi-arch OCI index digest - `sha256:87c050465fb969a68c7ac23e375e21f4c95cfacd0edce5fa1bc31e63b7891891`; re-verified via ghcr + - `docker buildx imagetools inspect`). immich v3.3.5's own compose still names 0.2.0, but immich only - supports `vchord`/`vector` now — `vectors` (pgvecto.rs) is not in its `VECTOR_EXTENSIONS`, so the - sidecar library is unused; 0.3.0 is backward-compatible (`ALTER EXTENSION vectors UPDATE`), immich - added 0.3.0 support in immich-app/immich#11624, and this recipe previously shipped 0.3.0 with - v3.0.1/v2.7.5. Direct dev deploy: 0.2.0-created volume reused by the 0.3.0 task, PG14 clean start, - `vchord 0.4.3`/`vector 0.8.1` installed, `/api/server/version` = 3.3.5, `!testme` GREEN (build #105). - Recipe PR extends upstream main `ac03d23`; publish with `abra recipe release immich -z`. -- **2026-08-07 INFRA note: cc-ci runner's gitea clone-token is STALE (HTTP 401).** `!testme` build - #1210 died at the recipe `git clone` step (~5s, before any deploy) with `could not read Username for - 'https://git.autonomic.zone'` — the runner's mounted gitea token `13e299f2…` is rejected (verified - HTTP 401 on the gitea API + git endpoint; `.testenv` basic creds work). PR #4's tree `77d79379` was - GREEN on #1145 (2026-07-31) & #1180 (2026-08-04) — the RED is infra, not the recipe. Fix: rotate the - runner's gitea clone-token (swarm secret), then re-`!testme`. (The 2026-08-04 Drone-direct - `GITEA_TOKEN`-as-build-param workaround is disallowed for normal runs.) -- **Historical (v2.7.5, 2026-04-13):** immich-server v2.7.5 pinned - `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191…`. PR #2 bumped the recipe to - `pgvectors0.3.0@sha256:87c050465…` (same PG14 + VectorChord 0.4.3, newer pgvectors 0.2.0→0.3.0). -- **Concurrent app+database restart needs `update_config: failure_action: continue` on the app service.** - When the recipe version label changes (bumping `coop-cloud.${STACK_NAME}.version`) AND the database - image changes in the same deploy, both services update simultaneously. The app container starts and - immediately tries TypeORM migrations against a still-restarting database → TypeORM connection fails → - app process crashes → task FAILED → Docker Swarm sets `UpdateStatus='paused'` (default - `failure_action: pause`). Fix: set `update_config: failure_action: continue` on the app service. - With `continue`, Docker Swarm records the update as `completed` and Docker's `restart_policy` retries - the app container; the database finishes restarting in ~15-20s and the app connects successfully. - This is also in the recipe as of PR #2. -- **VectorChord DB backup/restore needs the search_path sed.** A plain `pg_dump` of the - VectorChord/pgvecto.rs DB emits `SELECT pg_catalog.set_config('search_path', '', false);`. Importing - that as-is leaves the vector/vchord type + operator references unresolvable, so the first such - statement errors. immich's official restore (docs.immich.app/administration/backup-and-restore) pipes - the dump through: - `sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g"` - before `psql … --single-transaction --set ON_ERROR_STOP=on`. Omitting that sed (immich PR #1's - `pg_backup.sh`) is why the single-transaction import aborted wholesale and `ci_marker` was lost on - restore — fixed in the upgrade PR's `pg_backup.sh`. +## ghcr.io/immich-app/postgres +- image: ghcr.io/immich-app/postgres +- source: https://github.com/immich-app/immich (the image is built in-repo under docker/; there is no separate immich-app/postgres repo) +- releases: https://github.com/immich-app/immich/releases +- security: https://github.com/immich-app/immich/security/advisories + +## docker.io/valkey/valkey +- image: valkey/valkey +- source: https://github.com/valkey-io/valkey +- releases: https://github.com/valkey-io/valkey/releases +- security: https://github.com/valkey-io/valkey/security/advisories