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

upstream(immich): note pgvectors0.3.0 bump in PR #2 + new digest (2026-06-12)

Browse Source
This commit is contained in:
autonomic-bot
2026-06-12 02:50:45 +00:00
parent 2c5e08f78c
commit 28b9431035
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
cc-ci-plan/upstream/immich.md
View File

@ -20,7 +20,10 @@
**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`
— verified against immich's v2.7.5 compose AND the live ghcr manifest (tag resolves to that exact
digest). This is identical to what the recipe already pins, so **no DB image change for v2.7.5**.
digest). PR #2 (`upgrade-1.7.0+v2.7.5`, now at head d561baa `1.8.0+v2.7.5`) bumps the database
image to `14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465fb969a68c7ac23e375e21f4c95cfacd0edce5fa1bc31e63b7891891`
(same PG14 + VectorChord 0.4.3, newer pgvectors 0.2.0→0.3.0). Digest verified via
`docker buildx imagetools inspect` on cc-ci (2026-06-12).
- **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