recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

upstream(immich): v3.1.0 sidecar pins (valkey 8e8d64b4…, postgres unchanged)

Browse Source
This commit is contained in:
autonomic-bot
2026-07-31 03:26:34 +00:00
parent 39c7d08dbd
commit 865eb45966
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cc-ci-plan/upstream/immich.md
+10
View File
@@ -30,6 +30,16 @@
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).
- **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).