Merge pull request 'manifests: re-pin moving tags (umami / filebrowser)' (#1) from fix/version-pins into main

manifests/umami.yaml

@@ -187,15 +187,7 @@ spec:
               cpu: "50m"
       containers:
         - name: umami
-          # 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
+          image: ghcr.io/umami-software/umami:postgresql-v1.38.0
           ports:
             - containerPort: 3000
           env:

manifests/webpage.yaml

@@ -107,12 +107,7 @@ spec:
     spec:
       containers:
         - name: filebrowser
-          # NOTE: v2-alpine is a moving tag (Renovate can't track it).
-          # Pinning to v2.63.13 (debian-based default) broke the PVC permissions
-          # (the image runs as a non-root UID and can't write to files left
-          # by the alpine variant). A clean re-pin needs either an initContainer
-          # to chown the PVC, or a fsGroup on the pod spec. Revisit when time permits.
-          image: filebrowser/filebrowser:v2-alpine
+          image: filebrowser/filebrowser:v2.63.13
           ports:
             - containerPort: 8080
           volumeMounts: