Recipe upgrade: immich app + ML v3.3.5 → v3.4.1 (extends this PR with the app/ML bump on top of the pgvectors 0.2.0 → 0.3.0 Postgres bump already here).
14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465… (already in this PR; OCI-index digest re-verified)
redis
docker.io/valkey/valkey
9@sha256:418652cf…
unchanged (matches v3.4.1's official pin)
v3.4.1 is the newest stable upstream release (2026-11-11); v3.4.0-rc.* are pre-releases and are not taken. The Postgres sidecar stays on the same PG14 + VectorChord 0.4.3 scheme — its pgvectors 0.2.0 → 0.3.0 bump is already in this PR, is backward-compatible, and immich only uses vchord/vector now. Do not take pg15/16/17/18.
What's in the window (v3.3.5 → v3.4.1)
v3.3.6 (2026-11-04): privacy/bug-fix patch — disables onnxruntime telemetry in the ML container (immich-app/immich#32956).
v3.4.0 (2026-11-10): feature release — workflow improvements (EXIF missing/present match, OCR extraction trigger/filter), JPEG XL support, mobile tags, backups improvements, camera make/model display fixes, and a batch of security fixes (shared-link visibility, plugin allowedHosts anchoring, upload-access checksum check, email-template escaping, CSP inline hashes). No server-side breaking change, no new/renamed config, no manual DB step — new TypeORM migrations auto-run. docker/example.env is byte-identical to v3.3.6.
Direct --chaos dev deploy on cc-ci of this branch (bb25663) against upstream main ac03d237: all 4 services converged 1/1.
app + ML v3.4.1 running; /api/server/version = {"major":3,"minor":4,"patch":1,...}; /api/server/ping = {"res":"pong"}; ML server healthy.
Postgres 14.19 on the pgvectors0.3.0 image; extensions vchord 0.4.3 + vector 0.8.1 present. 104 Kysely migrations applied, including the v3.4.0 AddUpdateIdIndexes, AddAssetOwnerIdUpdateIdIndex, AddPasskeyTable, AddAssetFaceAssetState; new futo_backups_* tables present.
Dev deploy torn down completely (0 stacks, 0 volumes, 0 networks, 0 abra apps).
abra recipe lint immich -C -n: only pre-existing warnings (R002 healthchecks, R005 semver-like tags); no errors.
Advisory scan for 3.3.5 → 3.4.1: 0 CVEs determined fixed, plus 17 security advisories without CVE ids. The 8 unjudged adjudicated as outside this window: six legacy nvd:postgres entries name unrelated packages not present in the image (postgresql-ocaml, PL/php, pgbouncer, Quassel, gin-vue-admin, aiven-extras); CVE-2026-104867 has range >= 3.0.0, <= 3.0.3 and GHSA-h5w4-vjv4-9r5q <= v3.1.0, both already behind 3.3.5 before this window.
Operator Action Required
None. After merge, publish with:
abra recipe release immich -y
(minor bump; no --dry-run). The PR deliberately does not bump the coop-cloud.${STACK_NAME}.version label.
Recipe upgrade: immich app + ML **v3.3.5 → v3.4.1** (extends this PR with the app/ML bump on top of the pgvectors `0.2.0 → 0.3.0` Postgres bump already here).
## Image tag table
| service | image | current (upstream main) | new |
|---|---|---|---|
| app | ghcr.io/immich-app/immich-server | v3.3.5 | **v3.4.1** |
| immich-machine-learning | ghcr.io/immich-app/immich-machine-learning | v3.3.5 | **v3.4.1** |
| database | ghcr.io/immich-app/postgres | `14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` | **`14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465…`** (already in this PR; OCI-index digest re-verified) |
| redis | docker.io/valkey/valkey | `9@sha256:418652cf…` | unchanged (matches v3.4.1's official pin) |
v3.4.1 is the newest **stable** upstream release (2026-11-11); `v3.4.0-rc.*` are pre-releases and are not taken. The Postgres sidecar stays on the same PG14 + VectorChord 0.4.3 scheme — its `pgvectors 0.2.0 → 0.3.0` bump is already in this PR, is backward-compatible, and immich only uses `vchord`/`vector` now. Do **not** take pg15/16/17/18.
## What's in the window (v3.3.5 → v3.4.1)
- **v3.3.6** (2026-11-04): privacy/bug-fix patch — disables onnxruntime telemetry in the ML container (immich-app/immich#32956).
- **v3.4.0** (2026-11-10): feature release — workflow improvements (EXIF missing/present match, OCR extraction trigger/filter), JPEG XL support, mobile tags, backups improvements, camera make/model display fixes, and a batch of security fixes (shared-link visibility, plugin `allowedHosts` anchoring, upload-access checksum check, email-template escaping, CSP inline hashes). No server-side breaking change, no new/renamed config, no manual DB step — new TypeORM migrations auto-run. `docker/example.env` is byte-identical to v3.3.6.
- **v3.4.1** (2026-11-11): patch — shared-link cover-query performance, queue job-status query, HEIF mime mapping, workflow defaults, prometheus exporter bind, futo backups 1.16.0.
## Verification
- Direct `--chaos` dev deploy on cc-ci of this branch (`bb25663`) against upstream main `ac03d237`: all 4 services converged 1/1.
- app + ML **v3.4.1** running; `/api/server/version` = `{"major":3,"minor":4,"patch":1,...}`; `/api/server/ping` = `{"res":"pong"}`; ML server healthy.
- Postgres **14.19** on the `pgvectors0.3.0` image; extensions `vchord 0.4.3` + `vector 0.8.1` present. 104 Kysely migrations applied, including the v3.4.0 `AddUpdateIdIndexes`, `AddAssetOwnerIdUpdateIdIndex`, `AddPasskeyTable`, `AddAssetFaceAssetState`; new `futo_backups_*` tables present.
- Dev deploy torn down completely (0 stacks, 0 volumes, 0 networks, 0 abra apps).
- `abra recipe lint immich -C -n`: only pre-existing warnings (R002 healthchecks, R005 semver-like tags); no errors.
- Advisory scan for 3.3.5 → 3.4.1: **0 CVEs** determined fixed, plus 17 security advisories without CVE ids. The 8 unjudged adjudicated as outside this window: six legacy `nvd:postgres` entries name unrelated packages not present in the image (postgresql-ocaml, PL/php, pgbouncer, Quassel, gin-vue-admin, aiven-extras); CVE-2026-104867 has range `>= 3.0.0, <= 3.0.3` and GHSA-h5w4-vjv4-9r5q `<= v3.1.0`, both already behind 3.3.5 before this window.
## Operator Action Required
**None.** After merge, publish with:
```
abra recipe release immich -y
```
(minor bump; no `--dry-run`). The PR deliberately does not bump the `coop-cloud.${STACK_NAME}.version` label.
## Upstream release notes
- **Upstream release notes:** immich-server v3.3.5→v3.4.1: https://github.com/immich-app/immich/releases/tag/v3.4.0 and https://github.com/immich-app/immich/releases/tag/v3.4.1 (plus https://github.com/immich-app/immich/releases/tag/v3.3.6 for the intermediate patch)
- **Upstream release notes:** immich-machine-learning v3.3.5→v3.4.1: same monorepo releases (ML-specific change is immich-app/immich#32956)
- **Upstream release notes:** postgres pgvectors 0.2.0→0.3.0 (already in this PR): https://github.com/immich-app/base-images and https://github.com/immich-app/immich/blob/v3.4.1/docker/docker-compose.yml
NOT merged — for operator review.
CI verification is run against this one-commit PR head. NOT merged — for operator review.
cc @trav @notplants
autonomic-bot
requested review from trav 2026-10-30 03:20:26 +00:00
autonomic-bot
requested review from notplants 2026-10-30 03:20:26 +00:00
autonomic-bot
changed title from chore: bump postgres database to pgvectors 0.3.0 to chore: upgrade immich-server + immich-machine-learning to v3.3.62026-11-06 04:05:43 +00:00
autonomic-bot
changed title from chore: upgrade immich-server + immich-machine-learning to v3.3.6 to chore: upgrade immich-server + immich-machine-learning to v3.4.12026-11-13 04:42:57 +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.
Recipe upgrade: immich app + ML v3.3.5 → v3.4.1 (extends this PR with the app/ML bump on top of the pgvectors
0.2.0 → 0.3.0Postgres bump already here).Image tag table
14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465…(already in this PR; OCI-index digest re-verified)9@sha256:418652cf…v3.4.1 is the newest stable upstream release (2026-11-11);
v3.4.0-rc.*are pre-releases and are not taken. The Postgres sidecar stays on the same PG14 + VectorChord 0.4.3 scheme — itspgvectors 0.2.0 → 0.3.0bump is already in this PR, is backward-compatible, and immich only usesvchord/vectornow. Do not take pg15/16/17/18.What's in the window (v3.3.5 → v3.4.1)
allowedHostsanchoring, upload-access checksum check, email-template escaping, CSP inline hashes). No server-side breaking change, no new/renamed config, no manual DB step — new TypeORM migrations auto-run.docker/example.envis byte-identical to v3.3.6.Verification
--chaosdev deploy on cc-ci of this branch (bb25663) against upstream mainac03d237: all 4 services converged 1/1./api/server/version={"major":3,"minor":4,"patch":1,...};/api/server/ping={"res":"pong"}; ML server healthy.pgvectors0.3.0image; extensionsvchord 0.4.3+vector 0.8.1present. 104 Kysely migrations applied, including the v3.4.0AddUpdateIdIndexes,AddAssetOwnerIdUpdateIdIndex,AddPasskeyTable,AddAssetFaceAssetState; newfuto_backups_*tables present.abra recipe lint immich -C -n: only pre-existing warnings (R002 healthchecks, R005 semver-like tags); no errors.nvd:postgresentries name unrelated packages not present in the image (postgresql-ocaml, PL/php, pgbouncer, Quassel, gin-vue-admin, aiven-extras); CVE-2026-104867 has range>= 3.0.0, <= 3.0.3and GHSA-h5w4-vjv4-9r5q<= v3.1.0, both already behind 3.3.5 before this window.Operator Action Required
None. After merge, publish with:
(minor bump; no
--dry-run). The PR deliberately does not bump thecoop-cloud.${STACK_NAME}.versionlabel.Upstream release notes
NOT merged — for operator review.
CI verification is run against this one-commit PR head. NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
immich@539fae96✅ passedfull logs · dashboard
chore: bump postgres database to pgvectors 0.3.0to chore: upgrade immich-server + immich-machine-learning to v3.3.6!testme
🌻 cc-ci —
immich@e455d422✅ passedfull logs · dashboard
chore: upgrade immich-server + immich-machine-learning to v3.3.6to chore: upgrade immich-server + immich-machine-learning to v3.4.1e455d422a8to926ee88176!testme
🌻 cc-ci —
immich@926ee881✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.