chore: add MARIADB_AUTO_UPGRADE=1 to mariadb overlay #3
Reference in New Issue
Block a user
No description provided.
Delete Branch "upgrade-4.0.0+2.4.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The main upgrade to louislam/uptime-kuma:2.4.0 and mariadb:12.3 was already merged upstream (commits
47f5a98and51d0284). This PR adds the missingMARIADB_AUTO_UPGRADE=1env var tocompose.mariadb.yml, which ensures safe in-place upgrades for operators moving from MariaDB 11.x → 12.x.Note: cc-ci tests use the SQLite path (compose.yml only), so this overlay change passes CI via the existing test suite.
cc @trav @notplants
!testme
🌻 cc-ci —
uptime-kuma@eb4521cc✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
uptime-kuma@eb4521cc✅ passedfull logs · dashboard
eb4521cc5dtob0ce7942c7chore: upgrade to 3.1.0+2.4.0to chore: add MARIADB_AUTO_UPGRADE=1 to mariadb overlay!testme
🌻 cc-ci —
uptime-kuma@b0ce7942✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.