Upgrade immich v3.3.4 → v3.3.5 on top of the current upstream main (1.12.0+v3.3.4, 6b294fce).
This extends the existing upgrade PR #6 (branch upgrade-9c3bf2a) rather than opening a parallel one; the earlier v3.3.1 bump on that branch is superseded by this newer stable.
The DB and valkey digest pins are untouched. immich v3.3.5's own docker/docker-compose.yml pins the exact same postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357… and valkey:9@sha256:c123e371… combo, so the
PostgreSQL major/extension scheme remains in lockstep with the server. docker/example.env @ v3.3.5 is
byte-identical to v3.3.4.
Security patch release: dependency digest updates (certifi 2026.10.19 for the CA-trust fix) and the
October 2026 Node.js security patches. No schema migration, no new/renamed env var, no volume or routing
change. TypeORM migrations auto-run on start.
Operator Action Required
None. The version label is deliberately left untouched. After merge, publish with:
abra recipe release immich -z
(new upstream patch → patch bump; no --dry-run — this bumps the label, tags and pushes).
Verification
Live dev-immich.ci.commoninternet.net --chaos deploy of this exact tree: all 4 services 1/1; immich-server + immich-machine-learning running v3.3.5; /api/server/version → 3.3.5, /api/server/ping → pong, web root HTTP 200; migrations finished successfully; DB healthy with the vector/vchord extensions present (72 tables) — no pgvectors drop/panic. Dev deploy torn down
(0 dev-immich stacks/volumes remain).
Advisory scan (3.3.4 → 3.3.5): 0 CVEs identified as fixed by this window. CVE-2026-104867 is fixed
in v3.2.0 (before this window); the valkey CVEs relate to an unchanged sidecar. GitHub advisory API
sources were rate-limited on the last pass (noted in the run log).
Nothing is merged — for operator review.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
Upgrade **immich v3.3.4 → v3.3.5** on top of the current upstream main (`1.12.0+v3.3.4`, `6b294fce`).
This extends the existing upgrade PR #6 (branch `upgrade-9c3bf2a`) rather than opening a parallel one; the earlier v3.3.1 bump on that branch is superseded by this newer stable.
### Image changes
| service | image | current (upstream main) | new |
|---|---|---|---|
| app | `ghcr.io/immich-app/immich-server` | `v3.3.4` | **`v3.3.5`** |
| immich-machine-learning | `ghcr.io/immich-app/immich-machine-learning` | `v3.3.4` | **`v3.3.5`** |
| redis | `docker.io/valkey/valkey:9@sha256:418652cf…` | unchanged | unchanged |
| database | `ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` | unchanged | unchanged |
The DB and valkey digest pins are untouched. immich v3.3.5's own `docker/docker-compose.yml` pins the exact same
`postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…` and `valkey:9@sha256:c123e371…` combo, so the
PostgreSQL major/extension scheme remains in lockstep with the server. `docker/example.env` @ v3.3.5 is
byte-identical to v3.3.4.
**Upstream release notes:** immich-server v3.3.4→v3.3.5: https://github.com/immich-app/immich/releases/tag/v3.3.5
**Upstream release notes:** immich-machine-learning v3.3.4→v3.3.5: https://github.com/immich-app/immich/releases/tag/v3.3.5
### What changed (v3.3.4 → v3.3.5)
Security patch release: dependency digest updates (`certifi` 2026.10.19 for the CA-trust fix) and the
October 2026 Node.js security patches. No schema migration, no new/renamed env var, no volume or routing
change. TypeORM migrations auto-run on start.
### Operator Action Required
**None.** The version label is deliberately left untouched. After merge, publish with:
`abra recipe release immich -z`
(new upstream patch → patch bump; no `--dry-run` — this bumps the label, tags and pushes).
### Verification
- Live `dev-immich.ci.commoninternet.net --chaos` deploy of this exact tree: all 4 services **1/1**;
`immich-server` + `immich-machine-learning` running **v3.3.5**; `/api/server/version` → 3.3.5,
`/api/server/ping` → pong, web root HTTP 200; migrations finished successfully; DB healthy with the
`vector`/`vchord` extensions present (72 tables) — no pgvectors drop/panic. Dev deploy torn down
(0 `dev-immich` stacks/volumes remain).
- Advisory scan (3.3.4 → 3.3.5): 0 CVEs identified as fixed by this window. CVE-2026-104867 is fixed
in v3.2.0 (before this window); the valkey CVEs relate to an unchanged sidecar. GitHub advisory API
sources were rate-limited on the last pass (noted in the run log).
Nothing is merged — for 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
autonomic-bot
changed title from chore: upgrade immich-server + immich-machine-learning to v3.3.1 to chore: upgrade immich-server + immich-machine-learning to v3.3.52026-10-23 03:09:07 +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.
Upgrade immich v3.3.4 → v3.3.5 on top of the current upstream main (
1.12.0+v3.3.4,6b294fce).This extends the existing upgrade PR #6 (branch
upgrade-9c3bf2a) rather than opening a parallel one; the earlier v3.3.1 bump on that branch is superseded by this newer stable.Image changes
ghcr.io/immich-app/immich-serverv3.3.4v3.3.5ghcr.io/immich-app/immich-machine-learningv3.3.4v3.3.5docker.io/valkey/valkey:9@sha256:418652cf…ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…The DB and valkey digest pins are untouched. immich v3.3.5's own
docker/docker-compose.ymlpins the exact samepostgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357…andvalkey:9@sha256:c123e371…combo, so thePostgreSQL major/extension scheme remains in lockstep with the server.
docker/example.env@ v3.3.5 isbyte-identical to v3.3.4.
Upstream release notes: immich-server v3.3.4→v3.3.5: https://github.com/immich-app/immich/releases/tag/v3.3.5
Upstream release notes: immich-machine-learning v3.3.4→v3.3.5: https://github.com/immich-app/immich/releases/tag/v3.3.5
What changed (v3.3.4 → v3.3.5)
Security patch release: dependency digest updates (
certifi2026.10.19 for the CA-trust fix) and theOctober 2026 Node.js security patches. No schema migration, no new/renamed env var, no volume or routing
change. TypeORM migrations auto-run on start.
Operator Action Required
None. The version label is deliberately left untouched. After merge, publish with:
abra recipe release immich -z(new upstream patch → patch bump; no
--dry-run— this bumps the label, tags and pushes).Verification
dev-immich.ci.commoninternet.net --chaosdeploy of this exact tree: all 4 services 1/1;immich-server+immich-machine-learningrunning v3.3.5;/api/server/version→ 3.3.5,/api/server/ping→ pong, web root HTTP 200; migrations finished successfully; DB healthy with thevector/vchordextensions present (72 tables) — no pgvectors drop/panic. Dev deploy torn down(0
dev-immichstacks/volumes remain).in v3.2.0 (before this window); the valkey CVEs relate to an unchanged sidecar. GitHub advisory API
sources were rate-limited on the last pass (noted in the run log).
Nothing is merged — for 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
!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
chore: upgrade immich-server + immich-machine-learning to v3.3.1to chore: upgrade immich-server + immich-machine-learning to v3.3.5!testme
🌻 cc-ci —
immich@be7f7106✅ passedfull logs · dashboard