upstream(immich): postgres pgvectors 0.2.0->0.3.0 window notes

This commit is contained in:
2026-10-30 03:25:38 +00:00
parent 6234e36261
commit 7f3627e76c
+11
View File
@@ -123,6 +123,17 @@
migration, no config/env change, no breaking server-side change. Done in the 2026-10-23 upgrade migration, no config/env change, no breaking server-side change. Done in the 2026-10-23 upgrade
(v3.3.4→v3.3.5, app+ML only, extending PR #6; live v3.3.4→v3.3.5 dev deploy healthy — migrations finished, (v3.3.4→v3.3.5, app+ML only, extending PR #6; live v3.3.4→v3.3.5 dev deploy healthy — migrations finished,
`vector`/`vchord` present, no pgvectors drop; `!testme` GREEN first run — build #78). `vector`/`vchord` present, no pgvectors drop; `!testme` GREEN first run — build #78).
- **2026-10-30: postgres sidecar pgvectors 0.2.0 → 0.3.0 (same PG14 + VectorChord 0.4.3 scheme).** With
app/ML already at v3.3.5, the only newer same-scheme tag is
`ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.3.0` (multi-arch OCI index digest
`sha256:87c050465fb969a68c7ac23e375e21f4c95cfacd0edce5fa1bc31e63b7891891`; re-verified via ghcr +
`docker buildx imagetools inspect`). immich v3.3.5's own compose still names 0.2.0, but immich only
supports `vchord`/`vector` now — `vectors` (pgvecto.rs) is not in its `VECTOR_EXTENSIONS`, so the
sidecar library is unused; 0.3.0 is backward-compatible (`ALTER EXTENSION vectors UPDATE`), immich
added 0.3.0 support in immich-app/immich#11624, and this recipe previously shipped 0.3.0 with
v3.0.1/v2.7.5. Direct dev deploy: 0.2.0-created volume reused by the 0.3.0 task, PG14 clean start,
`vchord 0.4.3`/`vector 0.8.1` installed, `/api/server/version` = 3.3.5, `!testme` GREEN (build #105).
Recipe PR extends upstream main `ac03d23`; publish with `abra recipe release immich -z`.
- **2026-08-07 INFRA note: cc-ci runner's gitea clone-token is STALE (HTTP 401).** `!testme` build - **2026-08-07 INFRA note: cc-ci runner's gitea clone-token is STALE (HTTP 401).** `!testme` build
#1210 died at the recipe `git clone` step (~5s, before any deploy) with `could not read Username for #1210 died at the recipe `git clone` step (~5s, before any deploy) with `could not read Username for
'https://git.autonomic.zone'` — the runner's mounted gitea token `13e299f2…` is rejected (verified 'https://git.autonomic.zone'` — the runner's mounted gitea token `13e299f2…` is rejected (verified