admin
e459b0d262
Renovate PR #76 (merged 2026-06-06 10:48) bumped ghcr.io/immich-app/postgres from `16-vectorchord0.3.0` to `17-vectorchord0.3.0`. PostgreSQL major upgrades require pg_upgrade or pg_dump/restore — the new server binary refuses to open a data directory initialized by the previous major: FATAL: database files are incompatible with server DETAIL: The data directory was initialized by PostgreSQL version 16, which is not compatible with this version 17.6 Both immich-postgres and immich-server (depends on Postgres) went into CrashLoopBackOff. PVC still holds the v16 datadir. This PR: 1. Reverts ghcr.io/immich-app/postgres back to `16-vectorchord0.3.0` so immich recovers immediately. 2. Adds a packageRule with `dependencyDashboardApproval: true` covering `postgres`, `postgis/postgis`, and `ghcr.io/immich-app/postgres`. Any update to these images is now held on the Dashboard's "Pending Approval" section -- Renovate won't even open a PR until the user explicitly ticks the box. Forces the migration plan to be made BEFORE the change reaches main. This is the same recovery pattern we just used for meilisearch (PR #77) -- a class of stateful images where the on-disk format isn't forward-compatible across version bumps. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>