Merge pull request 'fix(URGENT): pin umami to exact SHA (v1.38.0 has schema lineage mismatch)' (#3) from fix/umami-sha-pin into main

2026-06-06 11:53:55 +00:00
parent a964dc20a4 7e6ea9d66c
commit dc64bb2d79
1 changed files with 9 additions and 1 deletions
@@ -187,7 +187,15 @@ spec:
              cpu: "50m"
      containers:
        - name: umami
-          image: ghcr.io/umami-software/umami:postgresql-v1.38.0
+          # NOTE: pinned to the exact image SHA the working 120d-old pod
+          # is on. v1.38.0 (the latest postgresql-vX.Y.Z) tries to apply
+          # migration `02_add_event_data` which requires an `event` table
+          # that this DB doesn't have -- the DB schema is older than v1
+          # numbered migrations expect. Until we plan a proper migration
+          # (likely to umami v3.x, which is what the dashboard `→ 3.1`
+          # hint suggests), this stays SHA-pinned so Renovate doesn't
+          # touch it and pod restarts don't roll the version forward.
+          image: ghcr.io/umami-software/umami@sha256:28f263fe06f79ebffa5a6a6e9bd33b7a278e9342a88e0bdac812416c9f9e4361
          ports:
            - containerPort: 3000
          env: