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

upstream(immich): v3.0.2 pins (valkey:9 digest refreshed, postgres pgvectors0.3.0 unchanged)

Browse Source
This commit is contained in:
autonomic-bot
2026-07-13 20:08:45 +00:00
parent c1695dcf72
commit 82ae406667
1 changed files with 13 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cc-ci-plan/upstream/immich.md
+13 -6
View File
@@ -18,12 +18,19 @@
do NOT take the newest `ghcr.io/immich-app/postgres` tag. Newer tags (pg-15/16/17/18, 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 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. **pg-major data migration** and an unsupported extension combo.
- **immich-server v2.7.5 (latest, 2026-04-13) pins** `ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23` - **immich-server v3.0.2 (latest, 2026-07-09) pins** (from its `docker/docker-compose.yml` at the
— verified against immich's v2.7.5 compose AND the live ghcr manifest (tag resolves to that exact v3.0.2 tag): `postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191…` and
digest). PR #2 (`upgrade-1.7.0+v2.7.5`, now at head d561baa `1.8.0+v2.7.5`) bumps the database `valkey:9@sha256:4963247afc4cd33c7d3b2d2816b9f7f8eeebab148d29056c2ca4d7cbc966f2d9`.
image to `14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465fb969a68c7ac23e375e21f4c95cfacd0edce5fa1bc31e63b7891891` The recipe (origin/main, published `1.9.0+v3.0.1`) is AHEAD on
(same PG14 + VectorChord 0.4.3, newer pgvectors 0.2.0→0.3.0). Digest verified via `postgres:14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465…` (pgvectors 0.2.0→0.3.0, backward-
`docker buildx imagetools inspect` on cc-ci (2026-06-12). 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-13). The recipe's valkey pin
`valkey:9@sha256:3b55fbaa…` was a STALE old digest for tag `9`; `valkey:9` now resolves to
`sha256:4963247afc4cd…` (= immich v3.0.2's pin = `valkey:9.1.0`, the newest 9.x; no 9.1.1/9.2.x
exists). Refreshed the digest to `4963247afc4cd…` in the 2026-07-13 upgrade (v3.0.1→v3.0.2).
- **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.** - **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 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 image changes in the same deploy, both services update simultaneously. The app container starts and