feat: umami 3.1.0 + filebrowser v2.63.13 (root) #4

2026-06-06T14:17:20+02:00

admin commented

2026-06-06 14:17:20 +02:00

umami: SHA-pinned v3.0.3 -> tagged 3.1.0 (proper v3 line)
filebrowser: v2-alpine -> v2.63.13 with pod-level runAsUser: 0 / runAsGroup: 0 so the non-root default UID can still write to the PVC files left by the previous root-running alpine image.

🤖 Generated with Claude Code

- umami: SHA-pinned v3.0.3 -> tagged `3.1.0` (proper v3 line) - filebrowser: v2-alpine -> `v2.63.13` with pod-level `runAsUser: 0 / runAsGroup: 0` so the non-root default UID can still write to the PVC files left by the previous root-running alpine image. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

admin added 1 commit 2026-06-06 14:17:21 +02:00

manifests: umami -> 3.1.0 (v3 line) + filebrowser v2.63.13 with runAsUser:0 bd0531e4a8

umami:
  Switch from SHA-pinned v3.0.3 to the tagged v3.1.0 release (the v3
  line proper -- same schema lineage, normal Prisma minor-version
  migration). This is the documented forward path that the version-
  checker hint `postgresql-latest -> 3.1` indicated. The v1.x
  postgresql-vX.Y.Z line we briefly tried earlier today is a
  DIFFERENT image lineage with incompatible migrations -- avoid.

filebrowser:
  Re-pin to v2.63.13 (debian-based default) so Renovate can track
  future bumps. The non-root UID in that image can't write to the
  existing PVC contents (chowned to root by the previous v2-alpine
  image), so set pod-level securityContext runAsUser:0 + runAsGroup:0
  to keep using the same volume layout without a chown initContainer.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

admin merged commit 87b062e84a into main

2026-06-06 14:17:22 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: admin/felhom.eu#4