[PR #87] [CLOSED] Review MariaDB 11.4 → 11.7 container update for Invoice Ninja #277

Closed
opened 2026-06-08 08:31:11 +00:00 by ryangr0 · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/webgrip/homelab-cluster/pull/87
Author: @Copilot
Created: 5/22/2026
Status: Closed

Base: mainHead: copilot/renovate-agent-review-79


📝 Commits (1)

📄 Description

This updates the Renovate review for the MariaDB image bump used by Invoice Ninja. The review focuses on the actual deployment surface in this repo and the upstream MariaDB/Docker upgrade path, with emphasis on stateful upgrade risk rather than image pinning.

  • What changed

    • Reviewed the live PR diff for kubernetes/apps/invoiceninja/invoiceninja/app/mariadb.yaml
    • Mapped local usage across the Invoice Ninja deployment, config, and PVC manifests
    • Cross-checked upstream MariaDB 11.5 / 11.6 / 11.7 release notes and official Docker image upgrade behavior
  • Key findings

    • The change targets a production, stateful MariaDB instance backed by a persistent volume
    • The update moves from MariaDB 11.4 (LTS) to 11.7 (rolling release, no longer maintained)
    • The manifest does not show an explicit upgrade path for existing data; MARIADB_AUTO_UPGRADE is not configured
    • The primary risk is DB upgrade behavior and rollback complexity, not the added digest pin
  • Resulting recommendation

    • Mark the update as high risk
    • Recommend closing/recreating in favor of the pending 11.8 update
    • If 11.7 is still desired, require backup/restore readiness and an explicit mariadb-upgrade plan before merge
  • Assessed surface

    containers:
      - name: mariadb
        image: mariadb:11.7@sha256:fcc7fcd7114adb5d41f14d116b8aac45f94280d2babfbbb71b4782922ee6d8d4
        volumeMounts:
          - name: data
            mountPath: /var/lib/mysql
    

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/webgrip/homelab-cluster/pull/87 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 5/22/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `copilot/renovate-agent-review-79` --- ### 📝 Commits (1) - [`76d4ecc`](https://github.com/webgrip/homelab-cluster/commit/76d4ecc95b48750f3685d861616894ed47619035) Initial plan ### 📄 Description This updates the Renovate review for the MariaDB image bump used by Invoice Ninja. The review focuses on the actual deployment surface in this repo and the upstream MariaDB/Docker upgrade path, with emphasis on stateful upgrade risk rather than image pinning. - **What changed** - Reviewed the live PR diff for `kubernetes/apps/invoiceninja/invoiceninja/app/mariadb.yaml` - Mapped local usage across the Invoice Ninja deployment, config, and PVC manifests - Cross-checked upstream MariaDB `11.5` / `11.6` / `11.7` release notes and official Docker image upgrade behavior - **Key findings** - The change targets a production, stateful MariaDB instance backed by a persistent volume - The update moves from MariaDB `11.4` (LTS) to `11.7` (rolling release, no longer maintained) - The manifest does not show an explicit upgrade path for existing data; `MARIADB_AUTO_UPGRADE` is not configured - The primary risk is DB upgrade behavior and rollback complexity, not the added digest pin - **Resulting recommendation** - Mark the update as **high risk** - Recommend **closing/recreating** in favor of the pending `11.8` update - If `11.7` is still desired, require backup/restore readiness and an explicit `mariadb-upgrade` plan before merge - **Assessed surface** ```yaml containers: - name: mariadb image: mariadb:11.7@sha256:fcc7fcd7114adb5d41f14d116b8aac45f94280d2babfbbb71b4782922ee6d8d4 volumeMounts: - name: data mountPath: /var/lib/mysql ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
ryangr0 2026-06-08 08:31:11 +00:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
webgrip/homelab-cluster#277
No description provided.